Vlocity Integration

Updated 3 weeks ago by Copado Solutions

Copado's Vlocity integration allows you to include Vlocity metadata in the same release management process as the one for standard Salesforce metadata with a complete Git version control.

While working with Copado and Vlocity, you are able to promote and deploy Vlocity configurations in the same way as for Salesforce metadata, taking advantage of Copado's quality gates and flexibility. 

Vlocity configurations/metadata is available to retrieve and commit to the repository, or to promote and deploy without version control (org to org). You can see Vlocity metadata in the same way you do with Salesforce metadata, for instance in Org Credential, Snapshot page or Commit Changes.


  • Copado fully enabled user.
  • Vlocity feature activated for your Copado instance.
    • If the feature is not enabled contact your sales executive.
  • Vlocity  Metadata Visibility
    • Records (configurations) permission.

Onboarding Vlocity Integration Strategies

If you are currently working with Copado and did not do the initial setup (Production Snapshot) including Vlocity metadata, you can follow this strategy:

  1. Commit  to a user story all Vlocity metadata with Production as a source environment
    1. Copado will now include the Vlocity metadata in your Git repository.
      You can use an org credential with visibility to Vlocity metadata only to reduce chances of committing other metadata. 
  2. Back-promote the user story to all the lower environments to sync Vlocity metadata in all the environments and branches.
This strategy will back-promote the current status of your Vlocity configuration in Production. Work in progress in Vlocity configurations will be overwritten in lower environments.

If you are currently working with Copado and did not do the initial setup but your lower environments are aware of Vlocity configurations and  have work in progress, you can follow this strategy:

  1. Create an independent auxiliary Git branch in your Git repository. 
  2. Create a Snapshot record:
    1. Select the Production org credential.
    2. Write the auxiliary branch name.
    3. From the advanced metadata, select only Vlocity Metadata.
    4. Save and click on Create Snapshot Now.
After completion, from your Git repository manually merge the new Vlocity folder into your master branch. In order to achieve this, you can create a pull-request from the auxiliary branch to master and merge.   

Each time a new user story gets created and changes are committed, changes will be merged into the source environment until everything is in sync.

Vlocity Dependencies

If you would like to resolve Vlocity dependencies before a commit, you can select the components you would like to commit and then click on Get Vlocity dependencies in the Commit Changes page. After completion of the job, you will see in the Selected Metadata tab your original selections plus the dependencies needed, so that you can commit and deploy them together.

How did we do?