Project Overview
Before you begin
- Make sure that you have the Administrator or Data manager role in the project to be able to upload data.
- Make sure that Task Mining - Recording Service version 5.2 and earlier is selected as the data source in Project > Details > Data sources. You won't be able to use any other data source for your Task Mining project.
- Record user actions and upload the logs into your project. Now you should be able to group events into tasks and start analyzing your processes. Logs can be imported from ABBYY Recording Service automatically or uploaded manually.
For details, see:
Data Upload
Data Requirements
Project Homepage
How user actions are logged
Logs contain actions performed by a user to complete a particular task. For example, a user filling out a technical support form will typically follow these steps:
1. Open a company's website and navigate to its technical support section.
2. Fill out the support form and type in their question.
3. Submit the completed form.
Each step will be logged as a sequence of actions (e.g. clicking a button, opening a new browser tab, keying text, etc.). These actions will become events in your Task Mining project. By way of illustration, the table below shows log events corresponding to each step of a form filling task.
| Task Steps | Logged Events |
|---|---|
| Open site and navigate to technical support section. |
Invoke GET STARTED OpenWindow Support form |
| Fill out support form and type your question. |
Invoke FirstName ChangeElement FirstName Invoke LastName ChangeElement LastName Invoke Email ChangeElement Email OpenWindow Booking.com : Hotels in New York. Invoke Moxy NYC Chelsea Invoke Description ChangeElement Description |
| Submit form. |
InvokeMenuItem UI_element_12 Invoke SEND REQUEST |
Note. In this example, the user visited a third-party website in order to fill out a technical support form. The associated events are displayed in italics in the table above. Events like these can be safely ignored, as they are not part of the task. For details, see Ignoring Unrelated Events.
Avoiding unrelated events
Users may perform actions outside tasks required by their jobs. For instance, a user might decide to watch a YouTube video while waiting for a long download to complete. This may dilute the logs with unrelated data. To prevent unrelated activity from being logged, we recommend limiting recording to task-related actions only.
Users may also perform multiple tasks at the same time, with events relating to different tasks recorded all in the same log. To analyze such concurrent tasks, you need to upload the log consecutively into your different Task Mining projects, keeping the events relating to the desired task and ignoring the rest.
An example of analyzing a log containing events from concurrent tasks
Identifying tasks and cutting logs
Once the data has been uploaded into ABBYY Timeline, you will need to cut the log to create timelines. To define a task, mark its start and end event, and select a cutting mode. Tasks can also be identified automatically, provided certain conditions are met. For details, see Defining Tasks.
Cut the log to create task instances, automation candidates, and project details. This will also create timelines required to analyzed the uploaded data.
See also:
9/22/2023 8:59:47 AM