For the managed package runtime, create an LWC Omniscript to use custom Lightning web components and functionality exclusive to LWC Omniscripts.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
It’s possible to switch an Omniscript to either an LWC Omniscript or an Angular Omniscript at any time. However, Angular Omniscripts and LWC Omniscripts don’t support the same elements and functionalities.
-
From the Omniscript's Script Configuration, add a Type, Subtype, and Language.
In the Vlocity Insurance and Health Summer '19-Winter '20 and Vlocity CME Fall '19-Winter '20 releases, the Omniscript's type must begin with a lowercase letter. You can’t use case-sensitivity to define a type's unique name if another Omniscript with the same type exists. For example, if you have an Angular Omniscript with an existing type named Test, you can’t create an LWC Omniscript with a type named test.The type limitation occurs because Type is stored in a Salesforce picklist, and Salesforce picklists store values without case sensitivity.
NoteThe combined Type, SubType, and Language mustn't exceed 60 characters.
- Select Enable LWC.
- Save the Omniscript by clicking Save.
- Drag supported elements into the structure panel. LWC compatible elements display a Lightning icon in the Available Components panel of an Omniscript.
- Click the LWC Preview tab to deploy the Lightning web component.
- (Optional) Create custom Lightning web components for Omniscript.