---
sourceDocument: Brazil Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/application-development

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Filter conditions

# Set filter conditions {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Set filter conditions to limit the scope of your analysis.

## Before you begin

Role required: sn_process_mining_analyst, sn_process_mining_power_user, or sn_process_mining_admin

## About this task

Setting filters is an optional task for project creation.

## Procedure

1. Navigate to WorkspacesProcess Mining Workspace.  
   If you continue from the Set Objectives page, you're on the Scope your analysis page.
2. Select Edit for the project that you want to edit.
3. Select the edit button for the Scope your analysis section.  
   The Overview section provides details of the process table including any guardrails set for it.
4. Select Filter conditions from the side panel.  
   Tip:  
   Select Advanced view on the top-right corner if you want to edit the project in the Classic view.
5. Fill the form with details.  

   |-|-|
   | Source | It's automatically populated based on your selection in the Set objectives tab. |
   | Table | It's automatically populated based on the table that you have selected in the Set objectives tab. |
   | Filters | Select any field from the root table that you want to filter the data by. |
   | Related List Condition | Select the number of records that you want to view. |
   | Optionally, select to narrow your process scope | There are the following options in this section: * None: No filter is applied. This is the default value. * Crop: Crop the process to view a specific area of the process by specifying a start and end condition. All events that occurred before the start condition and after the end condition won't appear in the process graph. Note: You can specify the crop process on the fields that you have set as your activity definitions. Therefore, set the activity definition for the project, before setting the crop process. Select the + sign beside Start condition and End condition. Set a process start and process end condition. Example: If a project is set with the State as the activity definition, you have the following path: New -\> Open -\> Work in Progress -\> Resolved -\> Work in Progress -\> Resolved -\> Closed If a start condition is specified on the first occurrence of Work in Progress and a stop condition is specified on the last occurrence of resolved, then the model would look like this: Work in Progress -\> Resolved -\> Work in Progress -\> Resolved. * Transition: A transition filter focuses on process paths that contain a specific transition between selected steps. For example, mine records that transitioned from State: Work in Progress <kbd class="ph userinput">At some point followed by</kbd> State: On Hold. To provide the transition filter, you must set up the filter condition, with a start condition that is "at some point followed by" or "directly followed by" step 2. You can provide only 2 steps here. {#filter-conditions__ul_hzx_zlt_sdc} |
   [Table 1. Filters form]

   {#filter-conditions__table_cdk_gnq_vkb}
6. Select Save.

*[\>]: and then