Industries/Vlocity terms Glossary

Since Vlocity was acquired by Salesforce in February 2020 and rebranded as Salesforce Industries, there can be some confusion around the terms used around Vlocity and Industries.

Think of Industries as the packaged solution, and Vlocity as the building blocks used to create and maintain this solution.

Here, we’ve outlined some key terms you might encounter throughout Vlocity development, and what they refer to.

This is where you create Vlocity data packs.

This is where you can view records (e.g. Accounts)

Sometimes called Vlocity Card. A piece of UI that will appear in OmniStudio Console. The UI will use data from an integration procedure or a data mapper, or you can embed FlexCards within each other.

A data source for a FlexCard. It is similar to a flowchart where you give some input and it does a series of steps to give an output. For example, you might give an account ID as input, and it will use a DataMapper to extract some fields from that account. Alternatively, you might give it a contact ID, and it will pull the weather for the contactʼs home address from a third party service.

This transforms data from one format to another. It might take data from an Account record, and then turn that data into a JSON format which can be used as the input for an IntegrationProcedure or a FlexCard.

For example, the output of a DataMapper for an account might look like:

{

"Name": "Gearset",

"NumberOfEmployees": 150,

...

}

This is similar to a wizard for getting a user to fill out information. It can ask for different data based on your responses. The typical example we would use to explain this would be imagining something like the form you fill out to compare health insurance plans.