OmniStudio-Developer Exam Dumps - Salesforce Certified OmniStudio Developer Plat-Dev-210

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. 

A Remote Action is the Integration Procedure element designed to call custom Apex logic. This scenario requires execution of an Apex method that performs custom authentication and token generation before later data retrieval, which is exactly the type of server-side custom logic handled by a Remote Action. A Data Mapper Transform restructures data; it does not execute Apex. A Sub-Integration Procedure calls another Integration Procedure, not an Apex method directly. An HTTP Action calls an external REST endpoint, which is useful after token generation but does not execute local Apex code. Salesforce documentation explicitly states that the Remote Action element calls the specified Apex class and method or an invocable action.

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

The requirement is element-level visibility: only one Overdue status block must appear when Account Balance is greater than zero. The correct FlexCard configuration is a rendering condition directly on the Block element. FlexCard element conditions are designed to show relevant information based on field values from the card’s data source. Creating a separate Card State is excessive because the whole card layout does not need to change; only one block must be conditionally visible. A Setup tab filter controls data retrieval, not the display of a specific UI block after data is returned. A Flyout action is also unrelated because it opens additional content after user interaction. The verified implementation is to add a rendering condition to the Block element.

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

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 six elements: ContactName, ContactPhone, ContactEmail, CaseNumber, CaseSubject, and CaseStatus. The DRGetContactDetails action is a DataRaptor Extract action that retrieves data from the Contact and Case objects in Salesforce. The BlkCases element is a Repeat Block that displays a list of cases related to the contact. Therefore, the JSON from the DRGetContactDetails action that would display all six values correctly shown is option A, which has the following structure:

The other options have different structures that do not match the OmniScript structure shown.

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.

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

The Add Response To Response JSON property on the DataRaptor Action indicates that the output of the DataRaptor should be added to the response JSON of the Integration Procedure. If this property is not set to true, the response will be empty even if the DataRaptor extracts data successfully. 

 Using the LIMIT filter on the Extract definition allows the developer to specify the maximum number of results to return from the DataRaptor Extract. Defining a formula with the Filter function is used to filter the results based on a condition. Using a Custom Output Type when creating the DataRaptor is used to define the structure of the output data. Setting the Limit Property on the Action that calls the DataRaptor Extract has no effect on limiting the results.

he Aggregation Step in a calculation procedure allows the developer to perform aggregate functions such as SUM, COUNT, MIN, MAX, and AVG on the output of a previous step. The developer can use this step to calculate the sum of the entire base price by specifying the field name and the aggregation function