Portal Routing

Routing supports the linking and redirection requirements of your web portal. Each page of your web portal must have a valid location to route customers to when they interact with menus and links that redirect to that page.

The pages of the web portal are provided with a default routing configuration which supports a fully functioning web portal. While modifications are not required, routing configuration is available to modify the configuration based on requirements, such as defining customer access of pages using Grant To and Segmentation options.

Each routing item must define the following:

Experience: The experience name is an internal identifier that allows other elements within the web portal to identify and link to the page. When another element, such as a link within a widget, redirects to a page the experience name is used to locate the page and properly redirect to the location. This value can be left blank if the page is not directly linked to from other elements of your web portal.
Page: The page name is an internal identifier for the page. This name is also used to define and configure a page within the web portal as described at Configuring a Page.
Path: The path defines the relative path within Digital Self Service - Transactions for the routing item. If this page is linked from the main menu navigation, this path must match the path for the menu item, as described in Menu.
Grant To: This option defines the type of customer that can view the routing location. This can allow a routing location to be displayed or hidden based on whether a customer has logged in to Digital Self Service - Transactions or if they are payment eligible.
Segments: Segments define the type of customer that can view the routing item based on their customer segment. Leaving this field blank makes the routing item available for all customer segments. Including segments limits the item to only the customer segments that are included. For more information on configuring segments, see Portal Segmentation.