Salesforce Vlocity Interview Questions and Answers.

Q1. What is Vlocity?

Vlocity offers industry specific solutions built natively & additively on Salesforce Platform.

Vlocity offers industry specific solutions for Insurance, Healthcare, Communications, Media & Entertainment, Energy & Utilities and Government.

After being acquired by Salesforce, Vlocity is now part of Salesforce Industries.

Q2. What is OmniStudio?

OmniStudio is a set of drag and drop configuration tools to quickly develop and deploy Industry applications.

OmniStudio Architecture consists of three layers:

  1. The Digital Experience Layer
    1. FlexCards: display contextual information and actions
    2. OmniScripts: guided path to complete a business process
  2. The Service Management Layer
    1. DataRaptors: services for retrieving, transforming, and updating data
    2. Integration Procedures: execute multiple actions in a single server call
  3. The Developer Experience Layer
    1. IDX Build Tool: Command-line tool to  packages and migrates OmniStudio Datapacks
    2. IDX Workbench: Desktop application that enables developers to migrate Datapacks and Salesforce metadata

Q3. What are FlexCards?

FlexCards summarize basic information at a glance, display detailed information on demand, and provide quick access to common tasks that are context-relevant. For example, in a call center scenario, when a call center agent interacts with a customer over the phone, the agent views the customer’s information and launches guided processes from the FlexCard during the call.

Key capabilities of Flex Cards:

  • FlexCards summarize Contextual Information at a glance.
  • FlexCards are the beginning and ending points for customer transactions.
  • Design FlexCards to ensure they meet customer requirements/needs. 
  • FlexCards can be view on Any Device or Channel such as Adobe Experience Manager, or inside a custom web container, like Heroku.
  • A FlexCard can display a combination of internal information from Salesforce and external information from a website or a third-party legacy system.
  • You can Quickly Build FlexCards Using Drag-and-Drop Elements in FlexCard Designer.
  • The FlexCard Designer includes a WYSIWYG editor that lets you control FlexCard layout and style without needing templates.
  • FlexCards can be embedded in Other FlexCards or an LWC OmniScript.
  • FlexCards can be used to display details on demand with Flyouts.
  • FlexCard elements can also be displayed conditionally.

Q4. What is an OmniScript?

An OmniScript gives customers a guided path for completing a business process and serves as a configurable way of creating a seamless customer experience.

For example, consider if a customer wants to:

  • View and update their contact information, which is stored in Salesforce.
  • View their service plan, which is stored in a legacy database.
  • View their bill, which is stored in a billing system; choose to pay it; and select a specific way to pay it.

Q5. What is a DataRaptor?

A DataRaptor is a mapping tool that enables you to read, transform, and write Salesforce data. There are four types of DataRaptor:

  1. DataRaptor Extract – Gets data from one or more Salesforce Object
  2. DataRaptor Load – Saves data to one or more Salesforce Objects
  3. DataRaptor Transform – Manipulates any data that comes from inside or outside Salesforce
  4. DataRaptor Turbo Extract – Gets data from a single Salesforce Object

Q6. What are Integration Prcedures?

Integration Procedures are a way to retrieve, save, and manipulate data behind the scenes. An Integration Procedure is also recommended when you need fast processing of complex data from multiple sources.

Key capabilities of Integration Procedures:

  • Integration Procedures read data from Salesforce, external systems using REST API, and Apex classes.
  • Integration Procedures are called from and return data to OmniScripts and OmniStudio FlexCards. They also serve as data sources for APIs and Apex code.
  • The Integration Procedure’s Response action allows you to trim the data returning to the browser from the server.
  • Integration Procedures process large amounts of data in batches without causing a Salesforce timeout. 

Q7. What are Calculation Procedures?

Calculation Procedures allow complex math to be configured within OmniStudio. Sometimes you need more than a simple mathematical equation, and configuring Calculation Procedures enables you to run just this kind of comprehensive and detailed set of mathematical processing steps. 

