Navigate To Page
For base apps (web apps), this action is used to navigate to a page in the current application, and if necessary, to pass parameters to the page.
For App UIs, this action is used to navigate to a page in the current App UI, and if necessary, to pass parameters to the page. To navigate to a page in a different App UI, use the Navigate to Application action..
This table describes the parameters for the Navigate To Page action:
Parameter Name | Description |
---|---|
page | The page within the current application (web apps) or App UI to navigate to. |
params | An object with the parameters to pass to the page, if required. |
history | Define the effect on the browser history. Allowed value are 'replace', 'skip' or 'push'. If the value is 'replace', the current browser history entry is replaced, meaning that back button will not go back to it. If the value is 'skip', the URL is not modified. Default is 'push'. |
Here's an example of a call to the Navigate To Page action, in which an input parameter is passed to the page:
const navigateResult = await Actions.navigateToPage(context, {
page: 'main-display-results',
params: {
calResults: $variables.calculationResults,
},
history: 'push',
});
Navigating to the same page but with different input parameters is considered a valid navigation, and since the input parameters change, the onValueChanged
event is triggered.
The navigation is pushed to the browser history, so pressing the browser's Back button restores the previous values of the input parameters.