Configure advanced conditions

  • Release version: Xanadu
  • Updated August 1, 2024
  • 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.
    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

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

    Configured process start condition