Field Settings

When dealing with information on systems and software, it is often essential to have all required data available for the system to function properly. However, the real world often presents scenarios where all required information is not available directly, and needs to be collected over time possibly from different sources.

Similarly, information gets outdated, rendering it invalid until it is replaced with updated information.

Invalid/missing data does not allow the system/software to function as expected, and therefore systems introduce restrictions on data to ensure only complete and valid data is used for processes within the system.

CloudERM does this through field settings on data concepts within the system. Fields settings tell the system which pieces of data on an entity are essential, and the software subsequently restricts processes and functions on that entity until all essential data is available.

Any field of data for an entity can have one of four field settings:

1. Require: Fields with the require setting cannot be ignored on entity creation. Providing these fields is a must when creating new entities (such as assets/customers/parts etc) within CloudERM.

2. Validate: Fields with the validate setting are essential for business/organizational processes. While entities with missing or outdated data on validate fields can be created in CloudERM, these entities will be rendered invalid, and processes will be restricted for the entity until valid data is provided.

3. Optional: Fields with the optional setting can be ignored. Entities with missing/outdated data in these fields have no restrictions on creation and processes.

4. Omit: Fields with omit setting are ignored by the software. These fields are not displayed on the software's UI and any past data in these fields is ignored.

You can learn more about field settings and how to modify them here.