---
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


---

# Example use case: a-b-a transitions

# Example use case: a-b-a transitions {#ariaid-title1}

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

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 AllProcess MiningProjectsAll 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 [Set rule-based finding definitions using Classic view](https://servicenow-prod.fluidtopics.net/vmYdOVDQ0wTDKXuWzjpufQ "Configure rule-based finding definitions to deliver discovered insights to your Summary and Insights page.").
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.
   {#aba-example__table_lcj_tx5_vvb__entry__2}

   | Field | Value |
   |-|-|
   | 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 |
   [ ]

   {#aba-example__table_lcj_tx5_vvb}
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.
    {#aba-example__table_dsg_ncv_vvb__entry__2}

    | Field | Value |
    |-|-|
    | 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 |
    [ ]

    {#aba-example__table_dsg_ncv_vvb}
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.
13. Select Create new rule (Same chain)  
    This is a new rule in the same chain. You can see that the Sequence field is <kbd class="ph userinput">2</kbd> and the Start condition field is automatically filled with the End condition of the previous rule.
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.
    {#aba-example__table_qxc_ydv_vvb__entry__2}

    | Field | Value |
    |-|-|
    | 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 |
    [ ]

    {#aba-example__table_qxc_ydv_vvb}
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.  
    {#aba-example__table_pkx_jfv_vvb__entry__2}

    | Field | Value |
    |-|-|
    | Name | First AG matches Second AG |
    | Start condition | AG is Anything |
    | End condition | AG is Anything(2) |
    | Relation constraint | is the same event |
    [ ]

    {#aba-example__table_pkx_jfv_vvb}  
    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.

*[\>]: and then