Power users can target a page using a full context path or a relative context path. Both paths require that you use the internal page name.
When specifying the page name for a page transition, you must use the internal page name used in the URL, not the display name used on the page tab.
Studio creates the internal name automatically when you create the page. The internal name removes spaces and special characters.
For example, while the label on the page tab is Data Results:

The page name in the URL is data-results:

While you can change the display name for a page, the internal page name does not change.
For a relative context path, the power user only specifies the name of the page. The default context path is then added in front of the target page name.
The default context is set using the Framework Setting df.viewTransitionDefaultContext. The default value for the setting is /web/guest/. If your application is created within a Liferay Portal community, you can change the setting to be the path to that community.
For example, if the user enters analyze in the target page field for a component, and the default context path is /web/my-community/, the end user is redirected to /web/my-community/analyze.
For a full context path, the entire path is provided, and the default context path setting is ignored.
For example, for the following target value:
/web/spend/analyze
no matter what the default context path is, end users are redirected to the /web/spend/analyze page.
#tabcomponentname[tabNumber]Where:
/web/spend/analyze#Sales Numbers[1]
To select the tab to display for multiple tabbed components, use a double colon (::) to delimit the components.
/web/spend/analyze#Sales Numbers[1]::Quarterly Forecast[2]