You have the option to add a button in a form associated with a task, allowing the user responsible for that task to return to a specific step in the process.
Button Configuration
To configure this button, follow these steps:
- Access the process editor and open the relevant process.
- Add or edit a form in the desired task.
- Add a button by clicking on the corresponding icon
.
- Edit the button by clicking on the pencil-shaped icon.
- Customize the label and add an icon to the button if desired.
- In the “Action” field, select the option “Call API or AI Prompt”.
- Click on the “Trigger” button.
- Select the option “API using NODEJS”.
- Select the web service you want to use or click on the ” + ” icon to create one.
- In the “Resource” section, enter the ID of the task you want the user to be redirected to when they click the button.
Tip: To obtain a task’s ID, select it, go to “Properties”, and click on the corresponding icon
.
- Click “Confirm” to save the configuration.
Adding a User Confirmation (Optional)
You can require the user to confirm their choice before returning to the task by filling in the following fields:
- “Confirmation message”: The message displayed to the user asking for confirmation.
- “Confirmation input”: The text the user must enter to validate their choice.
Allowing the User to Choose the Task
It is also possible to let the user directly choose the task they wish to return to. To do this:
- In the form, add a “Text” field with a list of available task IDs.
- Then add a button.
- In the “Trigger” section, add the following information in the “Resource” section:
“:field name”
The user must then select the desired task ID before clicking the button to be redirected.
Note: You can replace the display of task IDs with their names using an API.
Limitations
- The button can only return to a step within the same token. It is not possible to create a button on a sub-token to return to the main token.
- However, it is possible to create a button on a sub-token to return to a previous task within the same sub-token.