One baseline method to help enforce quality data is to configure Acceptance Criteria, meaning the minimum data required to successfully process a lead. If the configured conditions are not met, the lead will be rejected outright. The rejected lead is still recorded: it appears in the Events tab as a source event carrying the outcome and reason returned to the source, and no flow step runs for it.
Acceptance Criteria can be set both at the:
- Flow level: applies to all Sources
- Source level: applies only to that Source
The audit of Acceptance Criteria occurs at the beginning of the lead flow before any enhancements or validation occurs, so the best configuration is to check for basic data such as:
- Is there a value for this field
- Does the value of this field match a pre-defined list of acceptable answers
Required Fields as Acceptance Criteria
Required Fields are a common use case for Acceptance Criteria. You define required fields by listing the fields and setting the operator to “is not blank”.
Note: “is equal to” and “is included in” comparisons are case-insensitive. With those operators, values are compared without regard to case, i.e., “test” == “TEST” == “Test”; “includes”, “is true”/“is false” and “matches pattern” are case-sensitive.
- image_8.png200 KB
- image_10.png200 KB
- image_12.png200 KB
Comments
1 comment
I have to credentials: santiago@carbonbetter.com and sales@carbonbetter.com
I'm unable to access the dashboard with either one of these accounts.
Please sign in to leave a comment.