Use finding rules to identify when records return to a previous state.

Before you begin

Role required: sn_process_optimization_analyst, sn_process_optimization_power_user, or sn_process_optimization_admin

This example creates a finding definition that uses two finding rules and a finding constraint to identify when an incident is assigned to a group (in this example, the Database group), and then switched back to its original assignment. Use finding definitions like this one to identify situations where incidents are incorrectly assigned.

Procedure

  1. Navigate to All > Process Mining > Projects > All Projects, and open the project where you want to include this finding.
  2. In the Project Finding Definitions tab, select the New button to create a finding definition.
  3. Fill in the details in the Finding Definition record.
    For information, see Configure rule-based finding definitions. Finding definition record
  4. Right-click the form header, and select Save from the context menu.
    After saving, the Finding Rules and Finding Constraints tabs are visible.
  5. In the Finding Rules tab, select the New button to create a finding rule.
  6. Select the plus (+) icon to the right of the Start condition field to begin creating your start condition.
    Note: You must create conditions for each rule. There’s no option to select existing rules.
  7. Use the fields on the Create new condition form to create your first condition.

    For the start condition, you create a condition where an incident is created with any value in the Assignment group field.

    FieldValue
    Name AG is Anything
    Table configuration Incident
    Condition type Field/value condition
    Field Assignment group
    Predicate is anything
    Occurrence(s) to match All
    Condition subtype Single
    Finding definition record
  8. Select Submit to save your condition.
  9. In the Relation field, select eventually followed by.
  10. Select the plus (+) icon to the right of the End condition field to begin creating your end condition.
  11. Use the fields on the Create new condition form to create your second condition.

    For the second condition, you create a condition where an incident is assigned to the Database group.

    FieldValue
    Name AG is Anything
    Table configuration Incident
    Condition type Field/value condition
    Field Assignment group
    Predicate is
    Field value Database
    Occurrence(s) to match All
    Condition subtype Single
    Finding definition record
  12. Select Submit to save your condition.
    You now have your first finding rule, which identifies when an incident is assigned to the Database group. Now you must create a second finding rule in the same chain.Finding definition record
  13. Select Create next rule (Same chain)
    This is a new rule in the same chain. You can see that the Sequence field is 2 and the Start condition field is automatically filled with the End condition of the previous rule.Finding definition record
  14. In the Relation field, select eventually followed by.
  15. Select the plus (+) icon to the right of the End condition field to begin creating your second end condition.
  16. Use the fields on the Create new condition form to create your end condition.

    For the second condition, you create a condition where an incident is assigned to the Database group.

    FieldValue
    Name AG is Anything (2)
    Table configuration Incident
    Condition type Field/value condition
    Field Assignment group
    Predicate is anything
    Occurrence(s) to match All
    Condition subtype Single
    Finding definition record
  17. Select Submit to save your condition.
    You now have a completed second finding rule.
  18. Select Submit to save your finding rule.
  19. Open your project record again.
  20. From the Project Finding Definitions tab, open the finding definition created in the previous steps.
    Note: This should be the one you created in step 3.
  21. In the Finding Constraints tab, select the New button.
  22. Use the fields on the Finding Constraint form to create your constraint.
    FieldValue
    Name First AG matches Second AG
    Start condition AG is Anything
    End condition AG is Anything(2)
    Relation constraint is the same event
    Finding definition record
    This finding constraint refines your finding rules. Now, for example when an incident is assigned to Network, then Database, and then back to Network, it will be discovered by this finding rule.
  23. Select Submit.