Overview
When you are planning and installing assets, you gain additional pieces of information along the way. Data validation field rules help teams capture accurate information at the right time so that required information is available at handover.
For example, when you are first procuring assets, you may know the Description of the asset and the Trade. When the asset is ‘Delivered’, additional information such as the Vendor and Serial Number are available to record. When the asset is ‘Installed’,the Location and Installation Date can be added. Once the asset has been 'Commissioned', you can require the Warranty Period and calculate the Warranty Expiration.
Configured field rules enforce these required inputs at each status change, ensuring incomplete records cannot be saved. By capturing accurate data as it becomes available, teams maintain complete records for handover without extra work or backtracking.
For users working with the assets, updating an asset's status highlights configured fields as suggested (yellow) or required (red). Users must complete all required fields before saving. Computed number and date fields cannot be edited directly; to update them, users must change their underlying source fields.
Rules fall into three main categories: Required, Warning, and Computed.
Required Rules: Make fields mandatory based on asset status. Users cannot save changes if required information is missing, but they retain the ability to edit the field. An example includes requiring an Installation Date when an asset status is set to ‘Installed’.
Warning Rules: Recommend fields based on asset status. If recommended information is missing, users receive a warning but are still permitted to save. Users can edit these fields. An example includes recommending a Serial Number when an asset status is ‘Installed’.
Computed Rules: Automatically calculate field values upon creation or editing. The fields remain read-only and cannot be edited manually. If information is missing, the field remains blank or uses its default value. An example includes calculating Warranty Expiry by adding a Warranty Period to an Installation Date.