Configure 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).

Examples

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.

Tip
  • 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).

Things to Consider

  • General

    • Asset types in one rule must share the same status group.

    • Rules can be applied to all asset types or restricted to specific asset types.

    • Rules do not validate existing assets in advance; they apply upon asset creation, next status change, or next manual edit.

    • A single rule can cover several fields simultaneously.

    • New rules are active by default and apply when users change an asset's status. Inactive rules do not apply.

    • Rules are not retroactively applied to existing assets. They take effect when new assets are created, when an asset status changes, or during the next manual edit. Computed fields follow this same behavior.

    • If rules conflict, the rule for a specific asset type takes priority over the rule for all asset types. The stricter rule takes priority.

  • Errors

    • A Duplicate Rule Error occurs when a rule already exists for that combination of asset type, field, and rule type. Edit the existing rule to add additional statuses to its condition rather than creating a new one.

  • Limitations

    • Field rules apply only to data capture when an asset changes status. They do not control field visibility, or validate Attachments or Related Items.

  • Required and Warning Rules Show / Hide Details

    • A single rule can mandate multiple fields for the same status. Read-only fields cannot be made required.

    • Supported Field Types:

      • Allowed: Standard and custom fields that are set as optional within the fieldset.

      • Restricted: Fields already required in the fieldset, Checkbox fields, File Upload custom fields, and read-only fields cannot be used.

    • All selected asset types must share the same status group. You can align status groups for each asset type or create separate rules for each type.

    • Status conditions utilize OR logic (e.g., WHEN Status IS Commissioned OR Ready for Handover).

    • The ‘Field’ list shows only fields that every asset type has in common. For computed fields, only Number and Date fields show

    • If a status contains both Required and Warning rules on different fields, red and yellow asterisks appear simultaneously. Required rules are evaluated first, requiring completion before the warning pop-up displays for recommended fields.

    • Assigning both a Required rule and a Warning rule to the same field for the same status is strictly prohibited.

  • Computed Rules Show / Hide Details

    • Supported field types: Number and Date fields.

    • The Field list shows only fields that every asset type has in common. For computed fields, only Number and Date fields show.

    • Computed fields can be required. If a computed field remains empty when changing status, the system blocks the update until users populate the required source fields.

    • Computed fields can have both a computed rule and a default value. The computed value takes precedence whenever the formula yields a result. The default value is utilized only when missing input data prevents calculation.

    • Computed fields are read-only. To modify the calculated output, users must edit the underlying source fields.

    • Importing - Manual entries in computed columns are ignored during import and recalculated from relative source columns. Exported files display saved values, but manual edits made to those columns in spreadsheet software are discarded upon re-importing.

    • Errors

      • Incomplete formulas or explicit division by zero (e.g., Quantity0).

      • Incompatible field combinations (e.g., Date+Date) or mismatched target field output types (e.g., applying a Date-Date day count to a Date field).

      • Prohibited Formulas including Date + Date, Number - Date, and multiplying or dividing Date fields are not permitted.

      • Duplicate Computed rules on the same asset type and target field.

      • Circular formula references.

Prerequisites

Steps

Warning and Required Field Rules

  1. Navigate to the Company level Admin tool.

  2. Under 'Tool Settings', click Assets.

  3. Click the Rules tab.

  4. Expand the Field Rules section.

  5. Click Edit.

  6. Click Add Rule.

    1. Select the Asset Types that require the field validation rule. Select the target Asset Types.
      Note: Selecting 'All Asset Types' limits the Field list to fields shared in common across every asset type.

    2. Select the Fields from the drop-down menu that you want to require or recommend based on the status.

    3. Select  the Rule Type.

      • Required. Requires a value for this field before you can save changes to the asset.

      • Warning. Displays a warning when a field value needs updating, while still allowing you to save the asset.

    4. Click Add Condition, or click the condition hyperlink to edit an existing condition.

    5. Select the statuses that trigger the field being required or recommended. (for example, WHEN Status IS In-Design).

    6. Click Save to save the condition.

  7. Click Save in the rule’s row to finalize your field rule.

Computed Value Rules

  1. Navigate to the Company level Admin tool.

  2. Under 'Tool Settings', click Assets.

  3. Click the Rules tab.

  4. Expand the Field Rules section.

  5. Click Edit.

  6. Click Add Rule.

    1. Select the Asset Types that require the field validation rule. Select the target Asset Types.

    2. Select the Field from the drop-down menu that you want to calculate.
      Example: Warranty Expiration Date.

    3. Select the Rule Type.

      • Computed. Enters a calculated value to the field based on your equation.

    4. Click Define Rule, or click the formula hyperlink to edit an existing formula.

    5. Select the fields and the mathematical operators (+ - * /) to create your formula.
      Example: If you selected the Warranty Expiration Date field, your calculation might be Installation Date + Warranty Period.

      Notes
      • Formula Syntax: Standard mathematical operators (+, -, , ) can be used with any combination of fields and constants.

      • Order of Operations: Standard operational precedence applies (e.g., 7+23=13). Optional parentheses can group calculations, such as (A+B)(C+D).

      • Target Fields: Each rule fills a single target field. Only one Computed rule is permitted per asset type and target field combination.

      • Chained Rules & Circular References: Using one computed field within another formula is permitted, but circular references (A depends on B, B depends on A) are blocked upon saving.

      • Date Calculations: Date math counts strictly in days. Adding or subtracting a number from a date modifies the day count. Users must manually input fixed day increments for longer periods (e.g., 7, 30, or 365 days), as the system does not account for varying month lengths or leap years. Fractional days round up to the next whole day.

    6. Click Save to save the formula.

  7. Click Save in the rule’s row to finalize your field rule.

See Also

Loading related articles...