Adding Key Fields - "Expected Value"

Expected Value" Matching (Existing Functionality)

Overview:
Expected Value field is used to define a single expected value that must match exactly for the key field to be accepted as completed.

How It Works:

1. Select a Key Field – Users choose any field type (Picklist, Text, Number, Currency, Percent, etc.).
2. Define an Expected Value – The user enters the specific value that marks this field as complete.
3. Completion Check:
   • If the Key Field’s value matches the Expected Value exactly, the  key field is accepted by the milestone as Completed (✅).
   • If the value is anything else or null, it remains considered as  Incomplete (❌).
4. If No Expected Value Is Set:
   • The field is considered Completed as long as it is not blank (any value counts).

Example Scenarios:

Current Limitations:

• Only supports exact matches. No way to define multiple acceptable values.
• No support for greater/less than comparisons for numeric fields.

Coming Soon

Enhanced "Expected Value" Matching

Overview:
This version introduces greater/less than comparisons for numeric fields and the ability to list multiple acceptable values for Picklist and Text fields.

What's New?

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 Works:

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.