Salesforce Docs Portal

Flexcards Troubleshooting Considerations (Managed Package)

For the managed package runtime, when working within the Flexcard Designer, you may run into issues that require some troubleshooting to resolve. Before contacting support, consider these troubleshooting articles.

Managed Package app icon This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.

  • Grant access to your org domains to enable LWC features such as Preview. When spinning a new org or new installation, the Tooling API calls necessary for LWC may fail if the Remote Site Settings page in your org does not include the URLs required.

  • When you click on a Flexcard in the Omnistudio Flexcards home tab, and see a record detail page instead of the Flexcard Designer, you must update the Lightning record page of the Vlocity Card object to Vlocity Card Designer.

  • When you embed components, such as flyouts, Custom LWCs, and Child Cards, check that components are not called multiple times.

  • Update the Flexcard Object's Default Lightning Record Page to Access the Flexcard Designer (Managed Package)
    For the managed package runtime, if you click on a Flexcard in the Omnistudio Flexcards home tab, and see a record detail page instead of the Flexcard Designer, update your org's default Lightning record page for the Vlocity Card object. Set the org's default Lightning record page to Vlocity Card Designer.
  • Update Remote Site Settings to Preview Your Flexcard (Managed Package)
    For the managed package runtime, grant access to your org domains to enable LWC features such as Preview. When spinning a new org or new installation, the Tooling API calls necessary for LWC may fail if the Remote Site Settings page in your org does not include the URLs required. The required URLs are your org's lightning.force.com URL and the vf.force.com URL of the Visualforce page that contains the Flexcard Designer.
  • Fix Cyclic Redundancy When Embedding Flexcard Components (Managed Package)
    For the managed package runtime, when you embed components, such as flyouts, Custom LWCs, and child Flexcards, check that components are not called multiple times. If you add components that call themselves or call other components embedded inside components, you may create cyclic redundancy causing events to continuously fire in your browser, exceeding your maximum call size stack.