If the JSON sent from the Integration Procedure Action does not match the Original Input for the Integration Procedure, which statement is true?

If the JSON sent from the Integration Procedure Action does not match the Original Input for the Integration Procedure, which statement is true?

• A. The API url is not allowed to be listed in Salesforce.
• B. The JSON sent from the Integration Procedure Action does not match any Original Input for the Integration Procedure.
• C. The OmniScript has no active version.
• D. The Integration Procedure Preview Input Parameters do not match the JSON sent from the OmniScript.

Answer: (B)

The key idea is how input data is mapped into the Integration Procedure. The Integration Procedure defines one or more Original Input definitions that describe the exact shape and field names it expects. When the Integration Procedure Action sends JSON, that payload must line up with one of those Original Input definitions so the system can map each value to the corresponding input parameter. If the JSON coming from the Integration Procedure Action doesn’t match any of the Original Input definitions, there’s no valid mapping path left for the IP’s inputs, so the call can’t be processed as designed. That’s why the statement about the JSON not matching any Original Input is the correct one. The other options aren’t about the actual input mapping: an API URL’s presence isn’t restricted in that way, having no active version is a separate condition, and the Preview Input Parameters are used for design-time testing and don’t govern the runtime mapping of data to the IP’s Original Input.

The key idea is how input data is mapped into the Integration Procedure. The Integration Procedure defines one or more Original Input definitions that describe the exact shape and field names it expects. When the Integration Procedure Action sends JSON, that payload must line up with one of those Original Input definitions so the system can map each value to the corresponding input parameter.

If the JSON coming from the Integration Procedure Action doesn’t match any of the Original Input definitions, there’s no valid mapping path left for the IP’s inputs, so the call can’t be processed as designed. That’s why the statement about the JSON not matching any Original Input is the correct one.

The other options aren’t about the actual input mapping: an API URL’s presence isn’t restricted in that way, having no active version is a separate condition, and the Preview Input Parameters are used for design-time testing and don’t govern the runtime mapping of data to the IP’s Original Input.