Once the tasks are identified and the logs are cut, Timeline will create a list of tasks that can be automated. Each task instance will be represented by a separate timeline, which you can analyze using any of the available analysis modules.
The program summarizes data in the Automation Candidates table that contains the following information:
|Task||The name you gave to the task when defining it.|
|Count||The number of identified task instances in the logs.|
|Log coverage||The percentage of the forms in the logs that are related to the task.|
|Events avg||The average number of actions involved in the task (e.g., clicking a button, opening a tab, etc.).|
|Complexity||The complexity of the task. It is determined based on the number of task variations, the number of forms, and the applications involved. The greater its value, the more complicated the task is to perform.|
|Apps involved||The number of applications used when performing the task. Click the number to see the names of the applications.|
|Save||The money you can save by automating the task. You need to specify the task cost to see this value.|
|Linked processes||You can associate tasks from your current Task Mining project with events from Process Analysis projects using the Automation Candidates table. Click the number to see information about connected projects.
For details, see Link Projects.
Dealing with obtained table data
Based on the information from the table, you can choose tasks for further analysis and automation, or you may want to reconfigure task definitions.
How to interpret the table values?
Here are examples of how you may consider some table information:
- The Count column shows the number of task instances. It shows the exact number of timelines for the task. This amount becomes a base for built-in analysis tools. For example, if you open and run Deadline analysis, it shows timelines that violate time limitations within the selected task. The more task instances the task has, the more accurate the analysis is.
- Check the Events avg value. This shows the average number of user actions to perform a task. The task with many events and a low Complexity value may be a good candidate for automation. Such a task has a lot of steps but remains not complicated.
- Check the Apps involved list. For example, there are 2 applications that are used for the task. If a user works a little with one of them, you may want to remove this application from the task definition to make the analysis clearer.
How is the table connected with the Candidates Distribution chart?
Some of the table values are displayed on the Candidates Distribution chart. Visual representation makes it easier to analyze and select tasks for further automation. For example, tasks with a higher Count value are presented with bigger bubbles on the chart. The chart axis represents task Complexity for easier task comparison.
For more information about the chart, see Candidates Distribution chart.