Authentic Salesforce Certification Exam OmniStudio-Developer Questions Answers

The correct syntax for merge codes in Integration Procedure is {(NodeName)}, where NodeName is the name of the JSON node in the data source. The other options are either missing the parentheses or using incorrect symbols.

Setting the Timeout property on the HTTP Action in the Integration Procedure allows the developer to specify how long to wait for a response from the external system before timing out. Checking the Chain on Step Check on the HTTP Action in the Integration Procedure allows the developer to chain multiple HTTP Actions together and execute them sequentially. Configuring a Remote action with timeout settings of 120000 is not necessary, as it is already done by default in OmniStudio. Checking the Chainable checkbox on the integration procedure Action in the OmniScript has no effect on calling an external system.

The Conditional View property on the Step elements is the correct client-side control. The branching depends on a value selected earlier in the OmniScript, and the constraint explicitly says not to use server-side logic. Conditional View can hide or show elements, blocks, or steps based on conditions in the OmniScript data JSON. Pub/Sub on FlexCard elements is unrelated because this is an OmniScript step-visibility problem, not inter-component messaging. An Integration Procedure conditional block would push the path decision to server-side logic, violating the requirement. A Data Mapper does not control UI step visibility. Salesforce documentation states that Conditional View hides an element or group of elements in a block or step based on specified conditions, which fits this scenario precisely.

================