Sf Industry Commoncore Integration Procedure
Scaffold Salesforce OmniStudio Integration Procedure elements—DataRaptor Extract actions, Set Values steps, and parent OmniProcess metadata—from JSON patterns.
Overview
Sf-industry-commoncore-integration-procedure is an agent skill for the Build phase that provides OmniStudio Integration Procedure JSON templates for DataRaptor extracts, Set Values, and OmniProcess headers.
Install
npx skills add https://github.com/jaganpro/sf-skills --skill sf-industry-commoncore-integration-procedureWhat is this skill?
- DataRaptor Extract Action element with bundle, failOnStepError, and vlcSI property set
- Set Values element template with ElementValueMap output mapping
- Parent OmniProcess stub for IsIntegrationProcedure with WebComponentKey path
- SequenceNumber and Level fields for ordered step placement
- Credits OmniStudio community patterns for Integration Procedure design
- Templates cover 3 IP artifacts: DataRaptor Extract Action, Set Values element, and parent OmniProcess
- PropertySetConfig examples include failOnStepError and chainOnStep flags
Adoption & trust: 870 installs on skills.sh; 418 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are authoring Salesforce Integration Procedures but struggle to format OmniProcessElement records and PropertySetConfig JSON without deployment errors.
Who is it for?
Salesforce OmniStudio developers implementing Industry Cloud integration procedures with agent-assisted metadata drafting.
Skip if: Teams only building Lightning Web Components or REST Apex with no OmniStudio IPs, or beginners unfamiliar with DataRaptors and OmniProcess lifecycle.
When should I use this skill?
You are defining or extending a Salesforce OmniStudio Integration Procedure with DataRaptor Extract or Set Values elements.
What do I get? / Deliverables
You get ordered IP element and parent process JSON stubs aligned to OmniStudio conventions, ready to customize with your bundle and field names.
- OmniProcessElement JSON for extract and set-value steps
- OmniProcess header JSON for new Integration Procedure
Recommended Skills
Journey fit
Industry Cloud Integration Procedures are authored during implementation when you compose server-side OmniStudio flows. IP element JSON (sequence, PropertySetConfig, bundle names) is backend integration work on Salesforce, not storefront or marketing tasks.
How it compares
OmniStudio IP scaffolding templates—not a generic Salesforce Apex or Flow authoring skill.
Common Questions / FAQ
Who is sf-industry-commoncore-integration-procedure for?
OmniStudio and Industry Cloud implementers who need repeatable JSON patterns for Integration Procedure elements when working with AI coding agents.
When should I use sf-industry-commoncore-integration-procedure?
During Build integrations when you create or extend Integration Procedures with DataRaptor Extract and Set Values steps before activation and testing in a Salesforce org.
Is sf-industry-commoncore-integration-procedure safe to install?
It outputs metadata-shaped JSON only; validate in a sandbox and review the Security Audits panel on this Prism page before trusting third-party skill packages.
SKILL.md
READMESKILL.md - Sf Industry Commoncore Integration Procedure
{ "OmniProcessId": "{{ParentProcessId}}", "Name": "{{ElementName}}", "Type": "DataRaptor Extract Action", "Description": "{{Description}}", "IsActive": true, "Level": 0, "SequenceNumber": {{SequenceNumber}}, "PropertySetConfig": "{\"bundle\":\"{{DataRaptorName}}\",\"chainOnStep\":false,\"disableUniqueSFDCObjectCheck\":false,\"failOnStepError\":true,\"ignoreCache\":false,\"postTransformBundle\":\"\",\"preTransformBundle\":\"\",\"remoteOptions\":{},\"responseJSONNode\":\"\",\"responseJSONPath\":\"\",\"sendOnlyFailedResponse\":false,\"vlcSI\":{\"bundleName\":\"\",\"interfaceName\":\"\",\"remoteMethodName\":\"\"}}" } { "OmniProcessId": "{{ParentProcessId}}", "Name": "{{ElementName}}", "Type": "Set Values", "Description": "{{Description}}", "IsActive": true, "Level": 0, "SequenceNumber": {{SequenceNumber}}, "PropertySetConfig": "{\"ElementValueMap\":{\"{{OutputKey}}\":\"{{OutputValue}}\"},\"chainOnStep\":false,\"failOnStepError\":true}" } { "Name": "{{Type}}_{{SubType}}", "Type": "{{Type}}", "SubType": "{{SubType}}", "Language": "English", "VersionNumber": 1, "IsActive": false, "IsIntegrationProcedure": true, "Description": "{{Description}}", "PropertySetConfig": "{\"persistentComponent\":true,\"trackingCustomData\":{},\"enableLWCRuntime\":true}", "WebComponentKey": "{{Type}}/{{SubType}}/English/1" } # Credits & Acknowledgments This skill was built upon the collective wisdom of the Salesforce OmniStudio community. We gratefully acknowledge the following authors and resources whose ideas, patterns, and best practices have shaped this skill. --- ## Authors & Contributors ### Jag Valaiyapathy **sf-skills Project Creator** Key contributions: - sf-skills framework architecture and skill patterns - Scoring rubric design (110-point system) - Cross-skill orchestration model - OmniStudio skill suite design ### David Ryan (weytani) **Primary Contributor — sf-industry-commoncore-integration-procedure** — [GitHub](https://github.com/weytani) Key contributions: - Integration Procedure element type reference - Error handling and rollback patterns - Caching strategy documentation - Best practices consolidation --- ## Official Salesforce Resources ### Salesforce OmniStudio Documentation **[help.salesforce.com](https://help.salesforce.com/s/articleView?id=sf.os_integration_procedures.htm)** Key contributions: - Integration Procedure configuration reference - Element type definitions and PropertySetConfig properties - OmniProcess data model documentation - Core namespace migration guidance ### Salesforce Trailhead — OmniStudio Modules **[trailhead.salesforce.com](https://trailhead.salesforce.com/en/content/learn/modules/omnistudio-integration-procedures)** Key contributions: - Integration Procedure fundamentals - Hands-on exercises for element configuration - DataRaptor and IP chaining patterns - OmniStudio Developer certification prep material ### Salesforce Architects **[architect.salesforce.com](https://architect.salesforce.com/)** Key contributions: - OmniStudio architecture patterns - Performance and scalability guidance - Enterprise integration strategies --- ## Community Resources ### UnofficialSF Team **[UnofficialSF.com](https://unofficialsf.com/)** Key contributions: - OmniStudio community resources and tutorials - Integration Procedure pattern documentation - DataRaptor best practices that inform IP design ### Salesforce Ben **[salesforceben.com](https://www.salesforceben.com/)** Key contributions: - OmniStudio overview articles - Integration Procedure vs Flow comparison guides - Practical implementation tutorials ### Salesforce Stack Exchange **[salesforce.stackexchange.com](https://salesforce.stackexchange.com/)** Key contributions: - Community Q&A on Integration Procedure issues - PropertySetConfig troubleshooting solutions - DataRaptor-IP integration patterns - Core namespace migration solutions ### Vlocity / Industries CPQ Community **Various community