Skip to main content
Version: 1.28 (Current)

Redirect to Portal Page

Audience: Low-code Engineers

Skill Prerequisites: Actions, Tokens

Sends the user to a page of the current portal. You pick the page from a list, and can add a query string. The page URL is built by the site, so it follows the site's friendly URL settings and can point to the page in the user's language.

It works in Forms, Listings, User Guides and APIs. It isn't available in workflows. It ends the action list, so actions after it don't run.

Typical Use Cases​

  • Go to a confirmation or dashboard page after a form is submitted
  • Open an edit page for a listing row, with the row's ID in the query string, for example id=[ItemId]
  • Reload the current page with different query string values, by leaving Page empty
  • Send users on a multilingual site to the page in their current language

Don't use it to​

Action NameDescription
Redirect to URLSends the user to any URL, which can come from tokens.
Send File for DownloadSends the user to a portal file picked at design time.
Repost DataSends the browser to a URL with a POST.
Change Tab and Stop ExecutionMoves a form to another tab without leaving the page.
Stop ExecutionStops the remaining actions without going anywhere.

Input Parameter Reference​

The parameters unique to this action are listed below. Review the common parameters for all actions here.

ParameterDescriptionSupports TokensDefaultRequired
PageThe portal page to go to. If no page is selected, the action goes to the current page.NoNone SelectedNo
Enforce Current LocaleGoes to the version of the page in the current language, on multilingual sites. See Languages.NofalseNo
Query StringParameters to add to the page URL, in the form param1=value1&param2=value2, for example id=[ItemId]&mode=edit. You can end it with an anchor, for example id=[ItemId]#details.Yesempty stringNo
Use URL Provider to form Query StringOn: the parameters are added the way the site's friendly URLs do it, which can be as path segments, for example /id/5. Off: they're added as a normal query string, for example ?id=5. Turn it off if JavaScript on the target page reads the query string.NotrueNo
Open in PopupOpens the page in a popup window on top of the current page, inside an iframe. Shown when Open in new tab is off.NofalseNo
Popup TitleThe title of the popup. Shown when Open in Popup is on.Yesempty stringNo
Open in new tabOpens the page in a new browser tab. Safari opens it in the same tab. Shown when Open in Popup is off.NofalseNo

How the redirect works​

The action builds the page's URL on the server, then redirects the same way as Redirect to URL:

Where the action runsWhat happens
Forms and Listings, button actions and form events other than On Page LoadThe browser goes to the page. The popup and new tab options apply.
Forms, On Page LoadThe server answers with an HTTP redirect (302) before the form is shown. The popup and new tab options are ignored.
User GuidesThe browser goes to the page in the same window. The popup and new tab options are ignored.
APIsThe API answers with 302 Found and the page URL in the Location header. The popup and new tab options are ignored.

The action doesn't check whether the user can view the page. The site checks that when the page opens, and shows its login or access denied page if needed.

Languages​

With Enforce Current Locale on, the action picks the page version for the current language:

  1. If the selected page is already in the current language, it's used.
  2. Otherwise, if the page's default language version is in the current language, that version is used.
  3. Otherwise, the page's translation for the current language is used, if there is one.
  4. Otherwise, the default language version is used.

The URL is built for the current language, so it includes the language part your site uses, for example /fr-fr/.

With it off, the URL is built for the selected page as it is.

Considerations​

  • Query String values aren't URL-encoded. The action adds token values to the URL as they are. A value with a space, & or # can break the URL or add extra parameters. Use tokens that hold simple values, such as IDs. For values like names or search text, use Redirect to URL with Escape URL special characters in tokens on.
  • An anchor alone doesn't work with the URL provider off. With Use URL Provider to form Query String off, a Query String of just #details is added as ?details. Add a parameter before it, or turn the option on.
  • The selected page must exist. If the page was deleted, the action fails with an error.
  • Popups use an iframe. You may want to add query string parameters that hide the site's header and menu inside the popup.
  • Put it last. The action ends the action list. Actions after it don't run.
  • Add a condition to redirect only in some cases, for example [Role] == "Manager". See Common Parameters.

Examples​

tip

To understand how to use the below examples, please see Running Examples.

1. Go to an edit page with the item ID​

This action opens page 57, for example an Edit Project page, with the project's ID in a normal query string, for example /edit-project?id=12&mode=edit.

{
"Title": "Redirect to Portal Page",
"ActionType": "RedirectToPage",
"Description": "Open the project for editing",
"Parameters": {
"PageId": {
"Expression": "",
"Value": "57",
"IsExpression": false,
"Parameters": {}
},
"EnforceCurrentLocale": false,
"QueryString": "id=[ProjectId]&mode=edit",
"QueryStringUseUrlProvider": false,
"OpenInPopup": false,
"PopupTitle": "",
"OpenInNewTab": false
}
}

2. Show the translated page in a popup​

This action opens page 63 in a popup, in the user's current language. The popup title comes from a token.

{
"Title": "Redirect to Portal Page",
"ActionType": "RedirectToPage",
"Description": "Show the terms in a popup",
"Parameters": {
"PageId": {
"Expression": "",
"Value": "63",
"IsExpression": false,
"Parameters": {}
},
"EnforceCurrentLocale": true,
"QueryString": "",
"QueryStringUseUrlProvider": true,
"OpenInPopup": true,
"PopupTitle": "[TermsTitle]",
"OpenInNewTab": false
}
}

Revised 09/27/2026