Using Workflow Metrics¶
Workflow Metrics gives insight into the time spent to complete certain workflow events. To use it, set up deadlines on a workflow process’s events. These deadline configurations are referred to as SLAs (Service Level Agreements). Once defined, Workflow Reports measure compliance with the SLAs. They’re like a contract between the workflow participants and Users submitting workflow items. Workflow Reports shows data for all processes with SLAs, including each workflow item’s SLA status: on time or overdue.
Editing a Workflow with SLAs: Editing a workflow (e.g., removing nodes, editing a task name) with SLAs defined on it may invalidate the SLA for items already in the workflow/SLA pipeline.
Creating or Editing SLAs for Active Processes: Editing an SLA’s duration or defining a new SLA while items are already in the workflow process causes a recalculation for all instances currently in the workflow. Completed workflow instances are not recalculated.
To use Workflow Metrics, you must be using Elasticsearch to index your DXP data. To learn more, read the Installing Elasticsearch article.
Navigate to the Control Panel → Workflow → Metrics.
Click on the title of the Process.
If there’s no SLA for the process, a warning message stating as much appears. Click the Add a new SLA link from the warning to access the New SLA form directly.
Alternatively, click the Options () menu and select SLA Settings.
On the SLAs screen, click the Add button ().
In the New SLA form, give the SLA a Name and Description.
Define the time frame for the SLA, specifying three things:
Start: Enters Task: Review
Pause: On Task: Update
Stop: Process Ends: Approved
Define the duration (i.e., the deadline) for the SLA. Fill out at least one of the two time boxes.
Valid Start and Stop Events¶
Any workflow task can be used as a start or end parameter for the SLA.
When the item makes it to the event defined here, the SLA timer begins counting. Choose between these options:
|The Start Node||The SLA timer starts when entering the created node.|
|Entry into a Task||The SLA clock begins when the workflow transitions to the task.|
|Exit from a Task||The SLA clock begins when the workflow transitions out of the task. For example, the SLA timer starts when leaving the Review Task.|
If the item makes it to the Stop event before the defined SLA duration (the deadline), it’s On Time according to the SLA. If it fails to make it to the Stop event in the specified duration, it’s Overdue. When defining the tasks to act as the SLA’s Stop Events, choose between these options:
|Entry into a Task||The SLA clock stops when the workflow transitions to the task (for example, an Update Task).|
|Exit from a Task||The SLA clock stops when the workflow transitions out of the task (for example, a Review Task).|
|The end node||The SLA timer stops when entering the approved node.|
The Pause field defines an event in the workflow when time should stop counting. For the Single Approver workflow, you might choose to pause the SLA timer when the item is in the Update task. The SLA can be paused at any task that falls between the start node and the end node, and it is defined by setting the node(s) when the SLA should be paused. The SLA timer is paused the entire time a workflow item is in the specified node.
|Unit of Time||Instruction|
|Days||Enter a whole number for number of days. If there are partial days such as 36 hours, use in combination with the Hours field; express it 1 Day and 12 Hours.|
|Hours||Enter the number of hours and minutes. The values in the Hours box must not exceed 23:59; if the duration exceeds one day, use in combination with the Days field.|
Configuring the SLA Job Interval¶
The time interval between metrics recalculation is called the SLA Job Interval. The default value is 1 minute. To change it,
From the Applications Menu (), go to the System Settings application and open the Workflow Metrics entry.
Change the Check SLA Job Interval configuration value and click Save.
Create a configuration file called
Give it contents like these:
Place it in
Workflow Metrics data is read from the search engine to calculate metrics. When configuring the interval value, consider these competing performance concerns:
A long time between metrics recalculation events corresponds with more search documents being read during each recalculation.
A short time between metrics recalculation events corresponds with a higher frequency of read requests to the search engine.