Field Rules for Assets
Background
Field Rules allow you to make specific information for an asset type required, or show a warning that recommended information is missing, when the asset reaches a specific status. This helps teams capture important information at the right point in the asset lifecycle.
Rules fall into three main categories: Required, Warning, and Computed.
Required rules prevent users from saving an asset until specified fields contain valid values. Use these for mandatory details needed to move forward, such as an Installation Date when an asset status is marked Installed.
Warning rules recommend information to users without blocking their progress, making them ideal for valuable data that should not delay ongoing workflows.
Computed rules automatically derive values from other fields to eliminate manual entry errors, such as calculating Remaining Cost (Purchased Price - Billed to Date) or Release Date (Required On Site Date - LeadTime).
Let's say that at the time of handover, you want the following information for each asset: Description, Trade, Vendor, Serial Number, Installation Date, and a Warranty Expiration Date. You could configure field rules to capture that information at the following places:
When Status is 'In Design', you can create a warning for a Description and Trade field.
When the Status is 'Delivered', you can require the Description, Trade, Vendor, and Serial Number.
When the Status is 'Installed', you can create a warning for Warranty Period and require the Location and Installation Date.
When the Status is 'Commissioned', you can require the Warranty Period field and create a computed field for Warranty Expiration Date using the formula formula for Installation Date + Warranty Period.
Introduce new data requirements using Warning rules first, transitioning them to Required rules once adoption stabilizes.
Establish a single "All Asset Types" rule for universal fields, creating specific asset type rules only for unique exceptions.
Keep formulas simple and manually convert long-term date intervals into exact day counts (e.g., multiply by 30 for monthly approximations).