Deploy Your Migrated Components to the Testing Sandbox (Vlocity Industries Managed Packages and Custom Data Model)

Manually complete these steps to switch to the standard runtime and deploy your migrated components to the testing sandbox using your standard deployment process:

1. Set the Omnistudio designers to use the standard data model instead of the custom data model by executing an Apex class:
   1. Log in to your migration sandbox.
   2. Click Setup and select Developer Console.
   3. Run this command, replacing <namespace> with your org namespace: <namespace>.OmniStudioPostInstallClass.useStandardDataModel();

      Example: vlocity_ins.OmniStudioPostInstallClass.useStandardDataModel();

2. Switch to Omnistudio standard runtime and standard designer:
   1. In Setup, find and select Omnistudio Settings.
   2. Turn off the Managed Package Runtime setting. After you disable the managed package runtime setting, do not re-enable it.
   3. Turn off the Managed Package Designer setting.
3. Deploy custom Lightning web components (LWCs): Redeploy your Flexcards and Omniscripts with a standard runtime wrapper in Omnistudio standard runtime.
   1. In Setup, find and select Omnistudio Settings.
   2. Turn on the Deploy Custom Lightning Web Components in Standard Runtime setting.
4. Deploy the migrated components to the testing sandbox: Deploy the changes you made in the development sandbox (phase 1) to the testing sandbox. See Deploy Migrated Omnistudio Components to Another Environment.

• Deploy Migrated Omnistudio Components to Another Environment
  ̄After you test all your migrated content in a sandbox, use Visual Studio Code (VS Code) to push the content to the next environment in your migration plan. Deployment can be challenging if dependencies are not fully understood. We recommend thoroughly analyzing your entire implementation and carefully defining components in the package.xml file to make sure that no dependencies are overlooked.