---
sourceDocument: Australia Platform Analytics
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/now-intelligence

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Platform Analytics

ft:clusterId :

    - par

bundleId :

    - par

workflow :

    - Platform


---

# Define actions for task logging

# Define user actions for task logging {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
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

1. Navigate to WorkspacesTask Mining Workspace.
2. Navigate to the project you want to group tasks for.
3. Select Task scope from the navigation pane.  
   If the list of active tasks is empty, no tasks have been defined for this project.
4. **Optional:** Select Skip if you aren't adding any mapped or user-initiated tasks.
5. Select Add task scope.
6. 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.

7. On the form, fill in the fields.

{#mine-data__table_plp_4db_kcc__entry__2}

| 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. |
[Table 1. Automated task form]

{#mine-data__table_plp_4db_kcc}

{#mine-data__table_djv_kgf_nhc__entry__2}

| Field | Description |
|-|-|
| Task name | Name for the user-initiated task. |
| Task instructions | Directions for workstation users to start and stop activity collection. |
[Table 2. User-initiated task form]

{#mine-data__table_djv_kgf_nhc}

8. 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.
9. Repeat the task scope creation flow (steps 5--8) for every task you want to add to this project.
10. Select Save and continue.

## Defining a P1 incident tracking task {#mine-data__example_azx_kv5_xcc}

To configure a task to track the status of P1 incidents from creation to closing, set the values in the following table.{#mine-data__table_w1l_wfs_pfc__entry__2}

| Field | Value |
|-|-|
| Source table | Incident |
| Activity | State |
| Start | New |
| End | Closed |
[Table 3. Example: P1 incident tracking task]

{#mine-data__table_w1l_wfs_pfc}

## 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](https://www.servicenow.com/docs/GmifLOHUtAYng8UMwlzrgg "Select workstation users you want to collect activity data from and create data requests.").

*[\>]: and then