> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm-1/troubleshoot/best-practices/vlocity.md). # Vlocity Vlocity, as of June 1, 2020, is now a Salesforce company. Vlocity is a set of applications built solely on the Salesforce platform that caters to a number of industries, including healthcare, energy, government, entertainment, and insurance. Vlocity is popular among many of our healthcare clients. 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](https://www.autorabit.com/blog/how-to-back-up-your-metadata-in-salesforce/) 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](/product-guides/arm/integration-and-plugins/vlocity.md). 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. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://knowledgebase.autorabit.com/product-guides/arm-1/troubleshoot/best-practices/vlocity.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.