Salesforce OmniStudio-Developer - Salesforce Certified OmniStudio Developer (SP25)

 According to the OmniScript Data JSON page, the OmniScript structure JSON defines the data elements and their properties that are used in an OmniScript. The exhibit shows an OmniScript structure JSON with three elements: Step, Block, and Telephone. The Step element is an empty object, the Block element is an object with two properties: Text and Telephone, and the Telephone element is a string. Therefore, the JSON code that correctly represents the step in the OmniScript Structure panel shown is option C, which has the following structure:

The other options have different structures that do not match the OmniScript structure shown. Therefore, the correct answer is C.

The Timeout property on the HTTP Action in the Integration Procedure specifies how long to wait for a response from the external system before throwing an error. The Chain On Step checkbox on the HTTP Action in the Integration Procedure indicates that the next action should be executed only if the current action is successful. These two configurations should be used to implement the call to the external system given its known performance issues. 

Checking the Enable Cancel checkbox in the Setup tab under Cancel Options allows the developer to enable the cancel functionality for all steps in the OmniScript. The user can cancel the OmniScript at any time by clicking the Cancel button in the top right corner of the OmniScript. Adding a navigation Action inside each step is not necessary and would clutter the OmniScript design. Setting the Component name or Element Name to ‘’Cancel’’ has no effect on enabling the cancel functionality.

The Additional Input property allows the developer to specify additional input parameters to be sent to the Integration Procedure element. The input parameters can be specified as a JSON object or as a list of key-value pairs. If the developer checked Send Only Additional Input, then only the input parameters specified in Additional Input are sent, and the SEND/RESPONSE TRANSFORMATIONS are ignored. Therefore, the developer needs to specify the same input parameters as in the SEND/RESPONSE TRANSFORMATIONS in Additional Input. Option C shows how to do this using a JSON object with two properties: “DBExtractAction:Account” and “DBExtractAction:SecondaryAccount”. The values of these properties are the same as in the SEND/RESPONSE TRANSFORMATIONS. 

 Using two separate Calculation Steps with the Conditional Step property selected allows the developer to specify different formulas based on different conditions. The ISTRUE(isCustomer) and NOT(ISTRUE(isCustomer)) functions are used to evaluate the Boolean variable in the Condition syntax. The other options are either missing the Conditional Step property, using incorrect comparison operators, or using an IF statement instead of separate Calculation Steps.

 The merge code syntax for passing data from a DataRaptor Extract Action to an HTTP Action is %DataRaptorName: NodeName%. In this case, it is %DRReadCase: CaseNumber%.

Cloning an Integration Procedure creates a copy of it that can be modified and used independently from the original one. This is useful when the new Integration Procedure has a different purpose or functionality than the original one

The Lookup element is used to retrieve data from a single field in a Salesforce record. The Lookup element allows the developer to specify the object, field, and filter criteria for the data retrieval. The Select element is used to display a list of options for the user to choose from. The HTTP Action element is used to send or receive data from an external system using HTTP methods. The DataRaptor Post Action element is used to create or update Salesforce records using a DataRaptor Transform.

 A DataRaptor Extract can retrieve data from multiple objects using extraction steps and JSON paths. However, if the data is from a single object, only one extraction step is needed. The Extract JSON Path can use dot notation to access related fields from that object, such as Contact.Account.Name.

According to the Transform External Data Unit, the Expected Output JSON should match the Output Path of the DataRaptor Transform. In option D, the Output Path is Current:CityState, which matches the Expected Output JSON. The other options have different Output Paths that do not match the Expected Output JSON. Therefore, the correct answer is D.