The five basic components of Calculation Procedure are:

  • Variables and Constants: Used in calculation steps
  • Calculation Steps: Matrix and Lookup
  • Aggregation Steps: Allow you to use data from an array input where the calculations are run on each element separately
  • Preprocessor Class: Apex classes used to manipulate the input of the calculation
  • Postprocessor Class: Apex classes used to manipulate the output of the calculation

Q8. What are Calculation Matrices?

Calculation Matrices are lookup tables that take a unique input or set of inputs and return an output or set of outputs. A few examples of Calculation Matrices are:

  • An insurance premium matrix that matches characteristics of the insured to policy premiums
  • A weather alert matrix that sets an alert flag based on weather conditions

There are three types of Calculation Matrices:

  • Standard Calculation Matrix: Used when your matrix doesn’t need to be a part of a group or versioned row by row.
  • Grouped Calculation Matrix: Used to group similar matrices with the same Input and Output headers together.
  • Row-Versioned Calculation Matrix: Used if you have a matrix with many rows and may need to change small portions of the data at a time. Each row has its own start date and time

Q9. What is Vlocity CPQ? (Industries CPQ)

Vlocity CPQ (Industries CPQ) is a cloud-based, quote-and-order-capture system that is built natively and additively on the Salesforce platform.  It enables the configuration of product offers. CPQ gives sales teams advanced order capture and guided selling capabilities so that they can offer best-fit products and services to customers across different channels.

Q10. What is Vlocity Enterprise Product Catalog (EPC)?

Enterprise Product Catalog allows you to configure products, product bundles, price rules, availability and eligibility rules. EPC uses product, service and resource model. EPC is compliant with the SID/TM Forum Frameworx model, which is the modelling  standard for the Communications Industry. 


Salesforce Vlocity Interview Questions 1 – 10 | 11 – 20 | 21 – 30


Q11. What is Vlocity Party Model?

Vlocity Party Model is a set of custom object and fields in Vlocity Data Model that defines relationship between people and groups. A party is either a person, a household, a company or organization. In Vlocity each Account and Contact is tracked as a Party. Party records are auto generated in the background.

Q12. What is Vlocity Industry Process Library?

Vlocity Industry Process Library is a library of pre-built Industry specific components available for download. These contain some common Industry processes. If a customer has a use case for which there is already an exiting process library it significantly reduces the development effort for that component. The existing process libraries can be used with minor modifications.

Q13. What is OmniStudio Tracking Service?

The OmniStudio Tracking Service is an event-tracking service that captures details of actions that users perform. You can use the service to track any type of event. For example, you can track the time it takes to complete the steps in an OmniScript to identify process improvements.

The Tracking Service writes data to the Tracking Entry object: VlocityTrackingEntry__c.

Q14. What is a OmniStudio Data Pack?

A DataPack is a collection of components and related functionality that are packaged for migration from one org to another. DataPacks can be used for deployment; that is, to migrate functionality from a sandbox environment to a production environment.

Q15. How can you migrate OmniStudio Data Pack from one sandbox to another sandbox or production org?

IDX Workbench is a desktop application that enables you to migrate OmniStudio DataPacks and Salesforce metadata. It can be used to migrate Data Packs and Salesforce Metadata from one sandbox to Git repository, another sandbox or production org.

Q16. What is OmniOut?

OmniOut can be used to run OmniScripts and FlexCards off-platform on third-party websites with OmniOut for OmniScripts and OmniOut for FlexCards. You can run an OmniScript or FlexCard on your external site by adding the component to the OmniOut project, integrating OmniOut into your application, and deploying your application to your CMS.

Q17. What is Expression Engine?

Expression Engine is an APEX-based formula builder used across multiple areas in OmniStudio, including OmniScripts, DataRaptors, and Integration Procedures. The OmniScript formula builder and attribute rules use a client-side JavaScript expression engine that is evaluated in the browser and allows for fast, real-time applications.

