Loading
ただいま大変多くのお問い合わせをいただいており、ご連絡までにお時間を頂戴しております続きを読む
Omnistudio Installation and Upgrade
目次
絞り込み条件を選択

          結果がありません
          結果がありません
          検索のヒントをいくつかご紹介します

          キーワードの入力ミスがないか確認する。
          より一般的な検索語を使用する。
          絞り込み条件を減らして、検索範囲を広げる。

          Salesforce ヘルプ全体を検索
          Disable the Managed Package Runtime and Deploy Custom Lightning Web Components

          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.

          Before you begin:

          • Review the phases of the migration process to Omnistudio from Omnistudio for Managed Packages, making sure to confirm support for the features you need in Omnistudio and your Salesforce Industries cloud. See Migration Process from Omnistudio for Managed Packages to Omnistudio.
          • If you use the Salesforce Industries Communications, Media, and Energy (CME) package, verify that the standard runtime supports each component you use. Check each component’s Omnistudio Standard Runtime certification status in Communications, Media, and Energy (CME) Support for Omnistudio Standard Runtime.
          • Ensure that field-level security (FLS) is explicitly set for Omni Process Compilation (Read, Edit), Omni Data Transformation (Read), and Omniscript Saved Sessions (Read, Edit) on all user profiles that run Omnistudio components. Standard runtime enforces stricter FLS than the managed package runtime; missing field permissions cause LWC compilation errors and component visibility issues.
          1. In Setup, find and select Omnistudio Settings.
          2. Disable Managed Package Runtime.
            Note
            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
            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.

           
          読み込み中
          Salesforce Help | Article