If the JSON object sent from the Integration Procedure Action does not match any of the Original Input for the Integration Procedure, what issue can occur?

If the JSON object sent from the Integration Procedure Action does not match any of the Original Input for the Integration Procedure, what issue can occur?

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

Answer: (A)

The data you send into an Integration Procedure must align with one of the Original Input definitions of that Procedure. If the JSOW from the Integration Procedure Action doesn’t match any of those Original Input definitions, there’s no binding between the incoming payload and the Procedure’s expected inputs. That means the Integration Procedure can’t map the provided values to its inputs, causing the call to fail or not execute correctly. This is exactly the issue described: the JSOW sent from the Integration Procedure Action does not match any of the Original Input for the Integration Procedure.

The data you send into an Integration Procedure must align with one of the Original Input definitions of that Procedure. If the JSOW from the Integration Procedure Action doesn’t match any of those Original Input definitions, there’s no binding between the incoming payload and the Procedure’s expected inputs. That means the Integration Procedure can’t map the provided values to its inputs, causing the call to fail or not execute correctly. This is exactly the issue described: the JSOW sent from the Integration Procedure Action does not match any of the Original Input for the Integration Procedure.