Define user actions for task logging
Group workstation user actions as a task that can be logged to provide data for a Task activity analysis.
Before you begin
Role required: sn_tm_core.analyst, sn_tm_core.power_user, sn_tm_core.admin
Procedure
Navigate to Workspaces > Task Mining Workspace.
Navigate to the project you want to group tasks for.
Select Task scope from the navigation pane.
If the list of active tasks is empty, no tasks have been defined for this project.
Select Skip if you aren't adding any mapped or user-initiated tasks.
Select Add task scope.
Select the type of task scope you want to create.
The available options are:
Automated
Activity collection is based on mapped task activities.
User-initiated
Activity collection is user-initiated tasks. Workstation users start and stop activity collection by following instructions. Targeted activity collection only uses user-initiated task scopes, and at least one task must be defined if you choose this option.
Screenshot showing task scope options.
On the form, fill in the fields.
Field Description Task name Name for the automated task. Source table The table from which you choose what actions to group. Edit conditions Conditions based on the selected source table that determine the required task. Activity Activity that you want to group and from which you want to retrieve task state changes. Start State that triggers the starting point of the task. End State that triggers the end point of the task.
Screenshot showing automated task scope fields.
|Field|Description|
|-----|-----------|
|Task name|Name for the user-initiated task.|
|Task instructions|Directions for workstation users to start and stop activity collection.|
Screenshot showing user-initiated task fields.
Select Capture screenshots to create desktop actions to collect desktop actions automation properties.
Capture both steps and desktop actions automation properties in a single recording session, instead of recording the same process twice. When a Task Mining analyst submits the automation request, the recording is delivered to the automation team with all UI properties needed to build desktop actions.
Repeat the task scope creation flow (steps 5–8) for every task you want to add to this project.
Select Save and continue.
Defining a P1 incident tracking task
To configure a task to track the status of P1 incidents from creation to closing, set the values in the following table.
| Field | Value |
|---|---|
| Source table | Incident |
| Activity | State |
| Start | New |
| End | Closed |
Screenshot showing the example task.
What to do next
Select workstation users you want to collect activity data from and create data requests. For more information, see Add workstation users to a Task Mining project.