Omnistudio component selection for a delivered design
Key Takeaway
Match each requirement to the Omnistudio component built for it. A Data Mapper's Interface Type is fixed when you create it, so reading records (Extract) and saving edits (Load) need two separate Data Mappers. When one display needs Salesforce records and data from an external REST API, use an Integration Procedure instead of a single Data Mapper.
Omnistudio is a low-code toolkit in Agentforce Financial Services. You use it to build guided interactions, rich data displays, and data integrations without code, using data from Agentforce Financial Services and from external sources. Delivering a design well means matching each requirement to the right component: Omniscripts for guided steps, Flexcards for showing data and launching actions, Integration Procedures for multi-step server-side work, and Data Mappers for simple reads, writes, and transformations.
The four Omnistudio components
Omnistudio has four core components, and each has one main job:
- Omniscripts guide users through flows with logic.
- Flexcards display data and launch actions.
- Integration Procedures bundle server-side data operations for efficiency and reuse.
- Data Mappers transfer and transform data between Salesforce and the other three components.
A delivered design typically combines the components. Omniscripts create the guided interaction. Flexcards display data and launch actions. Data Mappers and Integration Procedures get and post the data behind them.
Omnistudio is the best choice for making complex processes easier and for showing relevant data to employees and customers. Omnistudio works best for high-volume, well-defined tasks where a consistent and efficient user journey is crucial.