Salesforce Developer OmniStudio-Developer Book

The merge code syntax for accessing a node from an Integration Procedure output is {{ProcedureName:NodeName}}. In this case, the ProcedureName is HTTPGetCaseDetails and the NodeName is CaseData. The % sign is used for single-value merge codes, not node merge codes. The $ sign is used for variables, not merge codes.

The correct answer is Option B, which shows a FlexCard with a header, a body, and a footer. The header contains the title and the icon of the FlexCard. The body contains a Data table element that displays the records from the parent FlexCard. The footer contains a navigation Action that invokes an OmniScript. Option A is incorrect because it shows a FlexCard with only a header and a body, and no footer.

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 Integration Procedure needs three separate responsibilities: retrieve Salesforce data, process it with Apex, and return the final response. A Data Mapper Extract Action reads Salesforce data and returns selected records and fields to the Integration Procedure data JSON. A Remote Action calls an Apex class method or invocable action, which satisfies the requirement to process data through Apex. A Response Action then returns the final data to the caller. Data Mapper Post Action is wrong because it writes data to Salesforce rather than retrieving it. HTTP Action is wrong because it calls an external REST endpoint, not an Apex class. The correct Integration Procedure design is therefore Data Mapper Extract Action, Remote Action, and Response Action.

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