--- title: Configure high touchpoints on nodes description: Configure a high touchpoints \(Node\) definition to view a pattern where a group of records in a step gets updated more often compared to another group to progress to any next step. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/now-intelligence/process-mining/high-touchpoints.html release: australia product: Process Mining classification: process-mining topic_type: task last_updated: "2026-03-12" reading_time_minutes: 2 breadcrumb: [Setting Automated improvement opportunities, Setting improvement opportunities, Use, Process Mining, Platform Analytics] --- # Configure high touchpoints on nodes Configure a high touchpoints \(Node\) definition to view a pattern where a group of records in a step gets updated more often compared to another group 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 High touchpoints on nodes displays a group of records in a step that has, on an average, more updates than another group. This points to the high-effort steps demonstrated by some records while others required fewer updates. **Note:** High 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/now-intelligence/process-mining/impact-metrics.md). \[Omitted image "high-touchpoints-node.png"\] Alt text: High 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/now-intelligence/process-mining/improve-opportunities.md). 2. Select **Create** on the High 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.
| Field | Description |
|---|---|
| Name | Specify a name for your automated finding definition. |
| Pattern type | This field is auto-populated. The automated finding definition that you chose to create is displayed here.You can change it if necessary. |
| Field to detect the pattern on | Select any field from the table on which you want to detect this pattern. The entire finding definition works on this field. |
| Category | Specify a category to which the automated finding definition belongs. The available options are:- Quality - Automation - Conformance - Performance |
| Active | Select the field if you want this finding definition to be active. By default, it’s selected. |
| Table | Displays the table name that you have selected. This field is non-editable. |
| Apply to process/project | Displays the table name that you have selected. This field is non-editable. |
| Impacted KPIs | 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. |