OmniStudio-Developer Exam Results

A Set Values Action in a Value field and a Remote Action in an Additional Output value field can execute a function like CONCAT or DATEDIFF by using the syntax {{function(parameters)}}. For example, {{CONCAT(‘Hello’, ‘World’)}} or {{DATEDIFF(‘2021-01-01’, ‘2021-01-31’)}}.

 According to the FlexCard Designer Overview page, another possible cause of a field showing only the label is that “the field is null on the Salesforce record”.

The requirement is only to show or hide a section based on a value already present in the OmniScript data JSON. That is exactly what Conditional View is designed for. It evaluates client-side conditions and controls whether a step, block, or element is displayed, editable, or required. Using an Integration Procedure would add unnecessary server-side processing because the required VIP value is already available in the OmniScript. A Data Mapper Transform is also unnecessary because there is no structural transformation requirement. Creating a new version may be part of the deployment process, but it is not the functional configuration that controls visibility. The best implementation is to place the special offers section in the script and configure Conditional View logic against the VIP member value.

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

The Remote Action node is identified by the element name configured in the Integration Procedure. Since the Remote Action is named FetchCart, the relevant Preview JSON node for that action is FetchCart. The debug-specific node, such as FetchCartDebug, is used for diagnostic details, not as the primary action node being evaluated in this question. ResponseCart and ResponseCartDebug belong to the Response Action, not the Remote Action. Salesforce documentation confirms that a Remote Action in an Integration Procedure calls the specified Apex class, method, or invocable action, and Integration Procedure actions are configured and executed as named elements in the procedure sequence.

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