You are here:
Tool Considerations for Deploying Omnistudio Components
Select the tool for deploying components based on what you’re deploying, the data model used in the source and target orgs, and the Omnistudio runtime used in the source and target orgs. The source and target orgs can be sandboxes, development orgs, or production orgs.
We recommend that you use Salesforce CLI for deploying Omnistudio components between orgs when you’re on Omnistudio standard runtime with standard objects.
Salesforce CLI is a Salesforce standard deployment tool. It caters across:
- Omnistudio components such as Omniscripts, Flexcards, Integration Procedures, and Data Mappers.
- Other Salesforce components such as Business Rules Engine.
- Metadata such as FlexiPage, PermissionSet, Omnistudio Lightning Web Components, and entities.
Salesforce CLI works only with standard objects in the source org and with standard objects and standard runtime in the target org. To learn more about the differences between Salesforce CLI and Build Tool, see Deployment of Omnistudio for Managed Packages Components Between Orgs.
Deployment using Salesforce CLI provides these benefits:
- Consistency: One standard deployment tool for all your deployment needs. Ensures consistent deployments across different environments, minimizing discrepancies.
- No learning curve: For users familiar with command-line interfaces, Salesforce CLI provides an intuitive way to manage deployments. Users aren't required to learn complex UIs or tools.
