| Name | Object | Error Message & Description | Default State | Mirrored in Apex |
|---|---|---|---|---|
| Check_asset_manager | Asset_Owner | Error Message: Please select a Salesforce user when the ‘Can Manage Assets’ field is checked. Description: The Validation Rule exists solely to display an error message in the UI for users when certain conditions are met. There is equivalent validation logic implemented in Apex | ✅ | ✅ |
| Change_Value_type | Asset_Property | Error Message: You can’t change the value type while at least one asset is using this property. Description: The Validation Rule exists solely to display an error message in the UI for users when certain conditions are met. There is equivalent validation logic implemented in Apex | ✅ | ✅ |
| Equal_recipient_and_sender_restriction | Asset_Transfer | Deprecated | ||
| Wrong_Recipient_for_To_admin_direction | Asset_Transfer | Error Message: Asset owner with “Can manage assets” enabled should be selected in “Asset recipient” field for transfer direction “User to Admin” Description: The Validation Rule exists solely to display an error message in the UI for users when certain conditions are met. There is equivalent validation logic implemented in Apex Fires only when the recipient is set or changed, so un-checking an admin’s “Can manage assets” later cannot freeze transfers that already name them. | ✅ | ✅ |
| Wrong_Sender_for_To_User_direction | Asset_Transfer | Error Message: Asset owner with “Can manage assets” enabled should be selected in “Asset sender” field for transfer direction “Admin to User” Description: The Validation Rule exists solely to display an error message in the UI for users when certain conditions are met. There is equivalent validation logic implemented in Apex Fires only when the sender is set or changed, so un-checking an admin’s “Can manage assets” later cannot freeze transfers that already name them. | ✅ | ✅ |
| restrict_change_field | Asset_Unit | Error Message: You cannot change Asset “Name”, “ID”, “Type” and “Bundle” when Asset in Status “In Use”, “Reserved” or “Disposed”. | ✅ | |
| restrict_change_owner | Asset_Unit | Error Message: You cannot set user except you for new asset. You cannot change Asset owner manually – please use Asset transfer object Description: The Validation Rule exists solely to display an error message in the UI for users when certain conditions are met. There is equivalent validation logic implemented in Apex | ✅ | ✅ |
| restrict_status_change | Asset_Unit | Error Message: You cannot manually set or change Status values: “Reserved”, “Disposed”, “In Use” and “Bundled”. Please use appropriate object. For “In Use” and “Reserved” use Asset Transfer, For “Disposed” use Asset Disposal, for “Bundled” use Asset Bundling Description: The Validation Rule exists solely to display an error message in the UI for users when certain conditions are met. There is equivalent validation logic implemented in Apex | ✅ | ✅ |
| Wrong_Recipient_archived_owner | Asset_Transfer | Error Message: You cannot transfer assets from/to owner with status “Archived” Description: Blocks naming an archived owner as recipient, but only when the recipient is set or changed, so archiving an owner later cannot freeze transfers that already name them. The Validation Rule exists solely to display an error message in the UI for users when certain conditions are met. There is equivalent validation logic implemented in Apex | ✅ | ✅ |
| Wrong_Sender_archived_owner | Asset_Transfer | Error Message: You cannot transfer assets from/to owner with status “Archived” Description: Blocks naming an archived owner as sender, but only when the sender is set or changed, so archiving an owner later cannot freeze transfers that already name them. The Validation Rule exists solely to display an error message in the UI for users when certain conditions are met. There is equivalent validation logic implemented in Apex | ✅ | ✅ |
| Wrong_Asset_Admin | Asset_request | Error Message: Asset owner with “Can manage assets” enabled should be selected in the “Asset Admin” field. Description: Blocks naming an owner without “Can manage assets” as Asset Admin, but only when the field is set or changed, so un-checking the box later cannot freeze requests that already name them — including the automated status update from the Change_Asset_request_status flow. Asset request has no trigger, so this rule has no Apex mirror. | ✅ | |
| restrict_duplicate_disposals | Disposal | Deprecated | ||
| Check_asset_status_for_disposal | Disposal | Error Message: Asset Units in Status “Available”, “Not Available” and “Repair or Warranty” only can be disposed. Description: Only lets a disposal be created for an asset in a disposable status. It fires on create only, so an existing disposal stays editable once its asset is “Disposed”, and because a disposed asset fails the rule it also prevents a later disposal on the same asset. Two disposals for one asset inside a single insert both still see the asset as available, so that case is caught in Apex instead. Skipped while Input Initial Values Mode is on. The Validation Rule exists solely to display an error message in the UI for users when certain conditions are met. There is equivalent validation logic implemented in Apex | ✅ | ✅ |
| Check_Disposal_date | Disposal | Error Message: Disposal date is required and cannot be in the future. Description: Ensures every disposal records the date the asset was actually disposed. The date may be earlier than the record creation date, but never blank and never in the future. | ✅ | |
| Check_Actual_dates | Repair | Error Message: Actual End date cannot be greater than Actual Start date Description: Ensures data integrity by preventing users from entering an Actual End Date that is earlier than the Actual Start Date. This rule enforces chronological consistency for project or task timelines within the ITAM application. | ✅ | |
| Check_Planned_dates | Repair | Error Message: Planned End date cannot be greater than Planned Start date Description: Ensures that the Planned End Date is not earlier than the Planned Start Date. This rule helps maintain logical scheduling of planned activities or projects within the ITAM application, preventing timeline inconsistencies. | ✅ | |
| Validate_date_fields_for_statuses | Repair | Error Message: To set “Planned” Status fill “Planned Start date”To set “In Progress” Status fill “Actual Start date” field and “Planned End date”To set “Completed” and “Failed” fill Actual Start date” field and “Actual End date” Description: Ensures required date fields are filled based on the selected status: – Planned: requires Planned Start Date – In Progress: requires Actual Start Date and Planned End Date – Completed/Failed: require Actual Start and End Dates | ✅ |