Omnistudio Integration Procedure Generate

omnistudio-integration-procedure-generate: OmniStudio Integration Procedure Creation and Validation

Expert OmniStudio Integration Procedure (IP) builder with deep knowledge of server-side process orchestration. Create production-ready IPs that combine DataRaptor/​Data Mapper actions, Apex Remote Actions, HTTP callouts, conditional logic, and nested procedure calls into declarative multi-step operations.

Scope

• In scope: Creating well-structured Integration Procedures from requirements; selecting and wiring element types (DataRaptor, Remote Action, HTTP, Conditional Block, Loop, Set Values, nested IP); dependency validation; error handling patterns; 110-point scoring; deployment and activation
• Out of scope: Building OmniScripts (use omnistudio-omniscript-generate), creating Data Mappers directly (use omnistudio-datamapper-generate), designing FlexCards (use omnistudio-flexcard-generate), mapping full dependency trees (use omnistudio-dependencies-analyze), deploying metadata to org (use platform-metadata-deploy)

---

Required Inputs

• Purpose: What business process is this IP orchestrating? (e.g., "onboard a new account", "process an order")
• Target objects / data sources: Which Salesforce objects, external APIs, or both?
• Type / SubType naming: PascalCase pair that uniquely identifies the IP (e.g., Type=OrderProcessing, SubType=Standard)
• Target org alias: Authenticated org alias for deployment (e.g., myDevOrg)

---

Quick Reference

Scoring: 110 points across 6 categories. Thresholds: [PASS] 90+ (Deploy) | [REVIEW] 67-89 (Review) | [BLOCK] <67 (Block - fix required)

---

Core Responsibilities

1. IP Generation: Create well-structured Integration Procedures from requirements, selecting correct element types and wiring inputs/​outputs
2. Element Composition: Assemble DataRaptor actions, Remote Actions, HTTP callouts, conditional blocks, loops, and nested IP calls into coherent orchestrations
3. Dependency Analysis: Validate that referenced DataRaptors, Apex classes, and nested IPs exist and are active before deployment
4. Error Handling: Enforce try/​catch patterns, conditional rollback, and response validation across all data-modifying steps (DML — Data Manipulation Language)

---

CRITICAL: Orchestration Order

omnistudio-dependencies-analyze -> omnistudio-datamapper-generate -> omnistudio-integration-procedure-generate -> omnistudio-omniscript-generate -> omnistudio-flexcard-generate (you are here: omnistudio-integration-procedure-generate)

Data Mappers referenced by the IP must exist FIRST. Build and deploy DataRaptors/​Data Mappers before the IP that calls them. The IP must be active before any OmniScript or FlexCard can invoke it.

---

Key Insights

Core Namespace Discriminator: OmniStudio Core stores both Integration Procedures and OmniScripts in the OmniProcess table. Use IsIntegrationProcedure = true or OmniProcessType = 'Integration Procedure' to filter IPs. Without a filter, queries return mixed results.

CRITICAL — Creating IPs via Data API: When creating OmniProcess records, set IsIntegrationProcedure = true to make the record an Integration Procedure. The OmniProcessType picklist is computed from this boolean and cannot be set directly. Also, Name is a required field on OmniProcess (not documented in standard OmniStudio docs). Use sf api request rest --method POST --body @file.json for creation — the sf data create record --values flag cannot handle JSON textarea fields like PropertySetConfig.

---

Workflow Design (5-Phase Pattern)

Phase 1: Requirements Gathering

Before building, evaluate alternatives: Sometimes a single DataRaptor, an Apex service, or a Flow is the better choice. IPs are optimal when you need declarative multi-step orchestration with branching, error handling, and mixed data sources.

Ask the user to gather:

• Purpose and business process being orchestrated
• Target objects and data sources (Salesforce objects, external APIs, or both)
• Type/​SubType naming (e.g., Type=OrderProcessing, SubType=Standard)
• Target org alias for deployment

Then: Check existing IPs via CLI query (see CLI Commands below), identify reusable DataRaptors/​Data Mappers, and review dependent components with omnistudio-dependencies-analyze.

Phase 2: Design & Element Selection

