In our last post we learned about basics of Vlocity Integration Procedure. In this session we will learn the Integration procedure Advanced concepts like loop blocks in IP, List Action, Long Running Transactions, Handling Exceptions and Rollback on Error.
Integration Procedure- Loop Blocks
A Loop Block iterates over the items in a data array to repeat the Actions in the Loop Block for each
item.

Integration Procedure- List Action
Merges multiple lists by matching values of specified list item JSON nodes.
- A basic merge matches node names exactly.
- An advanced merge matches nodes that have different names and/or reside at different levels in the incoming lists.

Integration Procedure- Long Running Transactions
Use chainable and queueable chainable settings to avoid hitting Salesforce governor limits when
invoking long-running Integration Procedures. You can also chain on one or more specific
long-running steps.


Integration Procedure- Long Running Transactions Limits

Integration Procedure- Handling Exceptions and Rollback on Error
Rollback on Error Configuration – Dataraptor. Create Account and the associated Opportunity, only
when no errors.

Try Catch Block – Integration Procedure

Rollback on Error Activation – Integration Procedure
All changes are committed to the database only after all operations in the transaction finish running without errors. If an error occurs in any of the intermediate steps with the Rollback On Error option enabled, all database changes are rolled back, and the transaction isn’t committed.

Integration Procedure Advanced Concepts Video
Check our training session and let us your feedback if you like it. IP is also very useful for API callout without any code.
Summary
I hope this post helped you to understand the Integration procedure advanced concepts. If you are new to OminStudio then please check our FREE Salesforce OmniStudio Training and let us know if you like our training, Which topic you want to learn next in Apex Hours.
I have an Integration Procedure with Datarpator Post action followed by a Remote Action Element. When Remote Action is executed (it’s calling an Apex method), we are getting the error ‘There is uncommitted data, cannot make callout function’. What should we do to commit the Dataraptor post action before calling remote action from Integration Procedure?
You can invoke ip passing chainable true and enable chain on step for Dr post action
We will make a post on same topic soon
how can I invoke an IP with chainable true via apex
Is is ideal to add a Data Raptor Extract action Inside loop block? Will the framework handle this automatically or we will consume 1 SOQL for each iteration
Hello,
I have one doubt on 3rd way of IP Error handling (i.e. Enabling rollback on error on procedure configuration).
SO, Is it a mandatory thing to keep all the DR in a try catch block and check “Fail on Block error”? Instead We keep only DR load element only and check the “Fail on Step error” and inside DR load options tab the “Rollback on Error” also will be checked.. will this also rolls backs all the IP transactions.
Notify us about your findings.
Thanks
Hi In our lower environment, IPs were working fine. But after deploying them through COPADO, in higher region we are getting a error even though they are active in the environment.
Error is like this ”
error : no procedure found with Id or Integration Procedure is Inactive.
”
Any idea what can I do.