Requirements for Extending OmniScriptBaseMixin (Managed Package)

For the managed package runtime, review and complete the requirements before you extend the OmniScriptBaseMixin component.

Managed Package app icon This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.

Custom Lightning web components extending the OmniScriptBaseMixin component cannot also extend or override an Omniscript element Lightning web component.
Custom Lightning web components extending the OmniScriptBaseMixin must use the Custom LWC element in Omniscript.
Custom Lightning web components built outside of the package cannot use any Salesforce Lightning web component that uses resources or affects the component at runtime. For more information, see Salesforce Modules.
To make the custom Lightning web component compatible with Vlocity Lightning web components, you must set two metadata tags in your XML configuration file:
- runtimeNamespace: If Lightning Web Security (LWS) is disabled, add the namespace of your Vlocity package to the XML metadata file in your component by using the runtimeNamespace metadata tag. Replace the namespace placeholder in the code example with the namespace of your Vlocity package. For more information on finding the namespace of your package.
```
<runtimeNamespace>namespace</runtimenamespace>
```
  Important If LWS is enabled, setting runtimeNamespace in your components causes errors similar to Cannot use runtime namespace 'somename' in module c-someComponentName. To determine if LWS is enabled in your org, see Enable Lightning Web Security in an Org.
- isExposed : Set the isExposed metadata tag to true.
```
<isExposed>True</isExposed>
```
View all of the component's properties, attributes, and methods in the ReadMe.