Neodeluxe Criteria

Criteria Overview

This article serves as a guide to help users navigate, understand, and manage Criteria setup within the various products and functionalities of the Neodeluxe Portal.

Criteria define the conditions that must be met before triggering specific actions or enabling certain functions, among other things. Let's see the application of Criteria in Neodeluxe.

You can navigate through Advanced Task Management, Client Portal: Flows/Landing Page, Data Governance, and Process Studio tabs to learn relevant criteria information.

• Advanced Task Management

  1. Criteria Configuration in ATM

  • Entry criteria: When the Queue entry criteria are met, the corresponding task is created.

  Timing of Task Creation is dependent on Task Execution timeframes set in the Queue.

  Exit criteria: When the Queue exit criteria are met, the corresponding uncompleted tasks from the queue are closed. 

  • Configuring the Exit Criteria section in Advanced Task Management is optional. Queues that do not have Exit Criteria will have the associated Tasks remain open until marked as resolved. 

  

  2. Key Considerations

  Keep the following considerations in mind when establishing criteria in Advanced Task Management:

  The Criteria Variable* options will depend on the selected Project Type*, the Criteria Data Sources*(Filevine and/or Vineportal), and Section Type* (Collection or Form Section).

  • If Filevine is selected as the Data Source*, the Variable* dropdown shows fields from all Collection or Form sections, based on the selected Section Type* and Project Type*.

  

• Client Portal:

  Flows

  1. Criteria Configuration in Flows

  • Flow Entry Criteria: When the entry criteria are met, the project is enrolled in the corresponding Flow, sending messages and assigning tasks associated with the Flow.
  • Flow Exit Criteria:  When the exit criteria are met, the enrolled project exits the corresponding Flow. Once the exit criteria are met, all associated messages and tasks will stop sending and will be unassigned.

   

  

  2. Key Considerations

  Keep the following considerations in mind when setting up a criteria in Flows:

  • When Filevine is selected as the Data Source*, the Variable* dropdown displays fields from all existing Collection and Form sections based on the chosen Project Type*.
  • You can use fields from both sections together when setting entry and exit criteria.
  • Conditions within criteria can also use different Data Sources.

  

  Landing Pages

  1. Criteria Configuration in Landing Pages

  • Section Settings - Conditionals: When the Section Settings criteria are met, the corresponding custom section is displayed.

   

  

  2. Key Considerations

  Keep the following considerations in mind when setting up a criteria in a Landing Page:

  • When Filevine is selected as the Data Source*, the Variable* dropdown displays fields from all existing Collection and Form sections based on the chosen Project Type*.
  • You can use fields from both sections together when setting entry and exit criteria.
  • Conditions within the criteria can also use different Data Sources.

  

• Data Governance

  1. Criteria Configuration in Data Governance

  When the Data Governance rule criteria are met, the corresponding rule is triggered. 

  Configuring the Criteria section is mandatory for rules based on Mandatory Fields.

  However, for rules based on Acceptable Values and rules based on User Access, configuring the Criteria section is optional.

   

  

  2. Key Considerations

  Keep the following considerations in mind when setting up criteria in Data Governance:

  • Criteria can be built based on the selected Governance Source*—either Project Type or Contact Cards. The Variables within the Criteria will be dynamically displayed according to the selected Governance Source*.

   

  

  • Some variables may not appear in the list until data sources get refreshed. Go to Admin > Neodeluxe Portal > Flows Data Source and click on the Refresh button in the desired source to do it.
  • For Collection Sections:

  Criteria can only apply to ONE Collection, and only that Collection can be used in the all the criteria setup.

  For example: If you select a variable from the Appeals Collection section, then all the other criteria and conditions 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 criteria setup.

  For example: If you select a variable from the Case Summary Static Section, then all other criteria and conditions must use Static Sections.

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

  1. APP: Foundation AI: When Foundation AI is selected in the App dropdown, the Variable options displayed are: Includes Tag and Document Type.
     • When the Process Studio Conditional Node criteria are met, the process continues the true path in the automation. Otherwise, the automation follows the false path.

• Process Studio

  1. Criteria Configuration in Process Studio

  • When the Process Studio Triggers Filters criteria are met, the corresponding process(es) are triggered.

  

  • When the Process Studio Conditional Node criteria are met, the process continues the true path in the automation. Otherwise, the automation follows the false path.

  

  2. Key Considerations

  Keep the following considerations in mind when setting up criteria in a Process Studio Trigger Filter Criteria:

  

  

  • Document Type: When the selected Variable is Document Type, the available Operators and Values are:

  

  Operators	Value
  Equals Not Equals Contains Not Contains Starts With Does Not Start With Ends With Does Not End With Is Blank Is Not Blank	PDF PNG JPEG DOCX

  • Includes Tag: When Includes Tag is selected as the Variable, the operator field is hidden. Instead, an additional dropdown appears, listing the available tags.

  

  2. APP: Filevine: When Filevine is selected in the App dropdown, the Variable options are dynamically shown based on the selected Project Type and Section, reflecting the available fields.

  

Criteria Elements 

In general, Criteria can be configured by using the following elements:

1. + Add Criterion: Click this button to add a new Criterion (N), where N represents the number of existing criteria. Add as many criteria as needed.
2. Criterion N: Each criterion consists of one or more Conditions. By default, Criterion 1 is shown. 

3. Condition: Each condition consists of the following elements:

• Data Source: The origin of the fields being evaluated (If applicable).
• Variable*: A field from the selected Project Type and Section.
• Operator*: A condition for evaluating the variable. Available operators depend on different parameters. For more information about operators' availability please visit Field Types vs Operators Availability in Neodeluxe Portal Criteria ADD LINK
• Value*: The value to be matched, which can be entered manually or selected from a dropdown.

4. Add Condition: Click this button to add a new condition within the corresponding criterion.

For Filevine Projects with Project Type Mass Tort, the Criteria is configured as follows:

When in a Filevine Project with Project Type Mass Tort:

• The user enters No in the Authorization Letter to Insurance Drafted field.

AND

• The user leaves the Insurance Claim Number field empty.

THE CRITERIA IS MET.

OR

• The user enters in the Date Authorization Letter to Insurance Sent Absolute field the date 02/25/2025 (which is Between 02/01/2025 and 03/21/2025).

AND

• The user enters any value in the Date Letter of Representation Drafted Relative field, (which means the field is Not Empty).

THE CRITERIA IS MET.

OR

• The user enters in the Project Hashtags the value standing (Which means that Contains “nd”).

THE CRITERIA IS MET.

Field Types vs. Operators Availability

In Neodeluxe, users can define custom criteria by selecting specific Variables and Operators:

• Advanced Task Management Criteria: Supported/ Unsupported Field Types Vs Operators.
• Client Portal Criteria (Flows and Landing Page): Supported/ Unsupported Field Types Vs Operators. 
• Data Governance Criteria: Supported/ Unsupported Field Types Vs Operators. 
• Process Studio: Supported/ Unsupported Field Types Vs Operators.

Have Questions or Issues?

If you have any questions or you are experiencing issues while using Criteria, please contact our Product Support Team:

• Email: help@neostella.com
• Submit a Request: Click here to submit a ticket

Our Product Support Team is available Monday through Friday, from 8:00 AM - 5:00 PM CST.