Review the basics of Omnistudio for Managed Packages that you use to build Service Consoles and Industry Cloud Apps.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
- Meeting Industry Challenges with Omnistudio (Managed Package)
For the managed package runtime, the industries we serve face daunting challenges to thrive and remain competitive. To better serve customers, companies often resort to custom coding, which can be expensive, risky, can require months or years to complete. And custom projects can be delayed because a business process has changed. Improving and transforming customer service can be a monumental task. Here are the industries that Vlocity serves: - Use the Applications Together (Managed Package)
For the managed package runtime, 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 Classic Cards or Flexcards. - Omniscript Basics (Managed Package)
For the managed package runtime, a Vlocity Omniscript guides users through complex processes with fast, personalized, and consistent responses. For example, you can create an Omniscript to guide: - Vlocity Cards Framework Basics (Managed Package)
For the managed package runtime, the Vlocity Cards Framework provides tools for building customer-centric, industry-specific UI components and applications on the Salesforce platform. Cards are rich in information and actions relevant to the customer's context. Create your cards in a declarative design tool and add them to your Lightning or Community pages. - Omnistudio Data Mapper or Integration Procedure? (Managed Package)
For the managed package runtime, Data Mappers read or write Salesforce SObject data or perform single-step data structure transformations. 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 (Managed Package)
For the managed package runtime, Integration Procedures and Omniscripts have differences and common features. Some important Integration Procedure features aren't present in Omniscripts. - Customizable Style Guide for Newport Design System (Managed Package)
For the managed package runtime, Vlocity's customers have their own set of brand guidelines and design specifications, particularly for customer-facing applications. The Vlocity Omniscript and Cards Designers allow you to choose between two templates: - Omnistudio Data Mapper Basics (Managed Package)
For the managed package runtime, a Data Mapper moves Salesforce data into and out of applications. There are four types: Extract, Turbo Extract, Transform, and Load. Data Mappers enable you to read and write data to and from your Salesforce org. - Viewing the Namespace and Package Version of Omnistudio for Managed Packages (Managed Package)
For the managed package runtime, to check the namespace and version of your Omnistudio for Managed Packages installation. - sObject Descriptions for Omnistudio for Managed Packages (Managed Package)
For the managed package runtime, review the descriptions of Omnistudio for Managed Packages sObjects, and which objects you must grant read access to so that customers can view Omnistudio components. - Naming Conventions in Omnistudio for Managed Packages (Managed Package)
For the managed package runtime, follow the recommended naming conventions when you create an Omnistudio for Managed Packages component, such as an Omnistudio Data Mapper, a Flexcard, an Integration Procedure, or an Omniscript.