Which statement describes Input Mappings from OmniScript to Integration Procedure?

Which statement describes Input Mappings from OmniScript to Integration Procedure?

• A. They map fields from OmniScript context data to the Integration Procedure input.
• B. They pass data via local browser storage.
• C. They require an external API gateway.
• D. They only pass output data, not inputs.

Answer: (A)

Input mappings are the mechanism that pass data from the OmniScript context into the inputs of an Integration Procedure. During runtime, you bind specific fields or expressions from the OmniScript data to the corresponding input parameters of the Integration Procedure, so the IP receives exactly the information it needs to run. After the Procedure executes, you typically use output mappings to bring results back into OmniScript. Data isn’t passed via local browser storage, and an external API gateway isn’t part of the mapping concept. Also, input mappings are about supplying inputs to the IP, not about outputs. For example, you would map a value like customerId from OmniScript to the IP’s customerId input so the Procedure can process it.

Input mappings are the mechanism that pass data from the OmniScript context into the inputs of an Integration Procedure. During runtime, you bind specific fields or expressions from the OmniScript data to the corresponding input parameters of the Integration Procedure, so the IP receives exactly the information it needs to run. After the Procedure executes, you typically use output mappings to bring results back into OmniScript.

Data isn’t passed via local browser storage, and an external API gateway isn’t part of the mapping concept. Also, input mappings are about supplying inputs to the IP, not about outputs. For example, you would map a value like customerId from OmniScript to the IP’s customerId input so the Procedure can process it.