Disable the Managed Package Runtime and Deploy Custom Lightning Web Components

If you migrate from Omnistudio for Managed Packages to Omnistudio, disable the Managed Package Runtime setting. Before you disable this setting, ensure that all Flexcards and Omniscripts in use that are key to your business processes are supported in standard objects. If you add or edit an Omniscript or Flexcard after disabling this setting and use custom components to load these Omniscripts or Flexcards in Lightning App Builders and communities, the changes won’t be reflected unless you replace them with standard components. To update your existing Flexcards and Omniscripts in Lightning App Builders and communities without using the standard components, enable the Deploy Custom Lightning Web Components setting.

1. In Setup, find and select Omnistudio Settings.
2. Disable Managed Package Runtime.
   

   Note After you disable the managed package runtime setting, you shouldn’t re-enable it.

   Starting with Summer ‘25, when you migrate from the managed package runtime with standard data model to the Omnistudio standard runtime and disable the Managed Package Runtime setting, Omnistudio automatically converts all custom functions in the user-defined syntax to the standard syntax.

3. Redeploy your Flexcards and Omniscripts with a standard runtime wrapper by enabling the Deploy Custom Lightning Web Components in Standard Runtime setting.
   

   Note Standard components should be used whenever possible. Deploying should only be considered as a workaround when you need to update existing components and don’t want to add them as standard components.

   Depending on the number of Flexcards and Omniscripts, this redeployment can take from a few minutes to an hour to complete. To monitor the redeployment, find and select Deployment Status in Setup.