Review the Automated Tasks (Vlocity Industries Managed Package and Standard Data Model)

The Omnistudio Migration Assistant automates these tasks to simplify and streamline your migration process:

• Switch to the standard runtime: Turns off the Managed Package Runtime setting in the Omnistudio Settings page. This makes sure that the Omnistudio components operate within the Omnistudio standard runtime environment.
• Update references to Omnistudio components after migration: Updates component names to remove special characters such as underscores during migration. For example, a component named My_Flexcard is converted to MyFlexcard.

  • Flexcard and Data Mapper: Updates the Flexcard name and Data Mapper name.

  • Omniscript: Updates the type, subtype, and language combination.

  • Integration Procedure: Updates the type and subtype.

• Update Remote actions: Updates Apex classes used in remote actions to work with the standard runtime. For example, classes that previously implemented VlocityOpenInterface and VlocityOpenInterface2 are converted to use System.Callable with the required call method.
• Migrate Omni Global Auto Numbers: Migrates Omni global auto numbers, shows the status as Successfully Migrated in the migration report. Review the Global Auto Number migration report to verify that the rollback flags are cleaned up from the Interaction Config and the data is removed from the custom Global Auto Number.
  

  Note Omnistudio Migration Assistant does not remove special characters from the Omni Global Auto Number names during migration.
• Migrate Custom Labels: Migrates Custom Labels and updates references in Omniscripts, Integration Procedures, and other Omnistudio components. You can continue using c=Custom Labels as before, including multi-language translations.
• Migrate Custom Lightning web components: Migrates all custom Lightning web components that extend omniscriptBaseMixin or override Omniscript elements from the managed package runtime to the standard runtime. This includes updating namespaces in HTML, JavaScript, and *.js-meta.xml files.

  Example:

  • HTML

    Before migration:

    <template>  
      		<vlocity_ins-input></vlocity_ins-input>  
    </template>
    

    After migration:

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

  • JavaScript

    Before migration:

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

    After migration:

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

• Update Lightning Pages: Updates all Omniscripts and Flexcards deployed on Lightning pages that were previously using the Vlocity LWC OmniScript Wrapper or custom LWC wrappers, replacing them with the standard runtime components so they work seamlessly post-migration. The Omnistudio Migration Assistant also updates references that use runtime_omnistudio:omniscript, which contain special characters in type and subtype.
  

  Note

  This task is automated only if your components are embedded inside the Vlocity LWC OmniScript Wrapper. See Update Components Deployed on Lightning Pages.

• Update Community Pages: Updates all Omniscripts and Flexcards deployed on Experience Cloud sites or Community pages that were previously using the Vlocity LWC OmniScript Wrapper or custom LWC wrappers, replacing them with the standard runtime components so they work seamlessly post-migration. The Omnistudio Migration Assistant also updates references that use runtime_omnistudio:omniscript, which contain special characters in type and subtype.
  

  Note

  This task is automated only if your components are embedded inside the Vlocity LWC OmniScript Wrapper. See Update Components Deployed on Experience Cloud Site or Community Pages.