For the complete documentation index, see llms.txt. This page is also available as Markdown.
Navigation actions
Availability of functionality depends on the license and may not be available in all deployments.
There is a possibility to define a redirect to the indicated address, after certain conditions are met.
Adding an action
After clicking the button Add an action at the top of the section above the remaining actions (if there were any on the application already), an empty row is added, in which we first select the action type.
Available events:
FORWARD TO THE NEXT PAGE (PAGE_CHANGE_FORWARD)
BACKWARD TO THE PREVIOUS PAGE (PAGE_CHANGE_BACKWARD)
APPLICATION SAVE (FORM_SAVE).
The redirect to the indicated 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 provided in the field Redirect link you can insert dynamic values coming from the application components (e.g. session variables). To use a component value, enter its id contained in ${}.
Only the first redirect (according to the order in the table) that meets the required condition will be executed.
Figure 2.Example of a conditional action on application save
Redirect to a user task in the EximeeBPMS process
Navigation actions also allow the user to be redirected directly to a task associated with a specific process in Eximee BPMS, using a dedicated system address.
This address has the form:
Figure 3.Navigation action for taking up a user task
where ${processInstanceId} is the identifier of the process instance in EximeeBPMS.
After calling the system address:
the system checks 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.
