[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CBEGWAD7T398FP82D1385G":3,"skill-same:01M7CBEGWAD7T398FP82D1385G":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7CBEGWAD7T398FP82D1385G","sf-industry-commoncore-integration-procedure",null,"OmniStudio Integration Procedure creation and validation with 110-point scoring. Use when building server-side process orchestrations that combine Data Mapper actions, Apex Remote Actions, HTTP callouts, and conditional logic. TRIGGER when: user creates Integration Procedures, adds Data Mapper steps, configures Remote Actions, or reviews existing IP configurations. DO NOT TRIGGER when: building OmniScripts (use sf-industry-commoncore-omniscript), creating Data Mappers directly (use sf-industry-commoncore-datamapper), or analyzing cross-component dependencies (use sf-industry-commoncore-omnistudio-analyze).","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-industry-commoncore-integration-procedure\u002Fskills\u002Fsf-industry-commoncore-integration-procedure\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sf-industry-commoncore-integration-procedure\ndescription: >\n  OmniStudio Integration Procedure creation and validation with 110-point scoring.\n  Use when building server-side process orchestrations that combine Data Mapper\n  actions, Apex Remote Actions, HTTP callouts, and conditional logic.\n  TRIGGER when: user creates Integration Procedures, adds Data Mapper steps,\n  configures Remote Actions, or reviews existing IP configurations.\n  DO NOT TRIGGER when: building OmniScripts (use sf-industry-commoncore-omniscript), creating Data Mappers\n  directly (use sf-industry-commoncore-datamapper), or analyzing cross-component dependencies\n  (use sf-industry-commoncore-omnistudio-analyze).\nlicense: MIT\nmetadata:\n  version: \"1.0.0\"\n  author: \"David Ryan (weytani)\"\n  scoring: \"110 points across 6 categories\"\n---\n\n# sf-industry-commoncore-integration-procedure: OmniStudio Integration Procedure Creation and Validation\n\nExpert OmniStudio Integration Procedure (IP) builder with deep knowledge of server-side process orchestration. Create production-ready IPs that combine DataRaptor\u002FData Mapper actions, Apex Remote Actions, HTTP callouts, conditional logic, and nested procedure calls into declarative multi-step operations.\n\n## Quick Reference\n\n**Scoring**: 110 points across 6 categories. **Thresholds**: ✅ 90+ (Deploy) | ⚠️ 67-89 (Review) | ❌ \u003C67 (Block - fix required)\n\n---\n\n## Core Responsibilities\n\n1. **IP Generation**: Create well-structured Integration Procedures from requirements, selecting correct element types and wiring inputs\u002Foutputs\n2. **Element Composition**: Assemble DataRaptor actions, Remote Actions, HTTP callouts, conditional blocks, loops, and nested IP calls into coherent orchestrations\n3. **Dependency Analysis**: Validate that referenced DataRaptors, Apex classes, and nested IPs exist and are active before deployment\n4. **Error Handling**: Enforce try\u002Fcatch patterns, conditional rollback, and response validation across all data-modifying steps\n\n---\n\n## CRITICAL: Orchestration Order\n\n**sf-industry-commoncore-omnistudio-analyze -> sf-industry-commoncore-datamapper -> sf-industry-commoncore-integration-procedure -> sf-industry-commoncore-omniscript -> sf-industry-commoncore-flexcard** (you are here: sf-industry-commoncore-integration-procedure)\n\nData Mappers referenced by the IP must exist FIRST. Build and deploy DataRaptors\u002FData Mappers before the IP that calls them. The IP must be active before any OmniScript or FlexCard can invoke it.\n\n---\n\n## Key Insights\n\n| Insight | Details |\n|---------|---------|\n| **Chaining** | IPs call other IPs via Integration Procedure Action elements. Output of one step feeds input of the next via response mapping. Design data flow linearly where possible. |\n| **Response Mapping** | Each element's output is namespaced under its element name in the response JSON. Use `%elementName:keyPath%` syntax to reference upstream outputs in downstream inputs. |\n| **Caching** | IPs support platform cache for read-heavy orchestrations. Set `cacheType` and `cacheTTL` in the procedure's PropertySet. Avoid caching procedures that perform DML. |\n| **Versioning** | Type\u002FSubType pairs uniquely identify an IP. Use SubType for versioning (e.g., `Type=AccountOnboarding`, `SubType=v2`). Only one version can be active at a time per Type\u002FSubType. |\n\n**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.\n\n> **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`.\n\n---\n\n## Workflow Design (5-Phase Pattern)\n\n### Phase 1: Requirements Gathering\n\n**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.\n\n**Ask the user** to gather:\n- Purpose and business process being orchestrated\n- Target objects and data sources (Salesforce objects, external APIs, or both)\n- Type\u002FSubType naming (e.g., `Type=OrderProcessing`, `SubType=Standard`)\n- Target org alias for deployment\n\n**Then**: Check existing IPs via CLI query (see CLI Commands below), identify reusable DataRaptors\u002FData Mappers, and review dependent components with sf-industry-commoncore-omnistudio-analyze.\n\n### Phase 2: Design & Element Selection\n\n| Element Type | Use Case | PropertySet Key |\n|--------------|----------|-----------------|\n| DataRaptor Extract Action | Read Salesforce data | `bundle` |\n| DataRaptor Load Action | Write Salesforce data | `bundle` |\n| DataRaptor Transform Action | Data shaping\u002Fmapping | `bundle` |\n| Remote Action | Call Apex class method | `remoteClass`, `remoteMethod` |\n| Integration Procedure Action | Call nested IP | `ipMethod` (format: `Type_SubType`) |\n| HTTP Action | External API callout | `path`, `method` |\n| Conditional Block | Branching logic | -- |\n| Loop Block | Iterate over collections | -- |\n| Set Values | Assign variables\u002Fconstants | -- |\n\n**Naming Convention**: `[Type]_[SubType]` using PascalCase. Element names within the IP should describe their action clearly (e.g., `GetAccountDetails`, `ValidateInput`, `CreateOrderRecord`).\n\n**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.\n\n### Phase 3: Generation & Validation\n\nBuild the IP definition with:\n- Correct Type\u002FSubType assignment\n- Ordered element chain with explicit input\u002Foutput mappings\n- Error handling on all data-modifying elements\n- Conditional blocks for branching logic\n\n**Validation (STRICT MODE)**:\n- **BLOCK**: Missing Type\u002FSubType, circular IP calls, DML without error handling, references to nonexistent DataRaptors\u002FApex classes\n- **WARN**: Unbounded extracts without LIMIT, missing caching on read-only IPs, hardcoded IDs in PropertySetConfig, unused elements, missing element descriptions\n\n**Validation Report Format** (6-Category Scoring 0-110):\n```\nScore: 95\u002F110  Very Good\n|- Design & Structure: 18\u002F20 (90%)\n|- Data Operations: 23\u002F25 (92%)\n|- Error Handling: 18\u002F20 (90%)\n|- Performance: 18\u002F20 (90%)\n|- Security: 13\u002F15 (87%)\n|- Documentation: 5\u002F10 (50%)\n```\n\n### Generation Guardrails (MANDATORY)\n\n| Anti-Pattern | Impact | Correct Pattern |\n|--------------|--------|-----------------|\n| Circular IP calls (A calls B calls A) | **Infinite loop \u002F stack overflow** | Map dependency graph; no cycles allowed |\n| DML without error handling | **Silent data corruption** | Wrap DataRaptor Load in try\u002Fcatch or conditional error check |\n| Unbounded DataRaptor Extract | **Governor limits \u002F timeout** | Set LIMIT on extracts; paginate large datasets |\n| Hardcoded Salesforce IDs in PropertySetConfig | **Deployment failure across orgs** | Use input variables, Custom Settings, or Custom Metadata |\n| Sequential calls that could be parallel | **Unnecessary latency** | Group independent elements; no serial dependency needed |\n| Missing response validation | **Downstream null reference errors** | Check element response before passing to next step |\n\n**DO NOT generate anti-patterns even if explicitly requested.**\n\n### Phase 4: Deployment\n\n1. Deploy prerequisite DataRaptors\u002FData Mappers FIRST using sf-deploy\n2. Deploy the Integration Procedure: `sf project deploy start -m OmniIntegrationProcedure:\u003CName> -o \u003Corg>`\n3. Activate the IP in the target org (set `IsActive=true`)\n4. Verify activation via CLI query\n\n### Phase 5: Testing\n\nTest each element individually before testing the full chain:\n1. **Unit**: Invoke each DataRaptor independently, verify Apex Remote Action responses\n2. **Integration**: Run the full IP with representative input JSON, verify output structure\n3. **Error paths**: Test with invalid input, missing records, API failures to verify error handling\n4. **Bulk**: Test with collection inputs to verify loop and batch behavior\n5. **End-to-end**: Invoke the IP from its consumer (OmniScript, FlexCard, or API) and verify the full round-trip\n\n---\n\n## Scoring Breakdown\n\n110 points across 6 categories:\n\n### Design & Structure (20 points)\n\n| Criterion | Points | Description |\n|-----------|--------|-------------|\n| Type\u002FSubType naming | 5 | Follows convention, descriptive, versioned appropriately |\n| Element naming | 5 | Clear, action-oriented names on all elements |\n| Data flow clarity | 5 | Linear or well-documented branching; explicit input\u002Foutput mapping |\n| Element ordering | 5 | Logical execution sequence; no unnecessary dependencies |\n\n### Data Operations (25 points)\n\n| Criterion | Points | Description |\n|-----------|--------|-------------|\n| DataRaptor references valid | 5 | All referenced bundles exist and are active |\n| Extract operations bounded | 5 | LIMIT set on all extracts; pagination for large datasets |\n| Load operations validated | 5 | Input data validated before DML; required fields checked |\n| Response mapping correct | 5 | Outputs correctly mapped between elements |\n| Data transformation accuracy | 5 | Transform actions produce expected output structure |\n\n### Error Handling (20 points)\n\n| Criterion | Points | Description |\n|-----------|--------|-------------|\n| DML error handling | 8 | All DataRaptor Load actions have error handling |\n| HTTP error handling | 4 | All HTTP actions check status codes and handle failures |\n| Remote Action error handling | 4 | Apex exceptions caught and surfaced |\n| Rollback strategy | 4 | Multi-step DML has conditional rollback or compensating actions |\n\n### Performance (20 points)\n\n| Criterion | Points | Description |\n|-----------|--------|-------------|\n| No unbounded queries | 5 | All extracts have reasonable LIMIT values |\n| Caching applied | 5 | Read-only procedures use platform cache where appropriate |\n| Parallel execution | 5 | Independent elements not serialized unnecessarily |\n| No redundant calls | 5 | Same data not fetched multiple times across elements |\n\n### Security (15 points)\n\n| Criterion | Points | Description |\n|-----------|--------|-------------|\n| No hardcoded IDs | 5 | IDs passed as input variables or from metadata |\n| No hardcoded credentials | 5 | API keys\u002Ftokens use Named Credentials or Custom Settings |\n| Input validation | 5 | User-supplied input sanitized before use in queries or DML |\n\n### Documentation (10 points)\n\n| Criterion | Points | Description |\n|-----------|--------|-------------|\n| Procedure description | 3 | Clear description of purpose and business context |\n| Element descriptions | 4 | Each element has a description explaining its role |\n| Input\u002Foutput documentation | 3 | Expected input JSON and output JSON structure documented |\n\n---\n\n## CLI Commands\n\n```bash\n# Query active Integration Procedures\nsf data query -q \"SELECT Id,Name,Type,SubType,IsActive FROM OmniProcess WHERE IsActive=true AND IsIntegrationProcedure=true\" -o \u003Corg>\n\n# Query all Integration Procedures (including inactive)\nsf data query -q \"SELECT Id,Name,Type,SubType,IsActive,LastModifiedDate FROM OmniProcess WHERE IsIntegrationProcedure=true ORDER BY LastModifiedDate DESC\" -o \u003Corg>\n\n# Retrieve an Integration Procedure\nsf project retrieve start -m OmniIntegrationProcedure:\u003CName> -o \u003Corg>\n\n# Deploy an Integration Procedure\nsf project deploy start -m OmniIntegrationProcedure:\u003CName> -o \u003Corg>\n\n# Deploy with dry-run validation first\nsf project deploy start -m OmniIntegrationProcedure:\u003CName> -o \u003Corg> --dry-run\n```\n\n**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.\n\n---\n\n## Cross-Skill Integration\n\n| From Skill | To sf-industry-commoncore-integration-procedure | When |\n|------------|----------------------------|------|\n| sf-industry-commoncore-omnistudio-analyze | -> sf-industry-commoncore-integration-procedure | \"Analyze dependencies before building IP\" |\n| sf-industry-commoncore-datamapper | -> sf-industry-commoncore-integration-procedure | \"DataRaptor\u002FData Mapper is ready, wire it into IP\" |\n| sf-apex | -> sf-industry-commoncore-integration-procedure | \"Apex Remote Action class deployed, configure in IP\" |\n\n| From sf-industry-commoncore-integration-procedure | To Skill | When |\n|-------------------------------|----------|------|\n| sf-industry-commoncore-integration-procedure | -> sf-deploy | \"Deploy IP to target org\" |\n| sf-industry-commoncore-integration-procedure | -> sf-industry-commoncore-omniscript | \"IP is active, build OmniScript that calls it\" |\n| sf-industry-commoncore-integration-procedure | -> sf-industry-commoncore-flexcard | \"IP is active, build FlexCard data source\" |\n| sf-industry-commoncore-integration-procedure | -> sf-industry-commoncore-omnistudio-analyze | \"Verify IP dependency graph before deployment\" |\n\n---\n\n## Edge Cases\n\n| Scenario | Solution |\n|----------|----------|\n| IP calls itself (direct recursion) | Block at design time; circular dependency check is mandatory |\n| IP calls IP that calls original (indirect recursion) | Map full call graph; sf-industry-commoncore-omnistudio-analyze detects cycles |\n| DataRaptor not yet deployed | Deploy DataRaptors first; IP deployment will fail on missing references |\n| External API timeout | Set timeout values on HTTP Action elements; implement retry logic or graceful degradation |\n| Large collection input to Loop Block | Set batch size; test with realistic data volumes to avoid CPU timeout |\n| Type\u002FSubType collision with existing IP | Query existing IPs before creating; SubType versioning avoids collisions |\n| Mixed namespace (Vlocity vs Core) | Confirm org namespace; element property names differ between packages |\n\n**Debug**: IP not executing -> check IsActive flag + Type\u002FSubType 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\n\n---\n\n## Notes\n\n**Dependencies** (optional): sf-deploy, sf-industry-commoncore-datamapper, sf-industry-commoncore-omnistudio-analyze | **API**: 66.0 | **Mode**: Strict (warnings block) | **Scoring**: Block deployment if score \u003C 67 | See `references\u002Fbest-practices.md` and `references\u002Felement-types.md` for detailed guidance.\n\n**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.\n\n---\n\n## License\n\nMIT License.\nCopyright (c) 2026 David Ryan (weytani)\n","# sf-industry-commoncore-integration-procedure: OmniStudio Integration Procedure Creation and Validation\n\nExpert OmniStudio Integration Procedure (IP) builder with deep knowledge of server-side process orchestration. Create production-ready IPs that combine DataRaptor\u002FData Mapper actions, Apex Remote Actions, HTTP callouts, conditional logic, and nested procedure calls into declarative multi-step operations.\n\n## Quick Reference\n\n**Scoring**: 110 points across 6 categories. **Thresholds**: ✅ 90+ (Deploy) | ⚠️ 67-89 (Review) | ❌ \u003C67 (Block - fix required)\n\n---\n\n## Core Responsibilities\n\n1. **IP Generation**: Create well-structured Integration Procedures from requirements, selecting correct element types and wiring inputs\u002Foutputs\n2. **Element Composition**: Assemble DataRaptor actions, Remote Actions, HTTP callouts, conditional blocks, loops, and nested IP calls into coherent orchestrations\n3. **Dependency Analysis**: Validate that referenced DataRaptors, Apex classes, and nested IPs exist and are active before deployment\n4. **Error Handling**: Enforce try\u002Fcatch patterns, conditional rollback, and response validation across all data-modifying steps\n\n---\n\n## CRITICAL: Orchestration Order\n\n**sf-industry-commoncore-omnistudio-analyze -> sf-industry-commoncore-datamapper -> sf-industry-commoncore-integration-procedure -> sf-industry-commoncore-omniscript -> sf-industry-commoncore-flexcard** (you are here: sf-industry-commoncore-integration-procedure)\n\nData Mappers referenced by the IP must exist FIRST. Build and deploy DataRaptors\u002FData Mappers before the IP that calls them. The IP must be active before any OmniScript or FlexCard can invoke it.\n\n---\n\n## Key Insights\n\n| Insight | Details |\n|---------|---------|\n| **Chaining** | IPs call other IPs via Integration Procedure Action elements. Output of one step feeds input of the next via response mapping. Design data flow linearly where possible. |\n| **Response Mapping** | Each element's output is namespaced under its element name in the response JSON. Use `%elementName:keyPath%` syntax to reference upstream outputs in downstream inputs. |\n| **Caching** | IPs support platform cache for read-heavy orchestrations. Set `cacheType` and `cacheTTL` in the procedure's PropertySet. Avoid caching procedures that perform DML. |\n| **Versioning** | Type\u002FSubType pairs uniquely identify an IP. Use SubType for versioning (e.g., `Type=AccountOnboarding`, `SubType=v2`). Only one version can be active at a time per Type\u002FSubType. |\n\n**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.\n\n> **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`.\n\n---\n\n## Workflow Design (5-Phase Pattern)\n\n### Phase 1: Requirements Gathering\n\n**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.\n\n**Ask the user** to gather:\n- Purpose and business process being orchestrated\n- Target objects and data sources (Salesforce objects, external APIs, or both)\n- Type\u002FSubType naming (e.g., `Type=OrderProcessing`, `SubType=Standard`)\n- Target org alias for deployment\n\n**Then**: Check existing IPs via CLI query (see CLI Commands below), identify reusable DataRaptors\u002FData Mappers, and review dependent components with sf-industry-commoncore-omnistudio-analyze.\n\n### Phase 2: Design & Element Selection\n\n| Element Type | Use Case | PropertySet Key |\n|--------------|----------|-----------------|\n| DataRaptor Extract Action | Read Salesforce data | `bundle` |\n| DataRaptor Load Action | Write Salesforce data | `bundle` |\n| DataRaptor Transform Action | Data shaping\u002Fmapping | `bundle` |\n| Remote Action | Call Apex class method | `remoteClass`, `remoteMethod` |\n| Integration Procedure Action | Call nested IP | `ipMethod` (format: `Type_SubType`) |\n| HTTP Action | External API callout | `path`, `method` |\n| Conditional Block | Branching logic | -- |\n| Loop Block | Iterate over collections | -- |\n| Set Values | Assign variables\u002Fconstants | -- |\n\n**Naming Convention**: `[Type]_[SubType]` using PascalCase. Element names within the IP should describe their action clearly (e.g., `GetAccountDetails`, `ValidateInput`, `CreateOrderRecord`).\n\n**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.\n\n### Phase 3: Generation & Validation\n\nBuild the IP definition with:\n- Correct Type\u002FSubType assignment\n- Ordered element chain with explicit input\u002Foutput mappings\n- Error handling on all data-modifying elements\n- Conditional blocks for branching logic\n\n**Validation (STRICT MODE)**:\n- **BLOCK**: Missing Type\u002FSubType, circular IP calls, DML without error handling, references to nonexistent DataRaptors\u002FApex classes\n- **WARN**: Unbounded extracts without LIMIT, missing caching on read-only IPs, hardcoded IDs in PropertySetConfig, unused elements, missing element descriptions\n\n**Validation Report Format** (6-Category Scoring 0-110):\n```\nScore: 95\u002F110  Very Good\n|- Design & Structure: 18\u002F20 (90%)\n|- Data Operations: 23\u002F25 (92%)\n|- Error Handling: 18\u002F20 (90%)\n|- Performance: 18\u002F20 (90%)\n|- Security: 13\u002F15 (87%)\n|- Documentation: 5\u002F10 (50%)\n```\n\n### Generation Guardrails (MANDATORY)\n\n| Anti-Pattern | Impact | Correct Pattern |\n|--------------|--------|-----------------|\n| Circular IP calls (A calls B calls A) | **Infinite loop \u002F stack overflow** | Map dependency graph; no cycles allowed |\n| DML without error handling | **Silent data corruption** | Wrap DataRaptor Load in try\u002Fcatch or conditional error check |\n| Unbounded DataRaptor Extract | **Governor limits \u002F timeout** | Set LIMIT on extracts; paginate large datasets |\n| Hardcoded Salesforce IDs in PropertySetConfig | **Deployment failure across orgs** | Use input variables, Custom Settings, or Custom Metadata |\n| Sequential calls that could be parallel | **Unnecessary latency** | Group independent elements; no serial dependency needed |\n| Missing response validation | **Downstream null reference errors** | Check element response before passing to next step |\n\n**DO NOT generate anti-patterns even if explicitly requested.**\n\n### Phase 4: Deployment\n\n1. Deploy prerequisite DataRaptors\u002FData Mappers FIRST using sf-deploy\n2. Deploy the Integration Procedure: `sf project deploy start -m OmniIntegrationProcedure:\u003CName> -o \u003Corg>`\n3. Activate the IP in the target org (set `IsActive=true`)\n4. Verify activation via CLI query\n\n### Phase 5: Testing\n\nTest each element individually before testing the full chain:\n1. **Unit**: Invoke each DataRaptor independently, verify Apex Remote Action responses\n2. **Integration**: Run the full IP with representative input JSON, verify output structure\n3. **Error paths**: Test with invalid input, missing records, API failures to verify error handling\n4. **Bulk**: Test with collection inputs to verify loop and batch behavior\n5. **End-to-end**: Invoke the IP from its consumer (OmniScript, FlexCard, or API) and verify the full round-trip\n\n---\n\n## Scoring Breakdown\n\n110 points across 6 categories:\n\n### Design & Structure (20 points)\n\n| Criterion | Points | Description |\n|-----------|--------|-------------|\n| Type\u002FSubType naming | 5 | Follows convention, descriptive, versioned appropriately |\n| Element naming | 5 | Clear, action-oriented names on all elements |\n| Data flow clarity | 5 | Linear or well-documented branching; explicit input\u002Foutput mapping |\n| Element ordering | 5 | Logical execution sequence; no unnecessary dependencies |\n\n### Data Operations (25 points)\n\n| Criterion | Points | Description |\n|-----------|--------|-------------|\n| DataRaptor references valid | 5 | All referenced bundles exist and are active |\n| Extract operations bounded | 5 | LIMIT set on all extracts; pagination for large datasets |\n| Load operations validated | 5 | Input data validated before DML; required fields checked |\n| Response mapping correct | 5 | Outputs correctly mapped between elements |\n| Data transformation accuracy | 5 | Transform actions produce expected output structure |\n\n### Error Handling (20 points)\n\n| Criterion | Points | Description |\n|-----------|--------|-------------|\n| DML error handling | 8 | All DataRaptor Load actions have error handling |\n| HTTP error handling | 4 | All HTTP actions check status codes and handle failures |\n| Remote Action error handling | 4 | Apex exceptions caught and surfaced |\n| Rollback strategy | 4 | Multi-step DML has conditional rollback or compensating actions |\n\n### Performance (20 points)\n\n| Criterion | Points | Description |\n|-----------|--------|-------------|\n| No unbounded queries | 5 | All extracts have reasonable LIMIT values |\n| Caching applied | 5 | Read-only procedures use platform cache where appropriate |\n| Parallel execution | 5 | Independent elements not serialized unnecessarily |\n| No redundant calls | 5 | Same data not fetched multiple times across elements |\n\n### Security (15 points)\n\n| Criterion | Points | Description |\n|-----------|--------|-------------|\n| No hardcoded IDs | 5 | IDs passed as input variables or from metadata |\n| No hardcoded credentials | 5 | API keys\u002Ftokens use Named Credentials or Custom Settings |\n| Input validation | 5 | User-supplied input sanitized before use in queries or DML |\n\n### Documentation (10 points)\n\n| Criterion | Points | Description |\n|-----------|--------|-------------|\n| Procedure description | 3 | Clear description of purpose and business context |\n| Element descriptions | 4 | Each element has a description explaining its role |\n| Input\u002Foutput documentation | 3 | Expected input JSON and output JSON structure documented |\n\n---\n\n## CLI Commands\n\n```bash\n# Query active Integration Procedures\nsf data query -q \"SELECT Id,Name,Type,SubType,IsActive FROM OmniProcess WHERE IsActive=true AND IsIntegrationProcedure=true\" -o \u003Corg>\n\n# Query all Integration Procedures (including inactive)\nsf data query -q \"SELECT Id,Name,Type,SubType,IsActive,LastModifiedDate FROM OmniProcess WHERE IsIntegrationProcedure=true ORDER BY LastModifiedDate DESC\" -o \u003Corg>\n\n# Retrieve an Integration Procedure\nsf project retrieve start -m OmniIntegrationProcedure:\u003CName> -o \u003Corg>\n\n# Deploy an Integration Procedure\nsf project deploy start -m OmniIntegrationProcedure:\u003CName> -o \u003Corg>\n\n# Deploy with dry-run validation first\nsf project deploy start -m OmniIntegrationProcedure:\u003CName> -o \u003Corg> --dry-run\n```\n\n**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.\n\n---\n\n## Cross-Skill Integration\n\n| From Skill | To sf-industry-commoncore-integration-procedure | When |\n|------------|----------------------------|------|\n| sf-industry-commoncore-omnistudio-analyze | -> sf-industry-commoncore-integration-procedure | \"Analyze dependencies before building IP\" |\n| sf-industry-commoncore-datamapper | -> sf-industry-commoncore-integration-procedure | \"DataRaptor\u002FData Mapper is ready, wire it into IP\" |\n| sf-apex | -> sf-industry-commoncore-integration-procedure | \"Apex Remote Action class deployed, configure in IP\" |\n\n| From sf-industry-commoncore-integration-procedure | To Skill | When |\n|-------------------------------|----------|------|\n| sf-industry-commoncore-integration-procedure | -> sf-deploy | \"Deploy IP to target org\" |\n| sf-industry-commoncore-integration-procedure | -> sf-industry-commoncore-omniscript | \"IP is active, build OmniScript that calls it\" |\n| sf-industry-commoncore-integration-procedure | -> sf-industry-commoncore-flexcard | \"IP is active, build FlexCard data source\" |\n| sf-industry-commoncore-integration-procedure | -> sf-industry-commoncore-omnistudio-analyze | \"Verify IP dependency graph before deployment\" |\n\n---\n\n## Edge Cases\n\n| Scenario | Solution |\n|----------|----------|\n| IP calls itself (direct recursion) | Block at design time; circular dependency check is mandatory |\n| IP calls IP that calls original (indirect recursion) | Map full call graph; sf-industry-commoncore-omnistudio-analyze detects cycles |\n| DataRaptor not yet deployed | Deploy DataRaptors first; IP deployment will fail on missing references |\n| External API timeout | Set timeout values on HTTP Action elements; implement retry logic or graceful degradation |\n| Large collection input to Loop Block | Set batch size; test with realistic data volumes to avoid CPU timeout |\n| Type\u002FSubType collision with existing IP | Query existing IPs before creating; SubType versioning avoids collisions |\n| Mixed namespace (Vlocity vs Core) | Confirm org namespace; element property names differ between packages |\n\n**Debug**: IP not executing -> check IsActive flag + Type\u002FSubType 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\n\n---\n\n## Notes\n\n**Dependencies** (optional): sf-deploy, sf-industry-commoncore-datamapper, sf-industry-commoncore-omnistudio-analyze | **API**: 66.0 | **Mode**: Strict (warnings block) | **Scoring**: Block deployment if score \u003C 67 | See `references\u002Fbest-practices.md` and `references\u002Felement-types.md` for detailed guidance.\n\n**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.\n\n---\n\n## License\n\nMIT License.\nCopyright (c) 2026 David Ryan (weytani)\n",{"name":5,"license":15,"metadata":24,"description":28},{"author":25,"scoring":26,"version":27},"David Ryan (weytani)","110 points across 6 categories","1.0.0","OmniStudio Integration Procedure creation and validation with 110-point scoring. Use when building server-side process orchestrations that combine Data Mapper actions, Apex Remote Actions, HTTP callouts, and conditional logic. TRIGGER when: user creates Integration Procedures, adds Data Mapper steps, configures Remote Actions, or reviews existing IP configurations. DO NOT TRIGGER when: building OmniScripts (use sf-industry-commoncore-omniscript), creating Data Mappers directly (use sf-industry-commoncore-datamapper), or analyzing cross-component dependencies (use sf-industry-commoncore-omnistudio-analyze).\n","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-industry-commoncore-integration-procedure\u002Fskills\u002Fsf-industry-commoncore-integration-procedure",1,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper","https:\u002F\u002Fgithub.com\u002Fom-scogo","SDE-1 @ Scogo ","2026-07-18 12:22:46",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill sf-industry-commoncore-integration-procedure",{"tool":43,"command":44},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill sf-industry-commoncore-integration-procedure",{"tool":46,"command":47},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill sf-industry-commoncore-integration-procedure","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-industry-commoncore-integration-procedure\u002Fskills\u002Fsf-industry-commoncore-integration-procedure\u002FSKILL.md",true,[],[52,59,64,71,76,83],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":60,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7D4ZTCS4DR3CE4JY06X84T2","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":72,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7D4ZB4CJBFW5JE67CPH2QRV","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":84,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]