Salesforce Certified OmniStudio Consultant – Complete Winter '26 Guide

FlexCards: Displaying Data Contextually

FlexCards display contextual information from Salesforce records or external data sources on a card-style UI. They can be embedded in Experience Cloud pages, Lightning record pages, or other OmniStudio components. Child FlexCards show related record data. Custom actions on FlexCards trigger OmniScripts, open Lightning components, or navigate to records. Data sources: Salesforce SOQL (DataRaptor Extract), Integration Procedures, or Apex. The consultant designs FlexCards to surface the right information in the right context — reducing the need for users to navigate away to find related data.

OmniScripts: Guided User Experiences

OmniScripts create guided, multi-step processes for users — similar to a wizard. Steps and groups organise the experience. Elements: Text Input, Select (dropdown), Date Picker, Checkbox, Lookup, Navigation (radio buttons), Formula, and more. Conditional display rules show or hide elements based on prior responses. Data sources populate dropdown options and pre-fill fields. Custom validation rules enforce business rules before moving to the next step. The consultant designs OmniScripts for complex data entry processes like customer onboarding, service requests, or insurance claims.

Integration Procedures: Backend Orchestration

Integration Procedures (IPs) orchestrate backend calls without user interaction — they are called by OmniScripts, FlexCards, or other automated processes. Actions within an IP: DataRaptor Extract (query Salesforce), DataRaptor Load (write to Salesforce), HTTP Action (call external REST API), Apex Action (call custom Apex), Set Values (assign variables). IPs support conditional branching and looping. The consultant designs IPs to aggregate data from multiple sources, transform it, and return structured results — keeping business logic out of the UI layer.

DataRaptors: Data Access and Transformation

DataRaptors are data transformation tools with four types: Extract (read from Salesforce — returns a structured JSON), Load (write to Salesforce — creates or updates records), Transform (map and reshape data between structures without touching Salesforce), Turbo Extract (high-performance read for simple queries using SOQL). DataRaptor Extract replaces SOQL in OmniStudio components. Load handles parent-child record creation in a single operation. The consultant selects the appropriate DataRaptor type based on whether the operation reads, writes, or transforms data.

OmniStudio Architecture in Industry Clouds

OmniStudio is the foundation for Salesforce Industry Clouds (Health Cloud, Financial Services Cloud, Communications Cloud, Energy & Utilities). Industry-specific FlexCards and OmniScripts come pre-built with the industry cloud packages — the consultant configures and extends them rather than building from scratch. OmniStudio components integrate with Salesforce standard objects and industry-specific data models. Business Rules Engine (BRE) provides declarative if-then rules that drive OmniScript branching without hard-coding logic. The consultant understands how OmniStudio connects to the broader industry cloud architecture.

Tool Selection Framework

Know when to use each OmniStudio tool: FlexCards for contextual data display, OmniScripts for guided user processes, DataRaptors for Salesforce data integration, and Integration Procedures for complex orchestration.

Business Process to OmniScript Mapping

Know how to decompose a business process into OmniScript steps, identify reusable components, and design the data flow between steps. Understand when sub-OmniScripts improve reusability.

Data Integration Architecture

Know when to use DataRaptor Extract vs. Integration Procedure for data retrieval, how to handle complex data transformations, and when to call external APIs from Integration Procedures.

FlexCard Use Cases

Know common FlexCard use cases: account/contact dashboards, case summaries, 360-degree customer views. Understand how FlexCard states manage different data scenarios (loading, empty, error, data).

Performance & Scalability

Know best practices for OmniStudio performance: minimizing DataRaptor steps, using Turbo Extract for simple reads, caching Integration Procedure results, and structuring OmniScripts to minimize server calls.