Which statement best defines a Sub-Integration Procedure in OmniStudio?

Which statement best defines a Sub-Integration Procedure in OmniStudio?

• A. A one-off script executed during deployment.
• B. A data source for FlexCards.
• C. A reusable Integration Procedure invoked from another Integration Procedure, enabling modular design.
• D. A debugging tool for Integration Procedures.

Answer: (C)

Sub-Integration Procedures are reusable blocks of Integration Procedure logic that can be invoked from another Integration Procedure to keep your orchestration modular and reusable. This lets you encapsulate a common sequence of steps—like data fetch, transformation, or decision logic—into its own IP and call it from multiple places, passing in inputs and receiving outputs as part of the workflow. The other options don’t fit because a one-off deployment script is not how Sub-Integration Procedures are used, a data source for FlexCards serves UI data rather than orchestrating IP calls, and a debugging tool is for troubleshooting rather than structuring reusable integration logic. In short, a Sub-Integration Procedure is a reusable Integration Procedure invoked from another one to promote modular design.

Sub-Integration Procedures are reusable blocks of Integration Procedure logic that can be invoked from another Integration Procedure to keep your orchestration modular and reusable. This lets you encapsulate a common sequence of steps—like data fetch, transformation, or decision logic—into its own IP and call it from multiple places, passing in inputs and receiving outputs as part of the workflow. The other options don’t fit because a one-off deployment script is not how Sub-Integration Procedures are used, a data source for FlexCards serves UI data rather than orchestrating IP calls, and a debugging tool is for troubleshooting rather than structuring reusable integration logic. In short, a Sub-Integration Procedure is a reusable Integration Procedure invoked from another one to promote modular design.