How do you use an Integration Procedure Action to get and display data from an external source?

• A. In the Vlocity example, you link the OmniScript to an Integration Procedure that gets the data from a weather API. This action goes above the StepContacts element because we want to execute it before it gets to the start.
• B. Place the Integration Procedure inside the StepContacts element.
• C. Integration Procedures cannot be used with OmniScripts.
• D. Only use Integration Procedures after the StepContacts element.

Answer: (A)

The idea being tested is how to bring in data from an external source using an Integration Procedure so it can be shown in the OmniScript. You create an Integration Procedure that calls the external service (for example, a weather API) and returns the results to the OmniScript. Then you add an Integration Procedure Action in the OmniScript and set it up to run at the point in the flow where you need the data. Placing that action before the StepContacts element ensures the external data is retrieved and ready before that step renders, so you can bind the retrieved values to the UI as soon as StepContacts is reached.

This approach is the standard way to fetch external data and display it in OmniScript, and Integration Procedures are designed to work with OmniScripts. The other options don’t fit this common pattern: putting the Integration Procedure inside the StepContacts element isn’t how the data-loading step is typically structured, Integration Procedures can indeed be used with OmniScripts, and waiting to run the procedure after StepContacts would delay data availability and hinder display.