--- schema_version: "1" id: 119620e6b0441cc5681597688469f584cdfbdd7a84d0efafc9121db70aec83de title: Navigate Action (Managed Package) collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_navigate_action.md canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_navigate_action.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 56ada9d4cee4799264f12cf4034f706c6a8c45fc433339662ef69f5a5161c608 description: For the managed package runtime, navigate to various Salesforce experiences from Omniscript using the Navigate Action element. products: - Omnistudio release: "264" --- # Navigate Action (Managed Package) For the managed package runtime, navigate to various Salesforce experiences from Omniscript using the Navigate Action element. ![Managed Package app icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/resources-global/_corporate/images/managedpackageicon.png) This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see [Omnistudio Help](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_standard.htm&language=en_US). 1. Drag the Navigate Action into the Omniscript's structure panel. - If the Navigate Action renders in a Step, it becomes a clickable button. - If the Navigate Action is between Steps, it fires automatically. 2. If the Navigate Action renders in a Step: 1. Determine the style of the button by selecting an [SLDS Button variant](https://lightningdesignsystem.com/components/buttons/). In addition to SLDS Button variants, you can select **Link** to render the Navigate Action as an HTML anchor tag. 2. Display an [SLDS Icon](https://lightningdesignsystem.com/icons/) in the button by entering the Icon name in the **Icon Name** field. For example, to add the standard\_account Icon, enter Standard:Account. 3. If desired, replace the existing entry in the browser history by setting the **Replace** checkbox to **Yes**. If **Replace** is set to **Yes**, users can’t navigate back to the Omniscript. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/images/icon_note.png) Note By default, a Navigate Action in a Console App opens the PageReference type in a new subtab. If you use more than one Navigate Action, only the first Navigate Action redirects to a new tab. Even if the Replace checkbox is deselected, subsequent Navigate Actions replace the tab. But if the Replace checkbox is deselected, the page reference doesn’t replace existing entries in the browser history. Users can navigate back and forth between Omniscripts in the tab. After a Navigate Action completes, the Steps and other Omniscript elements that follow it run. However, if the user navigates away from the Omniscript, an asynchronously invoked Integration Procedure stops running. 4. To send messages from the Omniscript to separate Lightning web components, check **LWC PubSub Message?** and add a message key-value pair. Each Navigate Action must pass all required parameters to subsequent Lightning web components. For example, the first Navigate Action passes the `c__ContextId` parameter to a second Omniscript as `c__ContextId=ContextId`. A Navigate Action in the second Omniscript passes the parameter to a third Omniscript as `c__ContextId=%ContextId%`. All Navigate Actions must continue to pass the parameter to subsequent Omniscripts for as long as the parameter is needed. 5. To fire events from the Navigate Action, pass an event to the Omniscript in the URL parameter `c__vlocEvents`. The Navigate Action element must have the checkbox property **LWC PubSub Message?** enabled to fire the event. 6. Determine the Salesforce experience that the Navigate Action directs to by selecting a **PageReference type**.

PageReference Type

Description

Task Documentation

App

Direct users from an Omniscript to a standard App, a custom App, or a page within an App. Connected apps aren’t supported.

Component

Navigate from an Omniscript to an Aura or Lightning web component.

Current Page

Trigger a page update on the Current Page after a user completes an Omniscript.

Knowledge Article

Display a Knowledge Article in an Omniscript.

Login or Logout

Direct users from an Omniscript to a Community Login or Logout page.

Named Page

Navigate from an Omniscript to a Named Page or a Community Named Page.

Navigation Item

Navigate from an Omniscript to a page that displays mapped content on a CustomTab.

Object

Navigate from an Omniscript to a standard or custom Object page.

Omniscript by pageReference Type

Navigate to an Omniscript by using a Vlocity Omniscript pageReference type.

Record

Navigate from an Omniscript to a Record page.

Record Relationship

Navigate from an Omniscript to a page that interacts with a Record Relationship.

Restart Omniscript

Navigate to a new instance of the same Omniscript that resets the Omniscript data.

Web Page

Open an external Web page from an Omniscript.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/images/icon_note.png) Note In the LWC Omniscript Designer, the Navigate Action's JSON prop set doesn't contain every property from the Properties section. To add a property, edit the JSON. If a corresponding property exists, it appears in the UI. Don’t edit these properties when using the Edit JSON feature: - disOnTplt - iconPositionOptions - loginActionOptions - objectActionOptions - recordActionOptions - replaceOptions - targetLWCLayoutOptions - targetTypeOptions - variantOptions