Update References to Use the Salesforce Standard Data Model

Perform cleanup tasks to ensure that your migrated content functions as expected.

• Set the Omnistudio Designers to Use the Standard Data Model
  As part of the migration from managed package runtime to Omnistudio standard runtime, execute an Apex class to set the Omnistudio designers to use the standard data model instead of the custom data model.
• Updates to Omnistudio Custom Functions
  If you're on the managed package runtime with standard data model, Omnistudio automatically converts all custom functions in the user-defined syntax to the standard syntax when you switch to the Omnistudio standard runtime. For the custom data model, first use Omnistudio Migration Assistant (Pilot) to convert your records to the standard data model, then switch to the standard runtime to automatically convert the custom functions.
• 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.
• Update Components Deployed on Lightning Pages
  To ensure that your components deployed on Lightning pages work as expected after you migrate from Omnistudio for Managed Packages to Omnistudio, check your Lightning page for all Omniscripts and Flexcards using the Vlocity LWC Wrapper or any custom Lightning web components (LWC), and replace those with the standard components.
• Update Components Deployed on Experience Cloud Site or Community Pages
  To ensure that your components deployed on Experience Cloud sites or Community pages work as expected after you migrate from Omnistudio for Managed Packages to Omnistudio, replace all Omniscripts and Flexcards using the Vlocity LWC Wrapper or any custom Lightning web components (LWC) with the standard components.
• Update References to Omnistudio Components After Migration
  In the standard object data model, Data Mapper names, Flexcard names, and Omniscript and Integration Procedure types and subtypes can contain only alphanumeric characters.
• Update Remote Actions
  To ensure that remote actions work as expected after you migrate from Omnistudio for Managed Packages to Omnistudio, update any Apex classes used in remote actions with the correct syntax.