Rules for Mandatory User-Defined Fields

Updated 2 years ago by dustin keir

When you work with Address Book entries, Opportunities or Customer Service cases, you can specify that user-defined fields are mandatory if a rule is matched. 

For example, you can write a rule that makes a user-defined field mandatory only when the category for an Address Book entry is set to “Partner”. When users set the value of the Category field to Partner, they are prompted to set a value for the user-defined field when they save the entry.

A mandatory rule consists of a comparison statement. It may compare a field with a value or with another field. Or it may compare formulas using the same syntax as formula user-defined fields.

You can create comparison statements with the following symbols.

  • == to check that two values are equal to each other.

  • != to check that two values are not equal to each other.

  • > to check that the first value is greater than the second value.

  • to check that the first value is less than the second value.

  • >= to check that the first value is greater than or equal to the second value.

  • <= to check that the first value is less than or equal to the second value.

Comparison statements are often combined with logical operators to add multiple statements together.

  • Or – Combines two comparison statements where either one of the statements is true.

  • And – Combines two comparison statements where both of the statements is true.

  • Not – Negates a comparison statement.

While the comparison statements may be simple, say to compare a field with a value or with another field, you can also write more complex rules. Within the comparison statements, you can include arithmetic operators (+, -, * /) and alphanumeric, date, and numeric functions to create complex formulas.


How did we do?