System development/Required fields
In an information system you can configure which fields are required. On this page you can find information about required fields.
Issues
[edit | edit source]- How to indicate that a field is required or optional?
- When should you make a field in an information system required? See examples.
Best practices
[edit | edit source]- Reference attributes should be made required in a link table or when the child cannot exist without a parent. For example order - orderline.
- Make attributes like DisplayedName required.
Example project-person
[edit | edit source]In this chapter you can find some examples regarding required fields.
In the below screenshot you see a set of projects and a set of employees. A project and an employee can exist without having a relation.
But when you implement this example you use a link table. Records in the link table are required.
Example contract-organization
[edit | edit source]When you create a CONTRACT you always have to make a relation to ORGANIZATIONS, because a contract always consists of two (or more) ORGANIZATIONS making an agreement.