Skip to main content
Running a Vlocity deployment

Synchronize your source and target's data packs with a few clicks

Tom Smith avatar
Written by Tom Smith
Updated over a week ago

Important to note: From January 2023, users will need a Salesforce Industries add-on license to deploy Vlocity or OmniStudio components. Please, check our Pricing page for licensing details.

Deploying Vlocity changes between a source and target with Gearset can be done in a few clicks. To deploy changes, start from the comparison results between a source and target after you've run a comparison.

Select the changes you want to include, and click NEXT.

Deleted data packs can't be deployed to a Salesforce org, but leaving them unused in your org shouldn't cause any problems. Vlocity data packs can only be deleted manually in an org.

Gearset will automatically check for any missing dependencies, and offer to include them in the deployment. This helps to make sure that the deployment will succeed. To include the dependency, select the missing data pack and click NEXT.

You'll be able to review the changes that Gearset is going to deploy before starting the deployment. At this point, you can give the deployment a friendly name to make it easy to identify why you've ran the deployment. You can associate the deployment with a Jira ticket (or other issue tracking systems) to get status updates about the deployment on that ticket.

Click DEPLOY NOW to deploy the changes to your target org.

When the deployment finishes, you'll see a summary of what's been deployed. Gearset will activate any data packs you’ve deployed, such as OmniScripts or Flex Cards. This activation happens after the deployment, so it may take a few minutes for the data packs to become active in your target.

Did this answer your question?