> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/przeplywy/akcje-nawigacyjne.md).
# Navigation actions
{% hint style="info" %}
Availability of functionality depends on the license and may not be available in all deployments.
{% endhint %}
It is possible to define a redirect to a specified address after certain conditions are met.
## Adding an action
After clicking the button **Add action** at the top of the section above the remaining actions (if there were already any in the application), an empty row is added, in which we first select the action type.
Available events:
* **GO TO THE NEXT PAGE** (PAGE\_CHANGE\_FORWARD)
* **GO BACK TO THE PREVIOUS PAGE** (PAGE\_CHANGE\_BACKWARD)
* **FORM SAVE** (FORM\_SAVE).
The redirect to the specified address is entered in the field **Redirect link**. The event will occur after the condition contained in the field **Add condition**.
Figure 1.Row for defining a new action
In the link given in the field **Redirect link** dynamic values from application components can be inserted (e.g. session variables). To use a component value, enter its **id** contained in **${}**.
{% hint style="info" %}
Only the first redirect (according to the order in the table) that satisfies the required condition will be executed.
{% endhint %}
Figure 2.Example of a conditional action on application save
### Eximee internal redirect
If the action redirects to another Eximee form, mark in its row, under the method and field **Redirect link**, field **Eximee internal redirect**. The platform will then append to the redirect the parameters configured for the environment, for example source of entry or channel. Parameters present in the address are not overwritten, and parameters without values are not appended. The marking works when going to the next page, going back to the previous page, going to a selected page, and saving the application. Actions without the marked field work unchanged.
The list of parameters, the rules for their inclusion and an example are described on the page [Eximee internal redirects](/documentation/documentation-en/eksploatacja-aplikacji/webforms/konfiguracja/przekierowania-wewnetrzne.md).
### Redirect to a user task in the EximeeBPMS process
Navigation actions also allow redirecting the user directly to the task associated with a specific process in Eximee BPMS, using a dedicated system address.
This address has the form:
```
/process/${processInstanceId}
```
Figure 3.Navigation action for taking a User Task
where ${processInstanceId} is the identifier of the process instance in EximeeBPMS.
After invoking the system address:
* the system verifies whether the user has access to tasks in the given process,
* automatically finds the active user task,
* redirects the user directly to the form attached to that task.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/przeplywy/akcje-nawigacyjne.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
.png?alt=media)