Requirements for Lightning Web Components Compatibility with Vlocity Lightning Web Components (Managed Package)

Requirements for Lightning Web Components Compatibility with Vlocity Lightning Web Components (Managed Package)

For the managed package runtime, to make the custom Lightning web component compatible with Vlocity Lightning web components, you must set two metadata tags in your XML configuration file.

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

  • 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 NS variable in the code example with the namespace of your Vlocity package.
    Important
    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.
    <runtimeNamespace>NS</runtimenamespace>
  • 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.
  • isExposed : Set the isExposed metadata tag to true.
    <isExposed>True</isExposed>

Custom Lightning Web Components will not throw errors unless Debug Mode is enabled. For more information, see Debug Lightning Web Components.