For the managed package runtime, Vlocity Omniscripts can be deployed within the Vlocity application, or within an iFrame either on a Salesforce Community or an external website. Once embedded within the page, the script can be versioned, modified, and activated without the need to reconfigure the page.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
When using Omniscript in the Lightning Console, note that the result of launching the Omniscript home page has changed as of SFDC Winter '19. For the optimal experience, create a new primary tab by CTRL-clicking the link. From the new primary tab, you can open objects in a subtab of that primary tab.
- Add an Apex Class Permissions Checker (Managed Package)
For the managed package runtime, enable specific access to the VlocityOpenInterface Apex class used by remote action APIs for each user or profile, permission set, or permission set group. Use the Apex class check setting to enable users with permission sets or permission set groups to call allowlisted Apex classes remotely. Configure an Apex class permissions checker to ensure that users require explicit access to the Apex class that administers the remote action called from an Omniscript, Integration Procedure, Flexcard, Classic Card, or REST API. - Deploying Omniscripts Off-Platform with OmniOut (Managed Package)
For the managed package runtime, deploy Omniscripts to AEM, Heroku, and other Cloud Application Platforms to run them outside of the Salesforce platform. AEM, Heroku, and other Cloud Application Platforms connect with Salesforce through Salesforce Cloud Authentication Components or via a Salesforce Connected App.