omnistudio-omniscript-generate

You can generate deployment-ready OmniScript metadata by providing the Type, SubType, Language, and target org. The process validates PropertySetConfig settings, checks active Integration Procedure and DataRaptor references, and ensures deployment-safe activation handling.

Validating OmniScript structure involves evaluating it against a 120-point rubric covering data integration, error handling, performance, and security. This verifies prerequisite dependencies, checks duplicate Type, SubType, and Language values, and ensures accurate PropertySetConfig settings.

Yes, the sf CLI is required as a dependency to validate and deploy OmniStudio OmniScripts. The Skill uses it to verify accurate Integration Procedure and DataRaptor references, check duplicate combinations, and manage deployment-safe activation.

Yes, you can map dependencies for multi-step guided forms in Salesforce. The Skill designs guided digital experiences by mapping active Integration Procedure and DataRaptor references, evaluating element selection, and verifying PropertySetConfig settings.

OmniScript deployment fails due to duplicate Type, SubType, and Language combinations because these values must be unique. The Skill performs duplicate checks and deployment readiness validation to prevent these conflicts and ensure deployment-safe activation handling in the target org.