Task classification
You can use the Task classification page to view the list of tasks recorded by the Task Mining Agent. The recorded tasks represent the interactions that you performed in the applications or websites that are included in the Monitoring list of the Task Mining agent.
Figure 1. Dashboard
The following table describes the features of the Task classification page.
Element number | Element name | Description |
---|---|---|
1 | Table filters | Use the Filter by application list and the Filter by page list to filter based on application, page, and specific words. To do so, specify the required filter in the section, and then click Apply filters. |
2 | The Data analysis info button | Use the button to set a time frame for data analysis. |
3 | Filter options | Use the filter options button to filter the task based on various criteria. For more information, see Applying Filters to the task. |
4 | The Show task properties button | Use the Show task properties button to set the task properties. For more information, see Setting the task properties. |
5 | The Exclude task button | Use the Exclude task button to exclude a task from the project. Similarly, use the Include task button ("+" symbol) to include the task to the project. |
6 | The Apply wildcard and the Reset buttons | Use the Apply wildcard button to set the wild cards and aggregation rules for the page title. For more information, see Setting the aggregation rule for page title and element selector. Use the Reset button to reset the aggregation rules. |
7 | Task description | The tabular section on the page provides the following information: - Frequency The number of times the task was performed and recorded. - Application The name of the application or website in which the task was performed. - Page & URL The name of the page and the specific URL where the task was registered. - Task name The name of the task. You can give custom names for the task. |
Setting the task properties
You can click the icon to view the properties of each task, such as the name of the page, the selected element, and the associated screen captures as shown
in Figure 2. Dashboard
Figure 2. Dashboard
You can click the magnifying glass icon on the screenshot to enlarge the screen captures.
You can use the Task properties dialog to do the following tasks:
- Provide a custom name for the task.
- Mark a task as Human task if it must be performed manually and cannot be automated.
- Add the aggregation rule for the element selector by clicking the
icon.
Setting the aggregation rule for page title and element selector
On the Task classification page, you must set the aggregation rule for page title and element selector to group different elements into a unique group. It is useful when similar tasks, which have only a small difference in the page name or item, are selected. You can apply an aggregation rule to group similar tasks. By using this method, you can manage the tasks more easily.
When you set the aggregation rule, you can replace the aggregated page title or element selector with the following types:
-
Letters
The system aggregates the page title or element that has any letter to the specified character length in the character space you selected for aggregation. -
Any Digits
The system aggregates the page title or element that has any digit to the specified character length in the character space you selected for aggregation. -
Any Character
The system aggregates the page title or element that has any character to the specified character length in the character space you selected for aggregation. -
Any Non-digit Character
The system aggregates the page title or element that has any nondigit character to the specified character length in the character space you selected for aggregation.
Setting the aggregation rule for page title
You can use the following steps to set the aggregation rule for page title:
-
On the Task classification page, click the Apply wildcard button corresponding to the required task.
-
In the New value field of the Edit wildcard on page title dialog, modify the sample value. You can delete a part of the value in the New value field and not the complete value.
-
In the Rule parts section, click the rule that appears on deleting the string to view the Edit Rule Part section.
-
In the Edit Rule Part section, set the rules, click Simulate, and then click Apply.
Setting the aggregation rule for element selector
You can use the following steps to set the aggregation rule for page title:
-
On the Task properties dialog, click the Apply wildcard button for the selected element.
-
In the New value field of the Edit wildcard on selector dialog, modify the sample value. You can only delete any part of the value in the New value field.
-
In the Rule parts section, click the rule that appears on deleting the string to view the Edit Rule Part section.
-
In the Edit Rule Part section, set the rules, click Simulate, and then click Apply.
After you set the aggregation rule, the wildcard displays the number of page titles or elements that the system aggregated.
Examples of wildcard usage
Example 1: Partial match of selectors represents a task
In cases where different selectors represent the same Task group you can see some of the tasks mapped with the following selectors:
//div[@id/div[2]/div/div/div/div[1]....
You can select the first element or edit the number of wildcard characters and keep the part of the original string of elements, such as //div[@id=“
.
When the simulation is completed and confirmed the element will result in //div[@id="*
with 3 elements.
So the combination of the 3 factors (App: X, Page: Y, and the Selector: //div[@id=“*
) would result in a group of tasks.
The //iframe[@id
element would not wrap:
//div[@id/div[1]/a
//div[@id/div[2]/a/span
//iframe[@id
Example 2: All actions performed on the same page represent a single task
A wildcard with all its characters removed and the Any character amount set to the largest possible size (which encompasses all selectors) would result in grouping all of the following elements into a single task.
//div[@id/div[2]/div/div/div/div[1]....
//div[@id/div[1]/a
//div[@id/div[2]/a/span
//iframe[@id
</br
Example 3: All actions performed in the same application with different pages represent a single task (grouping)
You can have the following elements on two separate pages of the same application:
- A Visual Studio Code window with the following elements:
//div[@id/div[2]/div/div/div/div[1]....
- A second Visual Studio Code window with the following elements:
//div[@id/div[2]/div/div/div/div[1]....
//div[@id/div[1]/a
//div[@id/div[2]/a/span
//iframe[@id
If you set two wildcards, one for Page/URL: *
and the other for Elements: *
, all application elements and pages would be part of the same group of tasks:
//div[@id/div[1]/a
//div[@id/div[2]/a/span
//iframe[@id
Applying Filters to the task
The filter options button displays the options to filter the tasks based on specific criteria.
You can select the required checkbox and then click Use Selection to display the tasks that satisfy the criteria.
The following table describes the list of available filter options.
Filter Options | Description |
---|---|
Tagging status | Identifies the tasks with custom names. - Tagged: Displays the tasks with a custom name. - Untagged: Displays the tasks without a custom name. |
Inclusion status | Identifies the tasks that are included and excluded in a project. |
Search scope | Filters the tasks based on Name and Id. Select and apply the required filters in the table filters section before filtering the task by Name or Id. |
Human task | Identifies the tasks that must be performed manually. - Mandatory: Displays the tasks that are performed manually and marked as Human task. - Non mandatory: Displays the tasks that do not require human intervention. |