Salesforce OmniStudio Development - Hands-On Guide

Understand the three-layer Omni Studio architecture—digital experience layer, service management layer, and developer experience layer—and how flex cards, Omniscript, and data mappers enable low-code workflows in Salesforce.

Sign up for a personal revenue cloud management org with Omni Studio enabled. Verify your email and set your password to access the Omni Studio app and Omni Script components.

Dynamically apply filters in a turbo extract data mapper by using a dynamic contact id variable, testing with input parameters and Velocity environment variables in Omni Studio.

Learn to use extract interface type in OmniStudio with data mapper to fetch accounts with related contacts and owner, applying dynamic filters, mapping JSON outputs, and addressing output duplication.

Use the data mapper to set extract paths like accounts: contacts and accounts: owner, mapping account, contact, and owner fields to build a nested json output.

Transform a json input into a policy-rooted json output with OmniStudio data mapper, mapping annual premium, policy number, status, policy name, and deriving policyholder and beneficiary names from contacts.

Map input JSON from multiple sources into a unified customer JSON. Calculate a customer score from sentiment score and phone data, then derive engagement level to shape output fields.

Create your first flex card in Omni Studio by wiring a Soql data source to the contact object, displaying name, email, phone, and title with previews and optional filters.

Extend a flex card to display contact names, add a navigate button that opens the contact record in a new window, and embed the card in the account detail page.

View opportunity history in a modal by adding a view opportunity history action to the parent flex card, which opens a child history card as a fly out modal.

Modify a flex card to add collapsible asset lists and multi-state logic based on status and expiry, including a buy new asset action when no records exist.

Explore OmniStudio's omniscript, a drag-and-drop, low-code tool to build guided front-end processes, data integrations, and self-service flows for industry solutions.

Create your first Omniscript to input account details, map fields with a data mapper to create the account, and navigate to the newly created account record.

Create omni script to fetch account by record ID with data mapper extract, show read-only and editable fields, save updates via data mapper post action, and return to account page.

Create a flex card for account information inside an omni script, passing the record id to fetch and display account details via SQL queries or a data mapper.

Configure a flex card to host a drop-down menu and open Omniscripts from actions, passing the account id via the data mapper to edit or create related accounts.

Set values in OmniScript pre-populates fields, updates JSON nodes, and prepares data for actions like integration procedures and data mappers, using static or dynamic values and merge fields with ampersand.

Pass data from OmniScript to a weather information flex card by encoding the city input, binding current and location details, and displaying icons and condition text.

Learn to pass selected flex card records to an Omniscript via a custom event and update action, enabling display and downstream routing to a data mapper transform or integration procedure.

Learn to expose Apex classes to OmniScript by creating a global, callable class with a call method, handling input and output, and using integration procedures.

Configure a standard select element in OmniStudio to display account picklist values without apex code by binding to account.rating and account.active.

Explore how to build a lookup component in omni script that dynamically fetches s object or picklist values, filters by context, and maps jsonpath results for data-driven selections.

Configure a type ahead block in Omniscript to search accounts using a data mapper extract, display account names, and return the selected account id for downstream processes.

Explore key Omniscript elements and properties, including the step chart, cancel options, messaging and formulas, and action blocks to run actions concurrently with practical previews.

Discover how integration procedures orchestrate multi-step actions for data retrieval, form pre-fill, and updating Salesforce and external systems using data mapper, http actions, and Apex classes when needed.

Explore how to design your first Salesforce OmniStudio integration procedure by mapping input variables to data mapper extracts, using data sources and filters to query account records via various interfaces.

Create your first integration procedure using a data mapper extract to fetch account details by ID, configure input parameters, and return selected fields via a response action.

learn to use an integration procedure inside Omniscript to load account details via data extract, create a case record with data mapper load interface, and navigate to the created record.

Extend omni script with an integration procedure to read account information and create a case with priority, origin, type, subject, and description via a typeahead contact selector.

Learn to debug send and response transformations in OmniScript using the action debugger to inspect requests, rename JSON node, and verify account creation with step account vs step account one.

Learn to make api calls via integration procedures by sending a json payload (account data and contacts) to an external Salesforce org, using named credentials and send and response transformations.

Create an omniscript that collects account and contact data and maps it to the external api payload using a data mapper transform for an integration procedure.

Convert a json array with a data mapper transform; map contact phone to phone. Then use an integration procedure to create accounts and contacts via api call; validate state name.

Learn how the loop block in an integration procedure iterates a list of records, uses data mapper extracts and set values, and returns outputs through additional loop output and response.

Learn how to implement a try-catch block in an integration procedure to catch data mapper post errors, configure failure responses, and optionally terminate or silently fail.

Explore advanced error handling in Salesforce OmniStudio integration procedures by adding a pre-try block data mapper, simulating failures, and enabling rollback on error to revert prior steps.

Learn to restrict access to integration procedures in Salesforce OmniStudio. Apply custom permissions and permission sets, assign them to users, and test role-based or row-level access with Workbench.

Configure access at integration procedure and data mapper levels using permission sets and custom permissions. Verify access with a preview to confirm permissions and secure backend operations.

Install and configure Visual Studio Code and the Salesforce CLI to start developing Lightning web components. Install extensions such as Salesforce Extension Pack, auto close tag, and bracket colorizer.

Learn to pass data from omni script to a lightning web component by configuring @api inputs, mapping parameters with kebab-case names, and testing with merge fields.

Embed a flex card inside a lightning web component to display account classification from an integration procedure using a record ID, configuring the flex card name accordingly.

Learn to persist data across OmniScript screens by using Omni JSON data in a Lightning web component, with safe navigation and conditional population of first name and last name.

Migrate OmniStudio changes from a source org to a target org using IDC's workbench, configure a project, select data packs, and migrate with dependencies.

Refresh and migrate changes in data mappers and new components with the IDE workbench, including refreshing source vs target, migrating with dependencies, and creating and deploying a new flex card.

Develop a 'report a problem' omniscript by integrating a data mapper, extracting asset details, and building product and case information blocks with dynamic fields, lookups, and conditional file upload.

Integrate the creation of a case via an integration procedure inside an Omniscript, test end-to-end with asset context, and navigate to the created case record.