Q. Can we use more complex criteria for "Expected Value"

A. Out of the box, the answer is NO.

But, as a 1 off, we could enhance your "Expected Value" Matching. But there will be a cost, as we'd have to set up a small project to understand exactly what you want, then use our development team to deploy your requirements.

Customization Required - To enable this required additional cost. We initiate a project to deliver this per client request. 

Overview:

Our customization could introduce greater/less than comparisons for numeric fields and the ability to list multiple acceptable values for Picklist and Text fields.

Examples:

1. Comparison Operators (=, >, <, >=, <=) for Numeric Fields

   • Works only for Number, Currency, and Percent fields.
   • Users can specify a range of acceptable values.
   • Example: "Lead Score > 75" → Any value greater than 75 will mark the field as complete.

2. Multiple Expected Values for Picklist & Text Fields (IN Operator)

   • Instead of just one anticipated value, users can enter a list of values (comma-separated).
   • If the Key Field’s value matches any of them, the field is complete.
   • Example: "Approval Status = Approved, Pending, On Hold" → Any of these will mark the field as complete.

How It Would Work:

1. Select a Key Field – Choose any field type.
2. Select an Operator (=, >, <, >=, <=, IN):
   • If the field is Number, Currency, or Percent, users can select >, <, >=, or <=.
   • If the field is Text or Picklist, users can select IN and enter multiple values.
3. Define the Expected Value(s):
   • Single value for =, >, <, >=, <=.
   • Multiple values (comma-separated) for IN.
4. Completion Check:
   • If the field matches the criteria, the milestone is Completed (✅).
   • Otherwise, it remains Incomplete (❌).

Example Scenarios (Enhanced Version):

Important Notes:

• Greater/Less Than Comparisons (>, <, >=, <=) are ONLY available for Number, Currency, and Percent fields.
• For Picklist and Text fields, use IN to specify multiple accepted values.
• Existing exact match functionality (=) remains unchanged.