Update Omniscript Custom Lightning Web Components and Omniscript Elements Overridden with Customized Components

Migrate all custom Lightning web components that extend the omniscriptBaseMixin component or use a standalone component and all customized Omniscript elements that have overridden components from the managed package runtime to the standard runtime. This is a manual step.

1. Go to the lwc folder that has all your customized Omniscript elements.
2. For each customized Omniscript element, in the HTML file, replace the managed package namespace with the c namespace.
   For example, this code shows the contents of the customomniscriptText.html file with the omnistudio namespace:

    
   <template>
     <omnistudio-input><omnistudio-input>
   </template>
   

   This code shows the contents of the customomniscriptText.html file after changing the omnistudio namespace with the c namespace:

   
   <template>
     <c-input><c-input>
   </template>
   

3. In the JavaScript files, replace the managed package namespace with the c namespace.
   Most of these changes are related to module import.
   For example, this code shows the contents of the customomniscriptText.js file with the omnistudio namespace:

   import OmniscriptText from 'omnistudio/omniscriptText';
   import tmpl from './customomniscriptText.html';
   
   export default class CustomOmniscriptText extends OmniscriptText {
      render() {
          return tmpl;
      }
   }
   

   This code shows the contents of the customomniscriptText.js file after changing the omnistudio namespace with the c namespace:

   import OmniscriptText from 'c/omniscriptText';
   import tmpl from './customomniscriptText.html';
   
   export default class CustomOmniscriptText extends OmniscriptText {
      render() {
          return tmpl;
      }
   }
   

4. Remove this line from the meta.xml file of your custom component: <runtimeNamespace>devopsimpkg11</runtimeNamespace>

   For example, this code shows the contents of the customomniscriptText.js-meta.xml file before the change:

   <?xml version="1.0" encoding="UTF-8"?>
   <LightningComponentBundle xmlns="http://soap.sforce.com/2006/04/metadata" fqn="omniscript">
   <apiVersion>60.0</apiVersion>
   <isExposed>true</isExposed>
   <runtimeNamespace>devopsimpkg11</runtimeNamespace>
   <masterLabel>Custom LWC test</masterLabel>
   </LightningComponentBundle>
   

   This code shows the contents of the customomniscriptText.js-meta.xml file after change:

   <?xml version="1.0" encoding="UTF-8"?>
   <LightningComponentBundle xmlns="http://soap.sforce.com/2006/04/metadata" fqn="omniscript">
   <apiVersion>60.0</apiVersion>
   <isExposed>true</isExposed>
   <masterLabel>Custom LWC test</masterLabel>
   </LightningComponentBundle>
   

5. Deploy each custom component to the org by using Visual Studio Code or Salesforce CLI:

   sf force:source:deploy -p force-app/main/default/lwc/{component_name}

   Where component_name is the name of the custom component that you want to deploy to the org.
6. Update all Omniscript Action framework calls to run in the standard runtime.
   See Make Remote Calls Within Omniscripts from Lightning Web Components.
7. Verify that the migration is successful.
   1. From Setup, in the Quick Find box, enter Lightning Components, and then select Lightning Components.
   2. Make sure that the Namespace Prefix field is blank for the custom components that you migrated.