Download Latest OmniStudio-Consultant Questions

The feature that can be used to meet this requirement in an Integration Procedure is Loop Block. Loop Block allows the designer to iterate over a collection of data and perform actions on each item. In this case, a Loop Block can be used to loop over each contact record in the list and perform a multi-step calculation using Calculation Actions or Calculation Procedures. Batch Action is not a feature in Integration Procedure, but a type of Action element that can perform bulk operations on data. Conditional Block is used to specify a condition that determines whether the actions inside the block will run or not. DataRaptor Transform Action is used to transform data from one format to another using templates.

The FlexCard design solution that the consultant should recommend is to add a menu element and include all the actions. A menu element can display a list of actions in a dropdown menu, with icons and labels for each action. The consultant can use a menu element to show all the 8 actions in the FlexCard, without overloading it with buttons or links. This will improve the user experience and the design of the FlexCard

 The three OmniScript elements that should be used to meet these requirements are: Select, DataRaptor Extract Action, and DataRaptor Post Action. A Select element can display a dropdown list of options for the user to choose from, such as payment type. A DataRaptor Extract Action can retrieve data from a Salesforce object, such as saved payment information, and store it in an Interface object or a JSON object. A DataRaptor Post Action can write data to a Salesforce object, such as new payment information, and perform insert or update operations

The two reasons that explain why Integration Procedures are recommended as the first choice of data sources for FlexCards and OmniScripts are: they future-proof your front-end design and they combine multiple actions into a single server call. An Integration Procedure can abstract the data source from the front-end design, making it easier to change or update the data source without affecting the FlexCard or OmniScript. An Integration Procedure can also execute multiple DataRaptor actions, such as Extract, Transform, and Load, and also invoke REST or SOAP services in one call, reducing the number of requests and processing time