Vlocity

Vlocity, as of June 1, 2020, is now a Salesforce company. Vlocity is a set of applications built solely on the Salesforce platform and caters to a number of industries including healthcare, energy, government, entertainment, and insurance. Vlocity is popular among many of our healthcare clients including Anthem.

For best tracking and visibility, it’s recommended to set a metadata folder path for a repository. This can be completed through the use of the branch settings column in the Repository details. This will enable the metadata to be placed in the specified directory rather than the root directory. This should be completed before any baseline and commits as part of your VC Repo’s registration.

Branching baseline can also be used for periodical metadata backups into a separate backup repository, which can be used to track unplanned manual changes in the orgs.

Branching Baseline is one of the first steps in seeding the master branch. ARM has the ability to populate the Vlocity specific metadata into the master branch using Branching Baseline methodology. These are key metadata items that are extracted as part of the Baseline process for Vlocity. Branching Baseline has the ability to seed master branches for Salesforce-specific Metadata and Vlocity-specific metadata.

  • Attachment

  • AttributeAssignmentRule

  • AttributeCategory

  • CalculationMatrix

  • CalculationMatrixVersion

  • CalculationProcedure

  • CalculationProcedureVersion

  • Catalog

  • ContextAction

  • ContextDimension

  • ContextScope

  • ContractType

  • DataRaptor

  • Document

  • DocumentClause

  • DocumentTemplate

  • EntityFilter

  • FlexCard

  • IntegrationProcedure

  • InterfaceImplementation

  • ItemImplementation

  • ManualQueue

  • ObjectClass

  • ObjectContextRule

  • ObjectLayout

  • OmniScript

  • OrchestrationDependencyDefinition

  • OrchestrationItemDefinition

  • OrchestrationPlanDefinition

  • Pricebook2

  • PriceList

  • PricingPlan

  • PricingVariable

  • Product2

  • Promotion

  • QueryBuilder

  • Rule

  • StoryObjectConfiguration

  • System

  • TimePlan

  • TimePolicy

  • UIFacet

  • UISection

  • VlocityAction

  • VlocityAttachment

  • VlocityCard

  • VlocityFunction

  • VlocityPicklist

  • VlocitySearchWidgetSetup

  • VlocityStateModel

  • VlocityUILayout

  • VlocityUITemplate

  • VqMachine

  • VqResource

Seeding a master repository within ARM is possible for both Salesforce and Vlocity metadata as displayed below:

Upon successfully executing the Branching Baseline by selecting Salesforce and Vlocity for the retrieval type all metadata is placed into the master repository. The Salesforce metadata should be placed in the src directory within the master repository. Additionally, a vlocity.yaml file is created as part of the baseline process. Here is an example of a vlocity.yaml file:

Project path: ./autorabit_alldefault_vlocity_buildmanifest

  • Attachment

  • AttributeAssignmentRule

  • AttributeCategory

  • CalculationMatrix

  • CalculationMatrixVersion

  • CalculationProcedure

  • CalculationProcedureVersion

  • Catalog

  • ContextAction

  • ContextDimension

  • ContextScope

  • ContractType

  • DataRaptor

  • Document

  • DocumentClause

  • DocumentTemplate

  • EntityFilter

  • FlexCard

  • IntegrationProcedure

  • InterfaceImplementation

  • ItemImplementation

  • ManualQueue

  • ObjectClass

  • ObjectContextRule

  • ObjectLayout

  • OmniScript

  • OrchestrationDependencyDefinition

  • OrchestrationItemDefinition

  • OrchestrationPlanDefinition

  • Pricebook2

  • PriceList

  • PricingPlan

  • PricingVariable

  • Product2

  • Promotion

  • QueryBuilder

  • Rule

  • StoryObjectConfiguration

  • System

  • TimePlan

  • TimePolicy

  • UIFacet

  • UISection

  • VlocityAction

  • VlocityAttachment

  • VlocityCard

  • VlocityFunction

  • VlocityPicklist

  • VlocitySearchWidgetSetup

  • VlocityStateModel

  • VlocityUILayout

  • VlocityUITemplate

  • VqMachine

  • VqResource maxDepth: -1 autoUpdateSettings: true separateMatrixVersions: true

In addition to the vlocity.yaml file, the Vlocity metadata is retrieved and placed into the autorabit_alldefault_vlocity_build folder.

Last updated