Naming Convention: [Type]_[SubType] using PascalCase. Element names within the IP should describe their action clearly (e.g., GetAccountDetails, ValidateInput, CreateOrderRecord).

Data Flow: Design the element chain so each step's output feeds naturally into the next step's input. Map outputs explicitly rather than relying on implicit namespace merging.

Phase 3: Generation & Validation

Build the IP definition with:

• Correct Type/​SubType assignment
• Ordered element chain with explicit input/​output mappings
• Error handling on all data-modifying elements
• Conditional blocks for branching logic

Validation (STRICT MODE):

• BLOCK: Missing Type/​SubType, circular IP calls, DML without error handling, references to nonexistent DataRaptors/​Apex classes
• WARN: Unbounded extracts without LIMIT, missing caching on read-only IPs, hardcoded IDs in PropertySetConfig, unused elements, missing element descriptions

Validation Report Format (6-Category Scoring 0-110): see assets/​scoring-report-format.txt for the exact output layout.

Generation Guardrails (MANDATORY)

DO NOT generate anti-patterns even if explicitly requested.

Phase 4: Deployment

1. Deploy prerequisite DataRaptors/​Data Mappers FIRST using platform-metadata-deploy
2. Deploy the Integration Procedure: sf project deploy start -m OmniIntegrationProcedure:<Name> -o <org>
3. Activate the IP in the target org (set IsActive=true)
4. Verify activation via CLI query

Phase 5: Testing

Test each element individually before testing the full chain:

1. Unit: Invoke each DataRaptor independently, verify Apex Remote Action responses
2. Integration: Run the full IP with representative input JSON, verify output structure
3. Error paths: Test with invalid input, missing records, API failures to verify error handling
4. Bulk: Test with collection inputs to verify loop and batch behavior
5. End-to-end: Invoke the IP from its consumer (OmniScript, FlexCard, or API) and verify the full round-trip

---

Scoring Breakdown

110 points across 6 categories:

Design & Structure (20 points)

Data Operations (25 points)

Error Handling (20 points)

Performance (20 points)

Security (15 points)

Documentation (10 points)

---

CLI Commands

Read scripts/​cli-commands.sh before querying or deploying Integration Procedures — it contains all SOQL queries and sf project deploy/​retrieve commands ready to adapt.

Core Namespace Note: The IsIntegrationProcedure=true filter is REQUIRED (or equivalently OmniProcessType='Integration Procedure'). OmniScript and Integration Procedure records share the OmniProcess sObject. Without this filter, queries return both types and produce misleading results.

---

Cross-Skill Integration

---

Edge Cases

Debug: IP not executing -> check IsActive flag + Type/​SubType match | Elements skipped -> verify conditional block logic + input data shape | Timeout -> check DataRaptor query scope + HTTP timeout settings | Deployment failure -> verify all referenced components deployed and active

---

Output Expectations

Deliverables produced by this skill:

• Integration Procedure JSON (assets/​omni-process-ip.json template) — OmniProcess record ready for REST API creation with IsIntegrationProcedure=true
• Element JSON records (assets/​omni-process-element-dr-extract.json, assets/​omni-process-element-set-values.json templates) — OmniProcessElement records for each action step with PropertySetConfig wired
• Validation report — 110-point score across 6 categories with deploy/​review/​block threshold result
• Deployment checklist — confirms prerequisite DataRaptors are active, IP is activated, and consuming OmniScript or FlexCard can invoke it

---

Notes

API: Latest (check current Salesforce release notes; was 66.0 at time of authoring) | Mode: Strict (warnings block) | Scoring: Block deployment if score < 67

Dependencies (optional): platform-metadata-deploy, omnistudio-datamapper-generate, omnistudio-dependencies-analyze

Creating IPs programmatically: Use REST API (sf api request rest --method POST --body @file.json). Required fields: Name, Type, SubType, Language, VersionNumber, IsIntegrationProcedure=true. Then create OmniProcessElement child records for each action step (also via REST API for JSON PropertySetConfig). Activate by setting IsActive=true after all elements are created.

---

Reference File Index

---

Pre-Delivery Checklist

• Data Mappers exist and are deployed before IP references them
• IsIntegrationProcedure = true set when creating via Data API
• IP activated before any OmniScript/​FlexCard invokes it