Vlocity Facts #31 || Calling Integration Procedure asynchronously from Omniscripts and Integration Procedures

An asynchronous process is a process or function that executes a task "in the background" without the user having to wait for the task to finish.

Omniscripts:
By using Non-Blocking, Fire and Forget, Use Future, Use Queueable we can Integration procedure in asynchronous mode.

  • Non-Blocking — Runs asynchronously, and the response is applied to the Ul. When Invoke Mode is set to non-blocking, elements using default values will not receive the response because the element loads before the response returns.
  • Fire and Forget — Runs asynchronously with no callback to the Ul. A response will still appear in the debug console but will not be applied to the Data JSON.
  • Use Future — Specifies that the Integration Procedure runs asynchronously, as a Salesforce future method, which can return no data to the calling OmniScript.
  • Use Queueable — Which runs in Async mode, which have higher governor limits.
Integration Procedure: 
If a Child IP need to be called in Async mode from parent IP then you can use remote action and make useFuture as true. 
Same way you can mark useQueueable as true in Parent IP.
----------------------------------------------------------------------------------------------------------
If your parent Ip has 2 child Ip's one by one and if you face any issue, for example 2nd child Ip is depend on 1st Ip response. In this scenario if 1st child Ip takes long time to execute 2nd child Ip will execute immediately with out 1st Ip response -- To avoid this we can make useFuture as true in 2nd child Ip it will wait till the 1st child Ip execution.  

For other references: Integration Procedure Properties

Comments

Post a Comment

Popular posts from this blog

Vlocity Facts #01 | OmniStudio DataRaptors

DataRaptor is a mapping tool that  you can use to read, transform, and write Salesforce data. For Example. In each interaction with a digital customer  or business process, the system needs to extract the data in order to display it. If the user modifies this data or enters new data, they also need to be saved. This is where we use OmniStudio DataRaptors.  Where to use DataRaptors? Retrieving Data:   OmniScript calls  DataRaptor Extract (via the integration procedure) to read the data from Salesforce. For example, OmniScript editing an account should display data such as account name, phone number, website, and so on. Manipulating data: OmniScript captures modified and new data based on user input. For example, an agent changes the  phone number of an account. Save Data:   OmniScript calls DataRaptor Load (via the integration procedure) to write the data back to Salesforce. For example, the updated account phone number is saved back to the Account rec...
Read more

Vlocity Facts #34 || Getting the details from the URL in a FlexCard and an Omniscript

Image
 1.The parameters in the URL must be in the format c__Node, followed by their values, in order to extract the parameters from the URL. For example: If you need to show different layout or different set of actions for community users and salesforces users you can pass different parameters in URL. For Community Portal Pass Community or any other reference value in ' c__Type '. https://salesforce.lightning.force.com/lightning/cmp/ omnistudio__vlocityLWCOmniWrapper?c__target=c%3ApHXTestFlexCard&c__tabIcon=custom%3Acustom18& c__Type =Community  For Salesforce Users Pass Salesforce or any other reference value in ' c__Type '. https://salesforce.lightning.force.com/lightning/cmp/ omnistudio__vlocityLWCOmniWrapper?c__target=c%3ApHXTestFlexCard&c__tabIcon=custom%3Acustom18& c__Type =Salesforce  2. We can get the value as {Params.c__Parameter} from the FlexCard and we can execute different actions based on the input. 3. From the omniscript,  we can retrieve ...
Read more

Vlocity Facts #44 || Communication between Omniscript and Flexcard [Pub/Sub]

Image
Flexcards have the ability to trigger and listen to two kinds of events: Custom and Pubsub events . Custom Events: Facilitate the transmission of information between a child and its parent. This can occur between a child Flexcard and its parent Flexcard, or between an element and the Flexcard to which it belongs. Pubsub Events: Allows communication between two separate components. This could occur between two separate Flexcards on the same Lightning page, known as sibling Flexcards, or between a Flexcard and an Omniscript.  In this post I will discuss about Pub/Sub event. Consider we have omniscript and flexcard individually on home page when an update happens we need to show those details in flexcard. To achieve this we can use pub/sub event. Step 1: Create a omniscript according to your requirement. I'm trying to create Contact record by using Step element and data raptor post action. Now to trigger the flexcard we need to configure the messaging frame work when an update happen...
Read more