Lawson TX Triggering External Events?

Sort:
You are not authorized to post a reply.
Author
Messages
Garth Gerwing
Basic Member
Posts: 27
Basic Member
    We will be required to integrate between an in-house developed application and the Lawson Financials. For near/real-time integration requirements - we plan to leverage the IOS services layer that currently supports the Portal.

    So....pushing/pulling data to/from Lawson based on external events - no problem. But does anyone have any experience with monitoring Lawson activity (either transactional or data) in order to trigger activity externally? Like "listening" to TX's or servlets - something along those lines.

    NOTE: would like to avoid DB triggers and the like - I.E. constructs that would require on-going maintenance through upgrades.

    Kwane McNeal
    Veteran Member
    Posts: 479
    Veteran Member
      Garth,
      Without knowing specifically what you are trying to accomplish, you could use some form or ProcessFlow (though the more advanced modules cost money), or you could roll your own.

      As to your statement of no on-going maintenance solutions, I don't think that's possible, because if you change the underlying form or data element in someway, as would happen in an upgrade, the event you're polling for, by definition, becomes either a different event, or a similar event with different triggers.

      Kwane
      505-433-RSGI (7744)
      Jason Beard
      Veteran Member
      Posts: 124
      Veteran Member
        As Kwane suggests Process flow is Lawson's way of accomplishing this. any combination of online screen + form action can trigger an individual flow. So if you can define the events in Lawson that you want to watch for (ie Vendor Add/change = AP10_A and AP10_C)
        then you can define a flow to handle this event.
        thanks
        Jason
        617-548-5568
        Jason Beard
        617-548-5568
        jabeard3@gmail.com
        Garth Gerwing
        Basic Member
        Posts: 27
        Basic Member
          Thanks for the timely feedback, Kane/Jason. Yeah -- I am somewhat aware that ProcessFlow (Integrator) is out there - and conceptually what it can accomplish - but the we've built our own "work flow" functionality - so I was reluctant to investigate an investment in what might possibly turn-out to be duplicate functionality/capabilities.

          Lawson is kind of pushing PF in general - as a consolidated/centralized integration platform between Lawson Financials and any in-house developed application(s). I guess I will have to take a harder look at PF.  Thanks again for your help here.

          Garth
          Jason Beard
          Veteran Member
          Posts: 124
          Veteran Member
            Another option if you want to avoid pflow is to code user exits from the online screens that can then execute your custom workflow. It's a bit more tedious in that the coding is happening in COBOL rather than in pflow designer and you are somewhat dependent on Lawson not changing field names etc on the screen but it is still a workable solution. Again, only applicable to online screens.

            thanks,
            Jason
            Jason Beard
            617-548-5568
            jabeard3@gmail.com
            You are not authorized to post a reply.