Pass the Salesforce Salesforce Developer OmniStudio-Developer Questions and answers with CertsForce

The missing access is execute access to the specific Apex class used by the Remote Action. A Remote Action in an Integration Procedure invokes Apex or an invocable action, so the running user must be authorized to execute that Apex class. Salesforce documentation for OmniStudio Apex class permission checkers states that access must be enabled for the classes used by Remote Action APIs for each profile, permission set, or permission set group. “Run Flows” is irrelevant because this is not Flow execution. General data-model access may still be required for object operations, but it does not authorize the Apex class itself. A Try-Catch Block can catch or handle an error response, but it does not fix the underlying unauthorized Apex execution failure.

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

Option C is the correct way to configure Additional input to send exactly the same data as Input Data. The Additional input should have a key/value pair for each field in Input Data, and the value should be set to {{InputData.field}} for each field. This will pass the value of Input Data for each field to Additional input.

QUESTIONNO: 23

A healthcare company wants to enable its subscribers to add, edit, or delete dependents related to their policy Community portal. The developer on the project decides to use an MniScript.

How should the developer configure the OmniScript to providethis functionality?

A. Use an Edit Block element configured with Remote Actions.

B. Use an Edit Block element configured with SOQL statements.

C. Use an Input Block element and a DataRaptor Post Action element.

D. Use a Text Block element and a Remote Action element.

Answer: A

An Edit Block element configured with Remote Actions allows the developer to create a dynamic table that can display, add, edit, or delete records from a Salesforce object. The Remote Actions can be configured to perform CRUD operations on the object using SOQL or Apex.

Updating Salesforce data from an OmniScript requires a write operation, so the correct tool is a Data Mapper Load. A Data Mapper Extract reads data from Salesforce; it cannot update the Contact record. A Data Mapper Transform only reshapes data between formats and does not perform the Salesforce database update. The Data Mapper Load should include the Contact identifier and the new Phone value so Salesforce can update the correct record. When upsert behavior is needed, the appropriate field mapping must identify the key used to determine whether the record already exists. The question asks specifically about changing a Contact phone number from an OmniScript, so the correct configuration is a Data Mapper Load with the RecordId/key and updated phone value.

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

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. 

In OmniStudio, the Edit Block element is purpose-built for allowing users to dynamically add, edit, or delete rows of related data, such as dependents under a policy. To save these changes, Remote Actions (typically backed by Apex or API) are used to process each record operation (Create/Update/Delete).

A. Use an Edit Block element configured with Remote Actions – Correct. This is the recommended and most scalable way to support CRUD operations in OmniScripts for collections (e.g., dependents). The Edit Block provides UI-level support, while Remote Actions handle back-end interaction with Salesforce or external systems.

Incorrect Options:

B. Text Block is for display purposes and cannot manage data input or backend actions.

C. Input Block elements do not support row-level add/edit/delete functionality as Edit Blocks do.

D. SOQL is a read-only query language and cannot be used to update or delete records directly within an OmniScript.

Salesforce OmniStudio Guide → OmniScript Edit Block Element

OmniStudio Best Practices → CRUD Operations in OmniScripts

Two separate Group elements with mutually exclusive conditions provide the cleanest declarative control. One Group should execute only when updateBillingAddress is true and updateShippingAddress is false. The other Group should execute only when updateShippingAddress is true and updateBillingAddress is false. This enforces that only one address update path runs. A single OR condition would allow either or both flags to be true, so it cannot prevent simultaneous updates. A Try-Catch Block reacts after an error occurs; it is not the right way to express business-rule branching. An HTTP Action would add unnecessary external dependency. Integration Procedure blocks and groups are designed to run related steps conditionally, so mutually exclusive Group conditions are the correct structure.

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

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 correct parameter is ContextId. When an OmniScript is launched from a Lightning Record page, Salesforce passes the current record ID into the OmniScript as a context ID. The OmniScript can then use ContextId to query related data through Data Mapper Extracts, Integration Procedures, or other actions. Using AccountId might work only if the developer manually maps that value, but it is not the standard automatic page-context parameter. recordId is common in Lightning Web Components, but OmniScript’s record-page launch behavior uses ContextId. CurrentRecord is not the standard OmniStudio parameter. Salesforce documentation explicitly states that, by default, the record ID on a Lightning Record page passes into the OmniScript as a context ID.

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

 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.