For the managed package runtime, before you can deploy components, you must specify the source, the target, and the objects to be deployed. The source can be an org, a Project object in an org, a JSON file, the Vlocity Process Library, or a Git repository. The target can be an org or a Git repository.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
You can also save to a JSON file when you deploy. See Save Objects to a JSON File (Managed Package).
- Configure for Deployment Between Orgs (Managed Package)
For the managed package runtime, you must configure a source org and a target org. Both orgs should have the same Omnistudio runtime. - Configure an Org Using a Community User Login (Managed Package)
For the managed package runtime, when you configure an org for running Test Procedures, you can specify a Salesforce Community and authenticate as a Community user. This is especially useful for running Test Procedures in which user access affects the results. - Configure a Project Object (Managed Package)
For the managed package runtime, after creating a Project object, configure the object. - Configure for Deployment from a JSON File (Managed Package)
For the managed package runtime, you can specify a DataPack as a Source and deploy to either an org or a Git repository Target. The DataPack must include all the objects you want to deploy in a single JSON file. - Configure for Deployment from the Salesforce Industries Process Library (Managed Package)
For the managed package runtime, you can deploy DataPacks from the Salesforce Industries Process Library to a Vlocity org. - Configure for Deployment Between a Repository and an Org (Managed Package)
For the managed package runtime, you can use a Git repository as a Source or Target in IDX Workbench, deploying DataPacks from the repository to a Vlocity org or the reverse. - Give a Bitbucket Git Repository Access to IDX Workbench (Managed Package)
For the managed package runtime, you can give IDX Workbench access to a Bitbucket repository using a password. - Create Additional Projects (Managed Package)
For the managed package runtime, after you have created your first project, you can create additional projects. - Switch Between Projects (Managed Package)
For the managed package runtime, you can switch from your current project to another existing project. - Handle a Login Failed Message (Managed Package)
For the managed package runtime, if you refresh a Source or Target org and see aLogin Failed ... Please Login Againmessage, you can fix the error. - Use a .vlocityignore File to Exclude Objects (Managed Package)
For the managed package runtime, you can specify a list of object types and/or objects to ignore in all the projects that use the same repository.