Salesforce Certified OmniStudio Consultant Exam Guide.
Salesforce OmniStudio Consultant (formerly known as Vlocity Platform Consultant) credential is intended for individuals who have experience consulting on building cloud applications using OmniStudio tools in a customer-facing role.
Salesforce Certified OmniStudio Consultant is probably one of the easiest Salesforce Certification.
1. About the Salesforce OmniStudio Consultant Exam
- Content: 60 scored, multiple-choice/multiple-select questions and up to 5 non-scored questions
- Time allotted to complete the exam: 105 minutes
- Passing score: 63% (38 out of 60 Questions)
- Registration fee: USD 200, plus applicable taxes as required per local law
- Retake fee: USD 100, plus applicable taxes as required per local law
- Prerequisite: None
2. Exam Outline
FlexCards: 23%
- Explain the capabilities, use cases and purpose of using FlexCards.
- Design FlexCards to ensure they meet customer requirements/needs.
- Collect and group the customer 360 Information required to show to an end user. (Console, FlexCards)
OmniScripts: 27%
- Explain the basic structure of an OmniScript.
- Validate developed OmniScript processes to ensure client expectation alignment.
- Identify business process step requirements and map them to OmniScript Components required to implement them.
Data Tools: 23%
- Explain the purpose and benefits of Integration Procedures and DataRaptors.
- Design Integration Procedures and related DataRaptors.
- Describe the benefits of using Calculation Matrices and Calculation Procedures and provide real examples.
Best Fit Solutioning: 27%
- Gather, analyze, and simplify business requirements in order to design solutions using OmniStudio tools following best practices.
- Map process requirements to OmniStudio capabilities and explain the interaction between them.
- Create fit/gap analyses between requirements and OmniStudio capabilities.
3. Salesforce OmniStudio Consultant Certification Exam Guide
4. OmniStudio Trail
5. Salesforce OmniStudio Consultant Certification Exam Trailmix
Prepare for Your Salesforce OmniStudio Consultant Credential
6. OmniStudio Documentation PDF
7. Important Topics for Salesforce OmniStudio Consultant Certification Exam
7.1 FlexCards: 23% (14 Questions)
- OmniStudio FlexCards display contextual information in an at-a-glance format and provide access to relevant tasks for the displayed data.
- 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.
- FlexCards 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 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
- Session Variable allows you to variable that allows you to store values from data sources or external systems and access them globally on a FlexCard
- There can be 12 columns on a FlexCard Grid
- Industries Console – helps provide 360 degrees view of the customer
7.2 OmniScripts: 27% (16 Questions)
- Explain the basic structure of an OmniScript.
- Validate developed OmniScript processes to ensure client expectation alignment.
- Identify business process step requirements and map them to OmniScript Components required to implement them.
- OmniScript 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 – OmniScript elements are used for reusing any other OmniScript
- OmniScript 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
- 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
7.3 Data Tools: 23% (14 Questions)
- Integration Procedures – 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.
- DataRaptors – A DataRaptor is a mapping tool that enables you to read, transform, and write Salesforce data
- There are four types of DataRaptor:
- DataRaptor Extract – Gets data from one or more Salesforce Object
- DataRaptor Load – Saves data to one or more Salesforce Objects
- DataRaptor Transform – Manipulates any data that comes from inside or outside Salesforce
- DataRaptor Turbo Extract – Gets data from a single Salesforce Object
- Calculation Matrices – Calculation Matrices are lookup tables that take a unique input or set of inputs and return an output or set of outputs
- 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
- 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
7.4 Best Fit Solutioning: 27% (16 Questions)
- Gather, analyze, and simplify business requirements in order to design solutions using OmniStudio tools following best practices.
- 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.
- DataRaptor 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
- 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
- Map process requirements to OmniStudio capabilities and explain the interaction between them.
- Create fit/gap analyses between requirements and OmniStudio capabilities.
- IDX Build Tool: Command-line tool to packages and migrates OmniStudio Datapacks
- IDX Workbench: Desktop application that enables developers to migrate Datapacks and Salesforce metadata
- Data Raptor Naming Conventions
- 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 Naming Conventions
- 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 Naming Convention
- 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 Naming Convention
- 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 Naming Convention
- Unique in the script
- Use ASCII characters
- No spaces (no exceptions)
- Example: GetCaseDetails
