An OmniScript displays data from an API via an Integration Procedure, but some data is missing. Which configuration error could cause this?

An OmniScript displays data from an API via an Integration Procedure, but some data is missing. Which configuration error could cause this?

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

Answer: (A)

Data binding between OmniScript and the Integration Procedure response hinges on matching the element names in the OmniScript to the JSON keys returned by the IP. If the element name for a piece of data doesn’t align with the corresponding key in the IP’s response, that value has nowhere to bind in the OmniScript, so it stays empty. This mismatch is a common configuration error that explains why some data shows up while other fields are blank, even though the API call succeeded. The other scenarios would lead to different symptoms: mismatched input parameters can disrupt what the IP receives and returns; a mismatch in the JSOW input affects what the IP expects; and trimming data via a JSON Path changes what is selected from the response rather than failing to bind a valid key. The binding mismatch explains partial data absence most directly.

Data binding between OmniScript and the Integration Procedure response hinges on matching the element names in the OmniScript to the JSON keys returned by the IP. If the element name for a piece of data doesn’t align with the corresponding key in the IP’s response, that value has nowhere to bind in the OmniScript, so it stays empty. This mismatch is a common configuration error that explains why some data shows up while other fields are blank, even though the API call succeeded.

The other scenarios would lead to different symptoms: mismatched input parameters can disrupt what the IP receives and returns; a mismatch in the JSOW input affects what the IP expects; and trimming data via a JSON Path changes what is selected from the response rather than failing to bind a valid key. The binding mismatch explains partial data absence most directly.