A field is considered required if the user cannot save a record without entering a value in that field. If a user attempts to save a record without populating a required field, TeamConnect displays a message that the field is required.

By default, the labels of all required system fields and custom fields (set as required when they were created) appear in boldface with an asterisk next to them, in the end-user interface. However, fields are not automatically displayed this way if they are required as a result of rules, or if another field uses its value. It is easier to require such fields when creating them than to modify the way they appear.

Example: Required Field in End-User Interface

How To Make Fields Required

You may make a field required in one of the following ways:

•By creating a custom field in an object definition and setting it as required for everybody. These fields are automatically displayed as required.

•By creating rules to make system or custom fields required under certain conditions. These fields are not automatically displayed as required.

Fields may also become required (though not marked as such in the user interface) as a result of certain design decisions that you may make. For example:

•If you add an object attribute to the unique identifier (ID) pattern in custom object definitions, the corresponding field becomes required.

•If you make a custom object definition contact-centric, the corresponding contact field becomes required.

•If you set a parent custom object definition as required, the corresponding parent project field in all child projects becomes required.

Practical Tips

Keep these tips in mind while working with required fields:

•If you include attributes in a naming pattern for custom object records, consider making the corresponding fields required. This action ensures that these fields are populated and that the resulting descriptions in the Name field are more consistent.

•If you make certain fields required in contact records, the users may not be able to add contacts through the contact search module window.

•Use the tag attributes, notUseRequiredFieldStyle or irequired to control whether custom field labels appear as required when including them in blocks.

•Make sure you include all required fields into wizards that you may be creating for that object. Otherwise, the user is unable to save the record after using the wizard.