Configure extreme touchpoints on nodes

---
title: Configure extreme touchpoints on nodes
description: Configure an extreme touchpoints \(Node\) definition to view a pattern where a step requires unusually large number of record updates than the normal range to progress to any next step.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/application-development/process-mining/extreme-touchpoints.html
release: australia
product: Process Mining
classification: process-mining
topic_type: task
last_updated: "2026-09-10"
reading_time_minutes: 2
breadcrumb: [Setting Automated improvement opportunities, Setting improvement opportunities, Use, Process Mining, Discover, AI Workflow Factory Prime, Agentic app development, Building applications]
---

# Configure extreme touchpoints on nodes

Configure an extreme touchpoints \(Node\) definition to view a pattern where a step requires unusually large number of record updates than the normal range to progress to any next step.

## Before you begin

Role required: sn\_process\_mining\_analyst, sn\_process\_mining\_power\_user, or sn\_process\_mining\_admin

Extreme touchpoints on nodes displays steps with an unusually large number of record updates than the median. This highlights steps that require extremely high effort.

**Note:** Extreme touchpoints \(Node\) can be configured for a project only if it has been configured for the process table on which the project is based. For information on configuring touchpoints for a table, see [Configure impact metrics](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/process-mining/impact-metrics.md).

\[Omitted image "extreme-touchpoints-node.png"\] Alt text: Extreme touchpoints \(Node\)

## Procedure

1.  Navigate to Improvement opportunity definition page.

    For information about the Improvement opportunity definition page, see [Set improvement opportunities](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/process-mining/improve-opportunities.md).

2.  Select **Create** on the Extreme touchpoints \(Node\) card.

    For a particular type of automated finding, you can create a maximum of two automated findings.

3.  Provide details in the **Define** section.

<table id="table_gyh_kjk_wbc"><thead><tr><th>

Field

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Name

</td><td>

Specify a name for your automated finding definition.

</td></tr><tr><td>

Pattern type

</td><td>

This field is auto-populated. The automated finding definition that you chose to create is displayed here.You can change it if necessary.

</td></tr><tr><td>

Field to detect the pattern on

</td><td>

Select any field from the table on which you want to detect this pattern. The entire finding definition works on this field.

</td></tr><tr><td>

Category

</td><td>

Specify a category to which the automated finding definition belongs. The available options are:-   Quality
-   Automation
-   Conformance
-   Performance


</td></tr><tr><td>

Active

</td><td>

Select the field if you want this finding definition to be active. By default, it’s selected.

</td></tr><tr><td>

Table

</td><td>

Displays the table name that you have selected. This field is non-editable.

</td></tr><tr><td>

Apply to process/project

</td><td>

Displays the table name that you have selected. This field is non-editable.

</td></tr><tr><td>

Impacted KPIs

</td><td>

Select the KPIs most likely impacted by the findings. Choosing the affected KPIs enables you to assess the business impact. You can view the KPI-related findings in the insights panel of the Process Mining workspace.

</td></tr></tbody>
</table>4.  Select **Configure**.

    The **Configure** tab is displayed.

5.  Fill the details on the form.

    Default values are provided. You can edit them if needed.

    \[Omitted image "extreme-touchpoints-node-config.png"\] Alt text: Extreme touchpoints \(Node\)

    According to the example, records that meet the following conditions are available as improvement opportunities in the Summary and insights page:

    -   The minimum touchpoints criteria is calculated as multiplier × median touchpoints for the step. In this example, records must meet or exceed 20 times the median repetition.
    -   A step must contain at least 20 records.
    -   The top percentage of records in the extreme group that can qualify. Prevents too many records from being included and focuses on true outliers. In this case, it is 2%.
    -   A maximum of 5 improvement opportunities will be generated in the Summary and insights page.
6.  Select **Save and exit**.


**Parent Topic:**[Setting Automated improvement opportunities](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/process-mining/automated-findings.md)