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

 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.

The FlexCard Player component is used to display FlexCards in a community page. The developer needs to add the FlexCard’s API name to the FlexCard Player component to configure the FlexCard for deployment in a community.

If the user already has OmniScript runtime access, the next security issue to investigate is access to the underlying Apex classes used by OmniStudio runtime operations, Data Mappers, Integration Procedures, or Remote Actions. Salesforce’s OmniStudio security checks include Apex class access enforcement, especially where Remote Actions or managed package classes are involved. Save Options would affect how data is saved, not whether the Lightning component can be accessed. Multi-language settings do not cause a permission-to-access-component error. FlexCard permissions are not the most likely cause when the problem occurs while launching an OmniScript. Therefore, the developer should verify the user’s permission sets/profile grant access to the Apex classes required by the OmniScript’s runtime and called actions.

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

The Send JSON Path syntax for accessing an element from an Integration Procedure structure is BlockName.ElementName. In this case, the BlockName is BlockX and the ElementName is ActionZ. The colon (:) is used to separate the input and output parameters, not the block and element names. The order of the block and element names should follow the hierarchy of the structure, from top to bottom.

When data changes every five minutes, the cache lifetime should be close to that refresh cycle. A 300-second Cache Duration gives the Integration Procedure a performance benefit while limiting stale data exposure to approximately the same interval as the source data change frequency. A contextual key controls cache separation by context, but it does not define when cached data expires. Disabling caching ignores the stated requirement that the developer wants to use caching. A very high value, such as 24 hours, is dangerous because users could receive stale data long after the underlying source changed. Salesforce’s OmniStudio caching guidance explains that Integration Procedures can cache results and that Cache Blocks are appropriate when different data must expire at different times.

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

In Expression Sets, for any intermediate step (like Calculation) to be referenced in subsequent steps, such as Aggregation, the value must be made available via Output.

B. It must be included in the output – Correct. Each step has an " Include in Output " checkbox. If not checked, its result is not accessible to following steps like Aggregation or Sub Expression.

Incorrect Options:

A. Constants are global but do not affect step dependency.

C. It does not have to be a Calculation Step; any previous step’s output can be used if exposed.

Salesforce OmniStudio → Expression Sets - Step Configuration

 The Use Data JSON property must be selected in the properties of the Type Ahead Block in order to display the fetched data in the fields. The Lookup Mode property is used to specify the type of lookup to perform. The FirstName, LastName, and BirthDate fields can be placed inside or outside the Type Ahead Block. The typeHead key is in the correct format.

 In a calculation procedure, the output of a calculation step must be included in the calculation output in order to be used in an aggregation step. The calculation output defines the variables that are available for aggregation