Required Assignment Criteria

With a required criterion, the object or candidate must meet this criterion. You can make a criterion required by selecting Always from the picklist in the Required field.

• For a criterion with a Compare To Object comparison, if the object does not have the attribute to satisfy the criterion, then that assignment rule fails and none of the candidates from that rule qualify for assignment.

• For person-based criterion (with a Compare To Person or a Compare Object to Person comparison method), if the criterion is not met, then that person candidate fails and does not qualify for that assignment rule. Therefore, further person-based criteria are not evaluated for that person candidate.

• For an organization-based criterion (with a Compare To Organization or a Compare Object to Organization comparison method), if the criterion is not met, then that organization candidate fails and does not qualify for that assignment rule. Therefore, further organization-based criteria are not evaluated for that Organization candidate.

For example, an assignment rule can have a required assignment criterion based on service request severity, with a Compare to Object comparison method and a criteria value of 1-Critical. In this case, if the object to be assigned has a service request severity of 1-Critical, then the object qualifies for the assignment rule. An object without a service request severity value or that has a different service request severity value does not qualify for this assignment rule.