When an OmniScript fails to display data returned from an Integration Procedure, the issue often lies in how the data is processed and mapped after the Integration Procedure completes its execution.

1. The Response JSON Path property within the OmniScript's Integration Procedure Action element filters the raw JSON response. If this path is configured incorrectly or is too specific, it can exclude, or "trim," the nodes containing the expected data, preventing them from being added to the OmniScript's data JSON.

2. For data to be displayed in an OmniScript element (e.g., a Text Block), the element's Name property must exactly match the corresponding key (node name) in the JSON data structure. If the element name and the JSON key do not match, the data binding fails, and the data will appear to be missing.

C. The Integration Procedure Preview Input Parameters are used exclusively for testing the Integration Procedure in isolation within the designer and have no effect on its runtime execution when called from an OmniScript.

D. This option describes a potential issue with the input sent to the Integration Procedure. The problem described is with the response data being displayed in the OmniScript, which is a separate part of the data flow.

1. Salesforce OmniStudio Documentation

Integration Procedure Action: "To filter the response from the Integration Procedure

enter a path to a node in the Response JSON Path field. The data from the node is merged into the OmniScript's data JSON." This confirms that an incorrect path can trim data (Option A).

2. Salesforce OmniStudio Documentation

OmniScript Data JSON: "OmniScript elements display and update data in the OmniScript's data JSON. The Name of an element must match a key in the data JSON for the element to populate with data." This supports the reasoning for Option B.

3. Salesforce OmniStudio Documentation

Test an Integration Procedure: "The Preview tab enables you to test the Integration Procedure by providing input parameters and viewing the output... This is for design-time testing." This confirms that preview parameters do not affect runtime calls

making Option C incorrect.