In a typical OmniScript to DataRaptor Extract integration, what must be configured to supply input to the Extract step?

In a typical OmniScript to DataRaptor Extract integration, what must be configured to supply input to the Extract step?

• A. Provide hard-coded values only.
• B. Map the relevant OmniScript context data as input fields.
• C. The Extract step does not require input.
• D. Use external API keys.

Answer: (B)

Input to the DataRaptor Extract in OmniScript comes from mapping OmniScript context data into the Extract’s input fields. The Extract uses these inputs to determine what to fetch, so you pull values from the running OmniScript (like IDs, search terms, or other criteria) and place them into the input structure that the Extract expects. This makes the data retrieval dynamic and based on the current OmniScript state, rather than relying on hard-coded values. The input must come from the OmniScript context; it's not about authentication keys, and the Extract step does require input parameters to operate.

Input to the DataRaptor Extract in OmniScript comes from mapping OmniScript context data into the Extract’s input fields. The Extract uses these inputs to determine what to fetch, so you pull values from the running OmniScript (like IDs, search terms, or other criteria) and place them into the input structure that the Extract expects. This makes the data retrieval dynamic and based on the current OmniScript state, rather than relying on hard-coded values. The input must come from the OmniScript context; it's not about authentication keys, and the Extract step does require input parameters to operate.