For the managed package runtime, the following topics tell you how to manage your Omniscripts.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
- Importing Omniscripts (Managed Package)
For the managed package runtime, starting with Spring 2016, Omniscripts can be imported using the Data Pack feature. This allows you to move Omniscripts from one environment to another. - Exporting Omniscripts (Managed Package)
For the managed package runtime, Omniscripts can be exported using the new Data Pack feature. This allows you to move Omniscripts from one environment to another. - Version Omniscripts (Managed Package)
For the managed package runtime, create multiple versions of an Omniscript to develop and test scripts in preview mode before activating scripts for production deployment. We don’t recommend making changes to a production Omniscript. Any time you plan to alter a production script, create a new, inactive version and make all updates in the latest version before activating. - Save and Resume an Omniscript (Managed Package)
For the managed package runtime, enable users to save and resume Omniscripts by using Omniscript's Save Options property. Users can bookmark links, launch a saved instance from an object page, or email the link. Configure custom URLs to resume saved Omniscript instances in different domains. For example, a customer can initiate an Omniscript inside of a Community, and then a customer service representative can resume the Omniscript inside of the Service Console. - Emailing an Omniscript (Managed Package)
For the managed package runtime, to email a link to an Omniscript to a Contact, Lead, or User, you create an Integration Procedure that uses a remote action to send the email and call the Integration Procedure from an Omniscript or from Apex code.