3 Helpful Form Rule Reminders

When creating Custom Fields and applying Form Permissions, the following reminders are helpful when considering how you want to build a form for your organization’s needs.

1. You cannot have two rules point to the same Required, Hidden, or Limited Field Criteria

1. • If a Checkbox is checked, making a field required, you cannot add a new rule requiring that same field as it already has a dependency.
   • If a Dropdown selection hides a field, use the same rule to indicate additional criteria for hiding the field, rather than adding a new rule
   • Use “ANY” vs “ALL” criteria requirements carefully
2. Some fields have restrictions in form permissions.  They are as follows:
   • Radios, Multiple Selection, Checkboxes cannot be limited
   • Radios, Multiple Selection, Checkboxes cannot be made required
   • Multiple Selections cannot be hidden
   • These are important reminders when architecting Custom Fields and should be considered before creating large amounts of fields with the expectations to use Form Permissions to tailor layouts
3. Field Position (in the Custom Field Edit screen, you may select a “Position”)
   • When using Form Permissions “Field Order” override (e.g. Project Properties), note that this feature resorts Custom Fields based upon their “Position”, not the Field ID
   • For example:
     • 2 Custom Fields are created:
     • Project VIP is in Position 1
     • Project Estimate Date is in Position 2
     • Field Order form permissions are added to “re-sort” these into Estimate 1st, and VIP 2nd.
     • 1 Custom Field (“Business Contact”) is added and placed after VIP; the new order of positions is:
       • VIP, Business Contact, Estimate Date
     • The Field Order permission will see that Business Contact is now Position 2, and was designed to swap positions 1 and 2
     • The form will result in:
       • Business Contact, VIP, Estimate Date
   • This can cause confusion when sorting fields in forms.  Best practice is to apply Field Ordering using the “Position” value in the Custom Field itself, rather than Field Ordering where possible, and override when all fields and their respective positions are confirmed.