Q18. List OmniScript Best Practices.

  • Reduce the number of fields the user must input information into by prefilling the fields using contextual data
  • Create re-usable OmniScripts
  • Reduce Conditional Views, Merge Fields, Formulas where possible.
  • Run logic on the server where possible, including conditional logic in Integration Procedures and formulas in DataRaptors.
  • Avoid assigning a ContextId within the OmniScript. OmniScript’s ContextId is a reserved key that assigns a Record Id from the URL.

Q19. List Data Raptor Best Practices.

  • Create targeted DataRaptors that only extract or load the data needed for one operation
  • Use relationship notation (queries) whenever possible to pull data from other Objects
  • Try to keep the number of Objects to three or fewer
  • Ensure that all filtering and sorting operations are on indexed fields. The Id and Name fields are always indexed
  • Use caching to store frequently accessed, infrequently updated data

Q20. List Integration Procedure Best Practices.

  • Use Integration Procedures for all data calls to Salesforce
  • Trim the Response data to only get what is needed
  • Use multiple Response Actions with different Execution Conditional Formulas to allow an Integration Procedure to exit early under appropriate conditions
  • Use caching to store frequently accessed, infrequently updated data
  • If possible run Integration Procedures asynchronously

Salesforce Vlocity Interview Questions 1 – 10 | 11 – 20 | 21 – 30


Q21. List OmniStudio Naming Conventions.

  • Data Raptor Names
    • Must be unique within the org
    • No spaces
    • Use camelCase – prefix, Verb, Object and Detail
    • Use an action verb and descriptive nouns
    • Use abbreviations
    • Example: testGetCaseDetails
  • DataRaptor JSON Paths
    • Unique in the DataRaptor
    • Use ASCII characters
    • No spaces (some exceptions for XML)
    • To parse to OmniScript elements the node name must match the element name
    • Use PascalCase
    • Short, descriptive names
    • Abbreviate
    • For Ids, Specify the object – if there is more than one extract from an object type, assign a label to each object
    • Example: CaseDetails
  • FlexCard Names and Authors
    • The combination of Name and Author must be unique
    • Names and Authors can only contain underscores and alphanumeric characters
    • Must begin with a letter, have no spaces, not end with an underscore, and can’t have two consecutive underscores
    • Especially avoid the apostrophe ( ‘ ) such as in a name (e.g. O’Niel)
    • FlexCard and Author names can be changed by cloning the FlexCard
    • Example: CasesClosed
  • OmniScript Type & Sub Type
    • Combination of Type/Sub Type/Language is unique in an org
    • Type must start with a lower-case letter (LWC)
    • No special characters
    • Use camelCase – prefix, Verb, Object and Detail
    • Use an action verb and descriptive nouns
    • Use abbreviations
    • Example: caseManagement/getCaseDetails
  • OmniScript & Integration Procedure Elements
    • Unique in the script
    • Use ASCII characters
    • No spaces (no exceptions)
    • Example: GetCaseDetails

Q22. What Data Sources are available for FlexCards?

FlexCards can use following Data Sources:

  • SOQL Query – Use the Salesforce Object Query Language (SOQL) to search your organization’s Salesforce data for specific information
  • SOSL Search – Use the Salesforce Object Search Language (SOSL) to construct text-based search queries against the search index
  • Apex Remote – Apex Remote data source is used to make a Apex Remote call
  • Apex REST – Apex REST data source is used to make a Apex REST call
  • DataRaptor – DataRaptor data source is used to make calls to Vlocity DataRaptors
  • REST – Uses the standard REST API call
  • Integration Procedures – Integration Procedure data source is used to make calls to Vlocity Integration Procedures
  • Streaming API – Streaming API enables streaming of events using push technology and provides a subscription mechanism for receiving events in near real time.
  • Custom – Uses the sample JSON provided.
FlexCard Data Sources
FlexCard Data Sources

Q23. What are FlexCard Actions?

