Event based triggers in Landmark

Hi,

I need to trigger an IPA flow when there is a new record created in Employee BC (new hire/rehire record) in MT. Is it possible to trigger event-based triggers on a business class? Is it possible to achieve it using LPL or available webservices?

I understand we have several ways (IPA, Rep set, FCU) to get the data out of Landmark. I am looking for a real-time Employee data integration with down stream applications. Please share your inputs.

Thanks,

Vikram

Find more posts tagged with

Process Automation (IPA) - General Discussions

Accepted answers

All comments

cleverly

Yes, it is definitely possible to trigger an IPA flow from LPL: See the syntax for initiate <PFlowServiceName> process on page 51 of the current LPL guide.

I've done it from a UBC before. But there's no reason it shouldn't work for a delivered one (and, in fact, that's how the delivered BC's that do trigger IPA's most of the time, unless they use trigger <RelatedValue> PA Service, which you could probably use too).

Unfortunately you cannot define LPL to run before or after each create statement. But you could add an ActionOverride for each existing Create action on the Employee business class (or at least those that are not-restricted and relevant to your flow). So you may have to duplicate some code, and when CU's come out you'd need to keep an eye out for any newly defined create actions, but it is totally doable.

cleverly

As far as webservices go, if you periodically poll the Employee business class's REST endpoint and specify _fts (from timestamp) and _tts (to timestamp) parameters, Landmark will return records that were created, changed, or deleted during that time frame (and it identifies, for each record, whether it was a create, update or delete). You could filter on create and do things as a batch that way. [We query once every 15 minutes for newly created or updated employees—during business hours—and then ship them off to our 3rd party timekeeping system.]

john-miller

Hire Actions, Rehire Actions, Promotions, Terminations and so on are all "Request Actions." They all run a Workunit already. You can add updates to those Process Definitions, or create a Workunit trigger in those Process Definitions to kick off a secondary workunit. You can also check ION to see if messages are flowing through One View, and you can build your product integration through ION. If setup correctly, most objects have BODs built already, you would just have to build some data flows and API endpoints in ION to push the data through.

Copyright © 2025 Infor. All rights reserved.