Pair Omniscript with Other Omnistudio Components

Learning Objectives

After completing this unit, you’ll be able to:

Explain how Omniscripts use Omnistudio Data Mappers and Integration Procedures for data handling.
Describe how Flexcards can launch and be used within Omniscripts for enhanced UI and context.

Explore Data Integration

Omnistudio has four major components, and Omniscripts play only one role. In this unit, you learn about how Omniscripts work with the other components to produce a comprehensive solution.

Think of Omniscripts as the user interface and engine that guides users step-by-step through a process. Omniscripts don't‌ do the complicated data changes or work with databases or external systems. They’re designed for user interaction: They present fields for input, display information, and control a user process.

Fortunately, Omnistudio has Omnistudio Data Mappers and Integration Procedures—tools that Omniscripts can use to get, manipulate, and write back data. These two Omnistudio components act as the data and logic layers that support ‌Omniscript's front-end user experience.

Omniscripts and Omnistudio Data Mappers

Data Mappers read and write Salesforce object data, as well as perform single-step data structure transformations.

Within an Omniscript, you can use the Data Mapper Extract Actions to get data from Salesforce objects and prefill input fields. Then when a user enters or changes data, you can use Data Mapper Post Actions to save that data back to Salesforce objects.

A Data Mapper Extract Action gets record details to prefill input fields, then the data is written back to Salesforce with a Data Mapper Post Action.

You also use Data Mappers for transformations, such as taking data collected in the Omniscript and mapping it into the correct format to fill a Docusign template or a PDF document.

Omniscripts and Integration Procedures

For more complex data operations and interactions, Integration Procedures are the go-to tool to use with Omniscripts.

Integration Procedures are server-side processes that bundle multiple actions into a single server call for efficiency and reusability. They read and write data from Salesforce and external systems, plus call Apex code. You use Integration Procedure Actions within an Omniscript to invoke these powerful server-side processes.

An Omniscript can use an Integration Procedure to combine data operations. This reduces the number of round trips to the server, significantly improving performance. For example, an Omniscript uses an Integration Procedure action placed between Steps to get data from multiple sources simultaneously, processes that data, and then uses a Set Values action in the Omniscript to prepare fields for the next Step.

In this diagram, an Omniscript calls an Integration Procedure to get data from:

Salesforce with a Data Mapper Extract Action that calls a Data Mapper Extract
An external API with an HTTP Action.
An external database with a Remote Action that calls an Apex class

Graphic corresponding to the preceding explanation of Omniscripts and Integration Procedures.

Using Data Mappers and Integration Procedures together helps Omniscripts effectively manage data and integrate with other systems while keeping the user interface smooth and responsive.

Investigate User Interface Connections

You know the basics of how Omniscripts are built and how they get data, but how do users ‌experience them once they’re deployed? And how do they work with other UI components?

Omniscripts can be launched from an action button on a Salesforce page or an action link on an Omnistudio Flexcard. They can also be deployed as a standalone Lightning web component on Lightning pages and Experience Cloud sites that use either Aura or Lightning Web Runtime, or accessed directly via a URL. So you can embed your guided processes wherever your users need them.

How would an action link on a Flexcard work? Flexcards show data and relevant actions that, when clicked, start an Omniscript to handle a guided process related to the data shown on the Flexcard. In this example, selecting Change Contact on a Flexcard opens an Omniscript so the user can update the account’s primary contact.

Screenshot corresponding to the preceding description of Flexcards.

A service rep or customer viewing this information can select the button on the Flexcard to launch an Omniscript that guides them through the contact update process. The Flexcard can even pass context data, like the record ID of the page where it displays, to the Omniscript to prefill customer details, such as the shipping address.

Flexcards can also be embedded inside of Omniscripts. Flexcards are great for data visualization and displaying contextual information. By embedding Flexcards using the Custom LWC element within an Omniscript, you can show dynamic data summaries or related lists within a Step. To do this, you send data from the Omniscript's JSON to the embedded Flexcard. You can also configure the embedded Flexcard to pass data back to the Omniscript's JSON based on user interactions with the Flexcard.

And, as you learned in the previous unit, Omniscripts can interact with other Omniscripts. Build complex or repeatable processes as reusable child Omniscripts added to several parent Omniscripts as needed.

Wrap Up

In this badge, you learned the basics of how Omnistudio Omniscripts help you create guided experiences for users and customers, simplifying complex processes. They provide a structured path—like a marked hiking trail—that makes sure users reach their destination efficiently. Omniscripts help businesses like yours offer consistent, personalized interactions, reducing errors and delays. They're ideal for situations requiring custom layouts, branding, and data operations, working with both Salesforce and external data.

You now know that Omniscripts are built using a drag-and-drop designer and are made up of elements. With these declarative tools, you can create reusable processes that work with the other Omnistudio components and can be deployed wherever you need them.

Now, think about how you can use Omniscripts to create guided experiences. What complex processes can you simplify for your users and customers, and how can you improve their interactions with your business?

As you consider that question, be sure to check out the links in Resources for more about Omniscripts.

Geschätzte Zeit

Themen

Benötigen Sie Hilfe?

Industry Solutions – Ressourcen