Learn about Omnistudio

Build Service Consoles and Industry Cloud Apps with the basic building blocks of Omnistudio.

• Understand Omniscripts
  An Omniscript guides users through complex processes with fast, personalized, and consistent responses.
• Understand Flexcards
  Flexcards provide tools for building customer-centric, industry-specific UI components and applications on the Salesforce platform. Flexcards are rich in information and actions relevant to the customer's context. Create your Flexcards in a declarative design tool and add them to your Lightning or Experience Cloud pages.
• When to Use Flexcards and Omniscripts
  Omniscripts and Flexcards have many basic similarities: Both are user interfaces, can pull data from multiple sources, and can be interactive. To decide when to use Flexcards or Omniscripts, consider if the purpose is to only show data or if users are likely to require complex interactive UIs.
• When to Use Omnistudio Data Mappers and Integration Procedures
  Omnistudio Data Mappers read or write Salesforce SObject data or perform single-step data structure transformations. Omnistudio Integration Procedures can interact with many types of data, including REST APIs and Apex classes, and process it in multiple steps. For some use cases, a single Data Mapper is sufficient. Integration Procedures usually call one or more Data Mappers and are more flexible and powerful. Use these guidelines to help you determine which to build.
• Integration Procedure Features Not in Omniscripts
  Integration Procedures and Omniscripts have differences and common features. Some important Integration Procedure features aren't present in Omniscripts.
• Use the Applications Together
  Use the Omnistudio applications together. Create guided interactions with Omniscripts; get and post data with Omnistudio Data Mappers and Integration Procedures; and display data and launch actions with Flexcards.