Navigation:  Release Notes > Release Notes 743 >


Previous pageReturn to chapter overviewNext page

Process execution history

The workflow process map is extended




Workflow steps in the public part of the workflow have additional information in order to better analyze the process without going through step details. Below is an example of a completed process step:



At the top of each step the start and end date of the step is displayed. The start date of the last run will be displayed. Below that, the process step name and actors are shown. By hovering the mouse over the dates, also the time is displayed.


At the bottom, the following information is shown:

The number of times this step has been activated
The number of times additional information has been requested
The number of attachments added through this process step


The exact coloring will depend on your stylesheet definitions. Please be aware that this implementation requires a stylesheet change! Also note that in case (some) numbers are not desired to be displayed, the stylesheet can be used to remove elements.


Additionally, information about attachments is (optionally) moved to the right side of the workflow screen. All attachments visible to the user will be displayed in a single list. Per attachment, the source of the file is displayed. For example when the file was submitted in the original request it will show (request). When submitted in the Report in PDF step, it will show (Report in PDF) with the file name. New attachments can only be added through process steps, messages or ticketing module. It won’t be possible to drag-and-drop new attachments into the workflow.

Overview layouts on top of request


The request information can be manipulated by an administrator.




The example screen below shows how request information can be positioned at the top of a request:




The first red box shows the area in which ticket information can be displayed. This is configured within the general settings of a process step:



You can use form fields and process fields in this definition. To better structure the information, hidden fields in forms may be used to pre-configure how data is presented here.


The second red box in the first image shows the request section, containing all fields submitted in the original request.


It is possible to define multiple formats. Only 1 format can be set as the one shown on top of the workflow page. Other formats can be used to send data to other systems or use in emails. This feature can be used instead of the #REPLACE-All_form_fields# function.


Several small enhancements and bugfixes

-Submit process step when action go-to is used: When defining the action step action "Go To", the option now exists to submit the current step, similar to how it is available for Change form.
-Escalation emails were not sent when all group members are opted out.