FlexCard Actions are used to launch or update an OmniScript, navigate to a web page or application, display a flyout, fire an event, or update data field values. Following actions are available for FlexCards:

  • Card – Perform card-level actions, such as reload, update data source, and remove
  • Event
    • Custom – Fire a Custom Event to notify the parent FlexCard of an event occurring
    • PubSub – Fire a PubSub Event to notify another component on a page or application of an event occurring
  • Flyout – Display additional information from a child card, OmniScript, or custom Lightning web component (LWC) in a modal or popover
  • Navigate – Select a target URL or a PageReference type that enables navigation within Lightning Experience, within Communities, or to an external web address
  • OmniScript – Launch an OmniScript from the FlexCard
  • Update OmniScript – Update an OmniScript from a FlexCard embedded as a custom Lightning web component in an OmniScript
  • OmniScript Action – Launch OmniScripts, components, web pages, or external applications from a reusable OmniStudio Action. An OmniStudio Action can launch the same OmniScript from multiple FlexCards

Q24. Explain various OmniScript Element Types.

OmniScripts have following element types:

  • Actions – Actions elements are used for calling on other tools to perform various actions such as getting or saving data, calculating, sending an email etc.
  • Display – Display element is used for displaying text and images on the screen to enhance the usability of the UI
  • Functions – Functions elements are used for performing calculations within the OmniScript, showing conditional messages, and providing geolocation
  • Group – Group element is used for grouping elements together on the UI
  • Inputs – Input elements are used for system or user input or selection
  • OmniScripts – Omniscripts elements are used for reusing any other OmniScript

Q25. Explain various OmniScript Actions Elements.

Actions elements are used for calling on other tools to perform various actions such as getting or saving data, calculating, sending an email etc. Some of the key OmniScript Actions Elements are:

  • DataRaptor Extract Action – Get data from one or more Salesforce records
  • DataRaptor Post Action – Update the data in one or more Salesforce records
  • Integration Procedure Action – Call a series of actions
  • API and HTTP Action – Get, save, or delete data through a web application programming interface
  • Email Action – Populate and send an email as part of an interaction
  • DocuSign Envelope Action and DocuSign Signature Action – Send DocuSign emails for signature or sign DocuSign emails
  • Navigate Action – Send the user back to a previous page after the interaction is complete

Q26. Which OmniScript element will you use to format and display JSON data as a table, using merge codes to dynamically include information such as First Name, Last Name and Address?

Text Block element allows you to add instructions, images, and hyperlinks in an OmniScript.

Q27. What is the advantage of using DataRaptor Turbo Extract as compared to standard DataRaptor Extract?

DataRaptor Turbo Extract retrieves and filters data from a single Salesforce object type with support for fields from related objects. You can filter the data and select the fields to return. Unlike a standard DataRaptor Extract a DataRaptor Turbo Extract doesn’t support formulas or complex output mappings. It has two advantages over a standard DataRaptor Extract.

  • Simpler configuration
  • Better performance at runtime

Q28. What DocuSign Action Elements available in an OmniScript?

OmniScript DocuSign Action Elements use DocuSign Template and require DataRaptor Transform. Following DocuSign Action Elements are supported in OmniScript:

  • DocuSign Envelope Action – Used to send DocuSign emails for signature
  • DocuSign Signature Action – Used to sign documents with DocuSign

Q29. How can you use output of a Calculation Procedure as an input for an aggregation step?

Include in Calculation Output checkbox should be checked in the Calculation Step.

Q30. Which element will you use if you need to convert JSON to XML in an Integration Procedure?

DataRaptor Transform is used to manipulates any data that comes from inside or outside of Salesforce can be used to Convert JSON input to XML output, and vice versa.

Additional Resources

This article will be updated soon, please come back for more Vlocity Interview Questions and Answers!

Additional Salesforce Interview Questions

The Thumbnail Story

The thumbnail picture used in this article was captured by me at Bonneville Salt Flats, Utah. The Bonneville Salt Flats are a densely packed salt pan in Tooele County in northwestern Utah. The area is a remnant of the Pleistocene Lake Bonneville and is the largest of many salt flats located west of the Great Salt Lake.

Please Leave a Comment