--- 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 --- # Set rule-based improvement opportunity # Set rule-based improvement opportunity {#ariaid-title1} * Release version: Xanadu * * Updated August 1, 2024 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Rule-based finding definition is a custom rule that displays improvement opportunities for a use case on the Summary and Insights page. ## Before you begin Role required: sn_process_optimization_analyst, sn_process_optimization_power_user, or sn_process_optimization_admin By setting up your own rules, you can focus on specific areas of the process that you'd want to know more about, thus identifying improvement opportunities for a given use case. For example, you can set up a rule to display records that took more than 7 days from Awaiting verification to Resolved. ## Procedure 1. Navigate to Improvement opportunity definition page. For information about Improvement opportunity definition page, see [Set improvement opportunities](https://servicenow-prod.fluidtopics.net/viI_ZW4uJeBZ9q_UhWC8_g "Set improvement opportunities to find areas of improvement by which teams could optimize a process. You can either select from a list of rules available to you or set your own rules. Based on the rules set by you, you can view your areas of improvement."). 2. Select Create on the Rule-based card. 3. Provide details in the Define section. For details, see [Rule-based finding definition form from Finding Builder](https://servicenow-prod.fluidtopics.net/190LmqQPlfce6W3x5vl16w "Use the Create Improvement opportunity definition form to create a finding definition from the Finding Builder."). 4. Select Configure. The Configure tab is displayed. 5. Fill the details on the form. 1. Define a filter by adding conditions that contain a field, operator, and values.Use the Occurrence is field to define whether the filter applies to the first, last, or all occurrences of this condition. 2. Use the Add contextual condition button to define additional contextual conditions for this filter. Use the and and or buttons to create as many contextual conditions as needed. 3. Select Add next step to define another filter within this chain. After creating a filter, a relationship section appears between the two filters. This section defines the relationship between the activities immediately above and below it. 4. Select a relationship between your filters. * Directly followed by * Eventually followed by * Not directly followed by * Not eventually followed by {#rule-based-builder__ul_mtw_4kl_xbc} 5. Select the Track duration field. This field tracks the time between the specified finding steps to calculate the total duration of the finding process, which is displayed on the improvement opportunity. 6. Select + Add Chain (on the top right) to create an additional chain of filters. A chain is a set of linked filters. Create a chain to define a separate set of related filters that must also evaluate to true, but doesn't have a relationship with the filters in another chain. After you create a chain, you can navigate between chains using the Chain \ tabs at the top of the window. 7. Select Add constraint. The constraints panel is displayed to the right. Use the Finding Constraint to set specific conditions between finding definitions steps, such as duration and relation constraints between certain steps, which help narrow down their scope beyond the basic finding rules. 8. Select Add constraint, provide all details and select Add constraint. {#rule-based-builder__table_gwq_33h_1cc__entry__2} | Field | Description | |-|-| | Name | Name of the constraint | | Start | Event that triggers the finding constraint. The options available are the steps provided in the filters. | | End | Event that concludes the finding constraint. The options available are the steps provided in the filters. | | Min duration | Specifies the minimum duration between when the event defined in the Start field and event defined in the End field. The event in the End field must occur after the amount of time specified in this field. | | Max duration | The maximum duration between when the event defined in the Start field and event defined in the End field. The event in the End field must occur before the amount of time specified in this field. | | Relation constraint type | Optional constraint conditions to further define when the constraint triggers. None : No relation constraint Same : Records must have the same value in a specific field. Specify this field in the Relation constraint field field. Different : Records must have different values in a specific field. Specify this field in the Relation constraint field field. Same user : Start and end conditions must be triggered by the same user. Different user : Start and end conditions must be triggered by different users. Same event : Indicates that the start and stop steps are identical, while intermediate steps can differ. This helps identify Ping-Pong patterns, such as A -\> B -\> A, where only the first and last steps need to match. Different event : Indicates that the start and stop steps are distinct from each other, while intermediate steps can vary or be the same. This helps identify sequences where the initial and final activities are not the same, such as A -\> B -\> C, ensuring that the process begins and ends with different events. | | Relation constraint field | Field associated with the relation constraint type. This field appears when Same or Different is selected in the Relation constraint type field. Note: The available relation constraint field will appear empty if there are no selections in the Start Condition or End Condition fields. | [ ] {#rule-based-builder__table_gwq_33h_1cc} {#rule-based-builder__ol_zql_xjl_xbc} 6. Select Save and exit. {#rule-based-builder__steps_vmx_t2k_wbc}