Verified:Website 𝕏@salesforcedevs GitHub

building-omnistudio-omniscript

Build and validate OmniStudio OmniScripts into OmniProcess and OmniProcessElement hierarchies.

803|289|Updated Nov 7, 2025

Search Tags:#deployment validation #salesforce #omnistudio #omniscript #propertysetconfig #data raptor #integration procedure

Ready to run

npx skills add https://github.com/forcedotcom/sf-skills --skill building-omnistudio-omniscript

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: building-omnistudio-omniscript
Source: https://github.com/forcedotcom/sf-skills/tree/main/skills/building-omnistudio-omniscript
Command: npx skills add https://github.com/forcedotcom/sf-skills --skill building-omnistudio-omniscript

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps you design OmniStudio OmniScripts correctly so guided, multi-step experiences work reliably and deploy without surprises.

Core Features & Use Cases

OmniScript creation from requirements: Turn business process inputs into a structured OmniScript with the right elements and step flow.
PropertySetConfig design & data binding: Configure element JSON (including data paths, validation, conditional logic) so the OmniScript behaves as intended.
120-point build validation & deployment readiness: Run strict scoring checks to catch missing fields, broken references, and orchestration/order issues before you deploy.

Quick Start

Generate an OmniScript for a ServiceRequest called NewCase in English by mapping required Type, SubType, and data sources into steps with validated actions and deployment-ready references.

Frequently Asked Questions about building-omnistudio-omniscript

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I build and validate an OmniScript before deploying to Salesforce?▼

You can build an OmniScript by mapping requirements into an OmniProcess and OmniProcessElement hierarchy, then run a 120-point validation workflow to score deployment readiness. This catches missing fields, broken references, and orchestration issues before deployment.

How do I configure PropertySetConfig data binding for OmniScript elements?▼

Configure PropertySetConfig by defining element JSON with specific data paths, validation rules, and conditional logic. This ensures the OmniScript behaves as intended and properly orchestrates DataRaptors and Integration Procedures across multi-step forms.

What is the best way to structure multi-step forms using OmniStudio OmniScripts?▼

The best way to structure multi-step forms is by mapping business process inputs into a structured OmniScript with dependency-ordered steps and validated actions. This creates reliable guided experiences by wiring element configuration and action logic correctly.

Why does my OmniScript deployment fail due to broken references and missing fields?▼

OmniScript deployment fails when elements have broken references or missing fields. A strict pre-deploy scoring check validates element configuration, action wiring, and dependency ordering to catch these issues and enforce deployment guardrails before release.

Can I use Integration Procedures and DataRaptors within an OmniScript workflow?▼

Yes, you can orchestrate Integration Procedures and DataRaptors within an OmniScript. The Skill handles action wiring and dependency-ordering so interactive processes correctly bind data sources and execute multi-step logic without orchestration errors.