Setting an Expected Value" Matching (Existing Functionality)

Created by Kridass Ragunathan, Modified on Tue, 22 Apr at 1:41 PM by Kridass Ragunathan

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:

Key Field TypeExpected ValueKey Field ValueCompletion Status
Picklist"Qualified""Qualified"✅ (Completed)
Picklist"Qualified""New"❌ (Not Completed)
Text"Approved""Approved"✅ (Completed)
Text"Approved""Pending"❌ (Not Completed)
Number"100""100"✅ (Completed)
Number"100""90"❌ (Not Completed)


Current Limitations:

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


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article