Skip to main content
New Idea

Mandate Asset field based on Asset State

Related products:Freshservice
  • November 19, 2025
  • 6 replies
  • 42 views

AmalinaQ
Apprentice
Forum|alt.badge.img

I would like to request a feature that allow us to mandate certain field in Asset module when asset state is set to certain value. It caused incomplete data record and improper asset tracking. Due to our business operation, we have more than 10 site office. Thus, i need every asset assigned with a site office detail when asset is set to “In Use”

Currently the Asset module doesn’t provide any way to enforce required fields. Unlike the ticket, change or service item that we can configure through business rule. This creates issues where assets move from one state to another, but important fields are left blank because there’s no validation.

For example, when an asset moves to “In Use,” we may want to require “Assigned To,” “Location,” or other key fields — but we can’t enforce this today.

Adding conditional mandatory fields would help:

  • Improve data accuracy and completeness

  • Ensure proper asset tracking throughout the lifecycle

  • Reduce manual follow-up and errors

This would be extremely useful for us who rely heavily on asset data to ensure accurate tracking.

6 replies

richard_wills
Contributor
Forum|alt.badge.img+2

In addition, the ability to filter by Asset State on the  all (list) asset views. There is no ‘easy way to define clearly when an asset might be ‘spare’ or ‘in use’ from a list view. I have to assume the ‘last updated’ time denotes it is in use or not.


Daniel Söderlund
Top Contributor ⭐
Forum|alt.badge.img+14

Business rule for forms are on the roadmap  


Forum|alt.badge.img+9
  • Contributor
  • December 4, 2025

Also being able to see when the person who last logged into the device, the date and time they did last log in so we know if that device is actually being used.


Daniel Söderlund
Top Contributor ⭐
Forum|alt.badge.img+14

Also being able to see when the person who last logged into the device, the date and time they did last log in so we know if that device is actually being used.

The agent adds who logged in to the device. Not sure about timestamp 


  • Community Debut
  • December 5, 2025

Adding conditional mandatory fields would definitely improve tracking and reduce errors. For inspiration on how simple rules can guide choices, check out the 7 Brew Secret Menu it shows how small enforced options make the experience smoother.


Forum|alt.badge.img+9
  • Contributor
  • December 7, 2025

Also being able to see when the person who last logged into the device, the date and time they did last log in so we know if that device is actually being used.

The agent adds who logged in to the device. Not sure about timestamp 

You can have who the device is assigned to and also have SCCM or Intune write to say who last logged into the device. SCCM also has the time-stamp of when they last logged in.