Skip to main content

Hey all, is there any known best practice in how one should check in / out documents via projections in regards of integrations and automation?

E.g. scenario might be:

1. Read file using Power Automate or Logic Apps
2. Run some logic against IFS e.g. verify that a work order exist or similar.
3. Create new document or new revision (with a potential view copy).
4. Stream the document into IFS Applications (NOT using the AccessProvider but via projections or similar e.g. Aurena agent).
5. Run some additional logic.
Preferably with rollback if possible e.g. if step 5 fails, we need to rollback the entire thing.

Any help, input, examples would be much appreciated.

Hi,

Have a look at the projection CreateAndImportDocument, it's made for these scenarios. It's documented in 21R1, and works the same on Apps 10.

/Mathias

 

 

thx Mr Dahl, is it possible to encapsulate transactions somehow in order to perform rollback? Like tag start and end somehow with a commit or rollback?

Secondly, I assume running any PLSQL is out of the question for Cloud21R1 and onwards? Which means we need to use a projection in order to combine several logical transactions with each individual rollback?

Terms & ConditionsCookie settings