AnyIty

Salesforce Applications Development

Asset Unit

API Name: ITAM_App__Asset_Unit__c

The Asset Unit object represents an individual IT asset within the organization’s inventory. These assets can include hardware (e.g., laptops, monitors, phones), software licenses, or other equipment assigned to employees for operational use. This object supports full lifecycle tracking of each asset, including assignment, availability, status changes, transfers, and disposal.

Each Asset Unit is linked to an Asset Type that defines default properties, and to an Asset Owner, which represents the employee currently responsible for the asset. Additional fields capture essential information such as serial number, origin, current status, and department assignment.


🔧 Key Functionalities

  • Tracks individual IT asset records with unique identifiers.
  • Links each asset to an Asset Owner, Department, and Origin.
  • Supports hierarchical asset structure using Parent Asset Unit (e.g., a dock connected to a laptop).
  • Stores dynamic custom properties based on Asset Type. Additionally, the object can store arbitrary custom properties unrelated to the Asset Type.
  • Enables validation bypassing for administrative purposes when needed.
  • Mass Clone Action – Easily duplicate up to 10 Asset Units at once (including their properties), useful when purchasing multiple identical assets in bulk.

📊 Asset Status Values

The Status field reflects the current state of the asset and is central to asset lifecycle management:

  • Available – The asset is unassigned and ready for use or reassignment.
  • In Use – The asset is currently assigned to an employee and actively in use.
  • Reserved – The asset has been marked for transfer or allocation but is not yet in use.
  • Repair or Warranty – The asset is temporarily out of service due to repair, maintenance, or warranty-related return.
  • Disposed – The asset has been officially retired and is no longer in the inventory.
  • Not Available – The asset cannot be assigned or used due to a temporary or unknown issue (e.g., lost, untraceable, or under investigation).

⛔ Statuses like Reserved, In Use, and Disposed are controlled by system processes such as Asset Transfer or Asset Disposal and cannot be manually selected.


⚙️ Record Page Features

The Asset Unit record page includes several features for usability and tracking:

  • Properties Component – Displays custom attributes dynamically based on the selected Asset Type.
  • Transfer Log – Shows a chronological log of all asset transfers.
  • Mass Clone Action – Clone up to 10 identical Asset Units with copied properties to streamline the process of adding bulk assets.

✅ Tips & Best Practices

  • When creating or updating an Asset Unit, assigning an Asset Type automatically pulls in default properties.
  • Use Parent Asset Unit to model asset dependencies (e.g., accessories assigned to a primary device).
  • Use Bypass Validation only in administrative or exception scenarios.
  • Make sure to update the Status field correctly as the asset moves through its lifecycle.
  • The Origin field is useful for tracking procurement source or initial registration of the asset.
  • Use the Mass Clone action to quickly replicate new assets during bulk equipment onboarding.

🔄 Asset Unit Status Change Matrix

From → ToChange Method / Object
Available → In UseAsset Transfer (Completed, direction: Admin to User)
In Use → AvailableAsset Transfer (Completed, direction: User to Admin)
Available → ReservedAsset Transfer (Status: Ready to Transfer, with “Reserved” checked)
Reserved → In UseAsset Transfer (Completed, Admin to User)
Available → DisposedAsset Disposal
In Use → DisposedAsset Disposal
In Use → Not Available🔄 Asset Transfer (User to Admin) → then 🖐️ Manual status update
In Use → Repair or Warranty🔄 Asset Transfer (User to Admin) → then 🖐️ Manual status update
Available → Not Available🖐️ Manual (via Asset Unit record)
Available → Repair or Warranty🖐️ Manual (via Asset Unit record)

⚠️ Notes

  • Statuses like In Use, Reserved, and Disposed are system-controlled — can’t be manually set.
  • Transitions from In Use typically require an Asset Transfer back to admin first.
  • Manual updates apply only when no process/object governs the transition.
Was this page helpful?
Authorization
*
*
Password generation