In an OmniScript displaying data from an API, which configuration issue could cause missing data due to the JSON path?

In an OmniScript displaying data from an API, which configuration issue could cause missing data due to the JSON path?

• A. The missing data is trimmed in the Integration Procedure Action Response JSON Path.
• B. The JSON sent from the Integration Procedure Action does not match the Original Input for the Integration Procedure.
• C. The element name for the missing data does not match the JSON node key in the Integration Procedure Response.
• D. The Integration Procedure Preview Input Parameters do not match the JSON sent from the OmniScript.

Answer: (A)

The data mapping from the API is controlled by the JSON Path you configure in the Integration Procedure Action Response. If the data you expect to return is trimmed at that path, those fields are removed from what the OmniScript receives. That means the script can display nothing for those fields or show as missing data. Keeping the JSON Path precise and not trimming the fields ensures the full API response is available to the OmniScript. The other scenarios describe issues that affect input alignment, field naming, or preview parameters, which can cause problems but don't directly tie to trimming data in the JSON Path that feeds the OmniScript.

The data mapping from the API is controlled by the JSON Path you configure in the Integration Procedure Action Response. If the data you expect to return is trimmed at that path, those fields are removed from what the OmniScript receives. That means the script can display nothing for those fields or show as missing data. Keeping the JSON Path precise and not trimming the fields ensures the full API response is available to the OmniScript.

The other scenarios describe issues that affect input alignment, field naming, or preview parameters, which can cause problems but don't directly tie to trimming data in the JSON Path that feeds the OmniScript.