Best Practice is to Record Only Task Actions
It is generally recommended to record only applications and actions related to the business process and tasks. Any extra, unnecessary, actions will clog up the logs, slowing down task definition and hampering analysis. If your log contains such actions, you may want to mark them manually using the Ignore event/Ignore application tools in the Task Definition Editor.
You can ask an operator to start the Recorder manually before starting a business task and stopping the Recorder after finishing the task. While this requires some additional coordination and instruction it can result in a very clean dataset for the analyzed business process.
One of the best ways to ensure unnecessary applications (those not associated with performing the task) are not recorded (like chats, social networks, web surfing, etc.), these applications should be added to the Excluded list in the appropriate Recording Service recording template. For detailed instructions on creating Excluded and Included lists, see "Administering" > "How to Configure and Apply Template" in the ABBYY Timeline Deployment Guide for Windows Systems.
IMPORTANT NOTE – AVOID RECORDING OVERLAPPING TASKS
ABBYY Timeline cannot be used to analyze events from overlapping tasks within a single Timeline project. A "task" in this context means user actions related to one particular task type and instance within the given business process. Recording user actions that represent a mix of actions for different tasks will cause your analysis to be less precise or possibly prevent you from detecting and separating tasks. The best approach is to advise users to record user actions related to performing one particular task, step by step, from start to finish without switching to any other tasks. This will produce a clean dataset for markup and subsequent analysis and you will be able to place all the logs into one Timeline project.
9/22/2023 8:59:47 AM