---
sourceDocument: Xanadu Platform Analytics
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/now-intelligence

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Platform Analytics

ft:clusterId :

    - par

bundleId :

    - par

workflow :

    - Platform


---

# Configure advanced conditions

# Configure advanced conditions {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Configure custom start and end conditions for your table configuration to define which
part of the process should be included in the Process Mining project
and made available for analysis.

## Before you begin

Role required: sn_process_optimization_analyst, sn_process_optimization_power_user,
or sn_process_optimization_admin

## Procedure

1. From the Advanced Condition tab of your table configuration record, select the plus symbol next to the Process start condition field.  
   Advanced conditions allow you to configure a specific start and end condition from your process map, such as, specifying resolved as your process end state instead of closed. Another example is only discovering process from the first occurrence of the New state until the last occurrence of Resolved, thus leaving the Closed state out of the analysis.

   If you've already configured a start condition, you can use the reference icon to add the
   existing condition to the Process start condition field.
2. In the Create new process start condition form, fill in the fields.  
   For a description of the field values, see [Create new process start condition](https://servicenow-prod.fluidtopics.net/rBzuvXnUOncrPUZHFgd4tQ "Use the Create new process start condition form to configure custom start condition for your table configuration to define which part of the process should be included in the Process Mining project and made available for analysis. The Create new process end condition form also has the same fields.").
3. Select Submit to save the condition.
4. To create an end condition, select the plus symbol next to the Process end condition field.
5. In the Create new process end condition form, fill in the fields.  
   Note:  
   The fields and descriptions are identical to those for the Create a new process start condition form.
6. Select Submit to save the condition.

## A configured process condition {#po-advanced-conditions__example_xlt_xqh_hvb}

In this example, a process end condition is configured when an incident record enters the <kbd class="ph userinput">Work in progress</kbd> state. Because the Occurrence(s) to match field is set to <kbd class="ph userinput">First only</kbd>, the condition only triggers the first time a record's state changes to <kbd class="ph userinput">Work in progress</kbd>.