Understanding Criteria in Rules

Criteria Overview

When creating a Data Governance Rule Based on:

• Acceptable Values, 
• Mandatory Fields, or
• User Access,

the Criteria section defines the conditions that must be met before the rule is triggered.

Criteria Considerations 

Keep the following considerations in mind when setting up criteria:

• For Collection Sections:
  • Criteria can only apply to one Collection, and only that Collection can be used in the rule.
  • For example: If you select a variable from the Appeals Collection, then all the other criteria and conditions in that rule must also use variables from Appeals. 

• For Static Sections:
  • Criteria can apply to one or more Static Sections, and only Static Sections can be used in the rule.
  • For example: If you select a variable from the Case Summary Static Section, then all other criteria and conditions in that rule must must also use variables from Case Summary.

Learn more about Filevine Static and Collection Sections (and their items): Static and Collections Sections. 

Criteria Configuration

The Criteria section consists of the following elements:

1. Add Criterion: Click this button to add a new Criterion N where N represents the number of existing criteria. Criteria use OR logic, meaning any one of them can trigger the rule.

2. Criterion N: Each criterion consists of one or more Conditions. By default the Criterion 1 is shown.
3. Condition: Each Condition consists of the following elements:

• Variable: A field from the selected Project Type and Section.
• Operator*: A condition for evaluating the variable (For example: Equal To, Not Equal To, Less Than). The available operators depend on the field type of the selected Variable*.
• Value*: The value to be matched, either entered manually or selected from a dropdown.

For example: 

The Variable* (Field in Filevine Project) Case & Filing Info - Petition Type should be Not Equal to the Value* EB-1 to trigger the rule.

• When the user enters in the Field Case & Filing Info - Petition Type located in the corresponding Filevine Project, the value PERM, the condition IS MET, due the value in the Case & Filing Info - Petition Type field is Not Equal to EB-1 so the rule IS TRIGGERED in the Neodeluxe Sidebar Extension.
• When the user enters in the Field Case & Filing Info - Petition Type located in the corresponding Filevine Project, the value  EB-1, the condition IS NOT MET, so the rule IS NOT TRIGGERED in the Neodeluxe Sidebar Extension.

4. Add Condition: Clicking this button adds a new Condition within the  corresponding criteria. Conditions are related using an AND logic expression.

For example:

When in a Filevine project with the same configured Project Type as the configured in the rule: 

• The user does not enter any value in the Fees and Expenses - Code field (Is Empty).

AND

• The user enters the value 1200 in the Fees and Expenses - Due field ($1200 is Less Than or Equal To $2500).

Doesn't care the values the user entered in the involved fields in the second criteria (Fees and Expenses - Date of Feed Absolute).

OR

• The user enters the date 02/22/2025 in the Fees and Expenses - Date of Feed Absolute field (02/22/2025 is Between 02/03/2025 and 02/28/2025).

Doesn't care the values the user entered in the involved fields in the first criteria (Fees and Expenses - Code and Fees and Expenses - Due).

The Rule IS applied, and depending on the rule configuration, an alert could be triggered or not.

However if the user does not comply with the established criteria when managing a Filevine project, the rule is not even assessed in the project.