When would you choose an Integration Procedure over an OmniScript?

When would you choose an Integration Procedure over an OmniScript?

• A. For simple data entry forms with validations on the client.
• B. For styling and layout of cards.
• C. For guided user flows in the UI.
• D. For server-side orchestration, external service calls, and data aggregation.

Answer: (D)

Integration Procedures are designed for server-side orchestration. They run on the backend to coordinate external service calls, fetch and merge data from multiple sources, and perform data transformations without presenting any UI. That makes them the right choice when you need to aggregate or orchestrate data across systems and return a prepared payload to the front end. In contrast, OmniScript handles guided UI flows, data entry, and client-side validations, while styling and layout are UI concerns. Guided user journeys belong to OmniScript, not to server-side procedures. So you’d pick an Integration Procedure when the goal is server-side orchestration, external service calls, and data aggregation.

Integration Procedures are designed for server-side orchestration. They run on the backend to coordinate external service calls, fetch and merge data from multiple sources, and perform data transformations without presenting any UI. That makes them the right choice when you need to aggregate or orchestrate data across systems and return a prepared payload to the front end.

In contrast, OmniScript handles guided UI flows, data entry, and client-side validations, while styling and layout are UI concerns. Guided user journeys belong to OmniScript, not to server-side procedures.

So you’d pick an Integration Procedure when the goal is server-side orchestration, external service calls, and data aggregation.