Article published on the 2nd of May, 2024.
Contents
1. Introduction
The Finish step of a process functions as the last step displayed to the user once a process finishes. Unless otherwise configured, the finish step typically displays a completion message, letting the user know that the process succeeded, along with one or more buttons for the user to interact with.
By default, the process Finish step will show a header with the text "Process succeeded", and a Close button, as shown in the following image:
As an administrator, you can define a message to display on the Finish step, and you can also select whether to display a button to run the same process again, reload the current page when the process dialog is closed, or hide the close-button.
You can also set up custom buttons on the Finish step, e.g., to allow the user to navigate to some location inside or even outside the WorkPoint solution.
Lastly, you can configure so-called Auto execute operations, which allows you to specify a link to which the system will automatically open when the process reaches the Finish step.
In this article, we will cover all these topics.
2. Custom message
The Finish step automatically displays a header depending on the outcome of the process, i.e. if the process fails for some reason, the header reads "Process failed", and if the process succeeds, the header reads "Process succeeded".
Below the header, you can define a message to display to the user.
To do so, write the message into the "Message" field on the Finish step:
When the process ends, the message will be displayed below the header:
The Finish step message can also include information from the process context, for example the title of a newly created entity or item, as shown here:
Resulting in the title of the created entity or item to appear in the Finish message in the process:
3. Standard options
In this section, let's cover the three standard options on the Finish step
3.1. Show run again button
If the "Show run again button" option is enabled, the Finish step will display a button with the title "Run again". Clicking this button closes the current process and starts another instance of the same process.
In the following example, we have enabled the "Show run again button" option:
Which results in the following behaviour:
3.2. Reload page on process dialog close
If the "Reload page on process dialog close" option is enabled, page where the user is currently located (behind the process window) will be reloaded when the process dialog is closed, either using the "Close" button or the close button in the top right of the process dialog.
This option is especially helpful e.g., if the process creates or deletes elements in a list, and you want to ensure that the changes are reflected after successful process execution.
In this example, we have enabled the"Reload page on process dialog close" option:
Which results in the following behaviour:
3.3. Hide close button
If the "Hide close button" option is enabled, the Finish step will not display the "Close" button. This is useful e.g., if you have configured a custom button to close the process and navigate somewhere else, and do not want the user to use the standard "Close" button.
In the following example, we have enabled the "Hide close button" option, and configured a custom button titled "Go to vehicle":
Which results in the following behaviour:
4. Custom buttons
As a process configurator, you can make custom buttons available on the Finish step for users to interact with.
These custom buttons can e.g., be used to go to a newly created entity site, or perhaps to a link outside the WorkPoint solution.
Custom buttons can be created by clicking the "New button" button in the "Custom buttons" section on the Finish step in the process settings:
This adds a new custom button, which can be expanded to configure:
| Option | Use |
|---|---|
| Title | Use this field to define a text which will be displayed inside the button on the Finish step. |
| Link/Item | Use this field to specify a link for the button. The link will be navigated to when the button is clicked. You can define a full URL, or a relative URL inside the WorkPoint solution. Examples:
|
| Redirect | Use this field to specify how the link should be opened when the button is clicked Options:
|
In the following example, we have created a custom button which googles the vehicle we have just created using a process:
The "Title" option is set to "Google vehicle".
The "Link/Item" option is set to the following adaptive expression: "https://www.google.com/search?q=" + CreateVehicle.Title.
In the "Redirect" option, we have selected "Close and open in a new tab".
This button results in the following behaviour:
5. Auto executes
Auto executes allow you to configure automatic execution of actions once the process reaches the Finish step. These actions have the same options as custom buttons, but will execute automatically, meaning the Finish step will not be displayed to the user - they will instead be taken directly to the link defined in the auto execute action.
To add a new Auto Execute action, click the "Add auto execute" button:
The following options are available for Auto Execute actions:
| Option | Use |
|---|---|
| Title | Use this field to give the Auto Execute action a title. This title is not shown anywhere besides the process builder. |
| Link/Item | Use this field to specify a link for the button. The link will be navigated to when the button is clicked. You can define a full URL, or a relative URL inside the WorkPoint solution. Examples:
|
| Redirect | Use this field to specify how the link should be opened when the button is clicked Options:
|
Note that at the moment, it's possible to configure multiple Auto Execute actions. Only the last one configured will be executed.
In the following example, we have a process which registers new vehicles in a Car rental service solution. We have an Auto Execute action which automatically redirects the user of the process to the new vehicle's site in the current tab upon process finish:
This configuration results in the following behaviour when a new vehicle is created:
Comments
0 comments
Please sign in to leave a comment.