omnistudio-integration-procedure-generate

Define the business purpose, target objects, and a PascalCase Type/SubType pair, then assemble elements such as DataRaptor actions, Remote Actions, and HTTP callouts. Create the OmniProcess record via REST API with IsIntegrationProcedure=true, add OmniProcessElement child records, then deploy and activate.

Use an Integration Procedure for declarative multi-step orchestration serving OmniStudio components like OmniScripts and FlexCards. Use Flow for standard Salesforce UI automation, and Apex when you need complex computation or fine-grained transaction control across multiple DML operations.

Add a Remote Action element and set remoteClass and remoteMethod in its PropertySetConfig. The Apex class must implement the omnistudio.VlocityOpenInterface2 interface (Core namespace) or vlocity_cmt.VlocityOpenInterface (managed package) with an invokeMethod implementation.

OmniStudio Core stores both Integration Procedures and OmniScripts in the OmniProcess table. Add the filter IsIntegrationProcedure=true or OmniProcessType='Integration Procedure' to your SOQL query, otherwise results mix both component types.

Yes, use an Integration Procedure Action element with ipMethod set to the target's Type_SubType identifier. You must verify the call graph contains no cycles, since direct or indirect circular calls cause stack overflow errors at runtime.

Deployment fails when referenced DataRaptors, Apex classes, or nested IPs do not exist or are inactive in the target org. Deploy and activate all prerequisite Data Mappers first, then deploy the Integration Procedure and set IsActive=true.