Example of logged user actions

Prerequisites: Recorder is installed on the user's computer in Server mode.

User's task: Invoice payment.

The steps required to complete the task may be as follows:

  1. Open Microsoft Outlook.
  2. Find the message containing the invoice ID.
  3. Saved the attached PDF document to a local folder.
  4. Switch to SAP in order to process the invoice.
  5. Enter the payment details, attach the PDF document, and forward the invoice to the accounts payable department.

If, while processing the invoice, the user receives an e-mail with another task (e.g. customer refund request) and switches to that task midway through the invoice task, then goes back to the invoice task, etc., the log will contain events related to both tasks and will confuse the automatic task detection as well as interfere with the analysis of the primary task being mined. For more information on handling such logs, see "What do I do if a user switches between tasks while logging?"

Which events will be logged?

The log will contain all user actions — applications opened and closed, switching between windows, using shortcut menus, entering information in text fields, clicking buttons, typing text on the keyboard, copy and paste operations, etc. For a complete list of events that can be recorded, see "Supported Log Events."

Defining tasks in a Timeline project

If a user has completed one task and then switched to another task, you can load the resulting log into a Timeline and then in the Task Definition Editor specify the start and end event for each recorded task. It is recommended to have unique start and end events for each task.

IMPORTANT NOTE – TASK TYPE COUNTS: While there is no technical limitation as to the number of tasks in a project we do not recommend analyzing more than 10 tasks simultaneously in one project. If your logs contain more than 10 tasks each best practices suggests loading them into different Timeline projects.

IMPORTANT NOTE – COMMON START EVENTS: If a log contains an event that serves as a starting point for multiple different tasks, consider analyzing such a log in multiple different projects. If you choose to analyze such a log within one project, you will need to find a subsequent event that is unique to the next task to be analyzed.

22.09.2023 8:59:47

Usage of Cookies. In order to optimize the website functionality and improve your online experience ABBYY uses cookies. You agree to the usage of cookies when you continue using this site. Further details can be found in our Privacy Notice.