Loading

Configure Navigation to OmniScripts in Salesforce Experience Sites

Udgivelsesdato: Mar 18, 2026
Beskrivelse

Navigation between OmniScripts in Salesforce Experience Sites requires configuration through a dedicated Experience Builder page. While direct navigation may work properly internally, using a centralized page with URL parameters is required for direct navigation in Community Sites.

A Standard Page named lwcos is required to host OmniScripts. The target OmniScript is determined dynamically using URL parameters. The configuration differs slightly based on whether the runtime is Standard or Managed Package.

Løsning

Create the dedicated OmniScript page

  • In Experience Builder, create a Standard Page named lwcos.
  • Use this page as the container for rendering OmniScripts.

Add the OmniScript component (based on runtime)

  • For Standard Runtime add the OmniScript for Experience Builder component to the lwcos page.
  • For Managed Package Runtime Add the Vlocity LWC OmniScript Wrapper component to the lwcos page.

Configure navigation actions

  • Navigation to OmniScripts should be performed using URL-based navigation from source components (for example, buttons, actions, or OmniScript navigation elements).
  • The final navigation URL must include parameters that specify the target OmniScript’s type, subtype, and language.
  • For Standard Runtime, use the following URL format:
    /s/lwcos?omniscript__type=<type>&omniscript__subType=<subtype>&omniscript__language=English
  • For Managed Package Runtime, use the following URL format:
    /s/lwcos?c__target=c:<Type><SubType><Language>

Notes

  • The lwcos page is required and should be dedicated to hosting OmniScripts.
  • URL parameters are used at runtime during navigation to determine which OmniScript is rendered.
Vidensartikelnummer

000393775

 
Indlæser
Salesforce Help | Article