- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-11-2024 01:08 PM - edited 11-11-2024 01:22 PM
Hello SME's!
I am helping set up HAM for our proprietary needs. I noticed that the 'Assigned' date in the 'General' tab auto-populated after referencing the ticket that the hardware was deployed to. I also noticed that the Installed Date does not auto-populate. Is there a certain state or sub state that influences this workflow OOB? Or is a Business Rule needing to be created for static hardware like Servers or Blades in a Chassis since they are 'Installable" unlike Computers that can vary in location on a day to day basis.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-11-2024 05:53 PM
@DillynITPDC Assigned Date:
This field is usually auto-populated when the asset is associated with a user or a request (e.g., a fulfillment task or incident).
OOB, ServiceNow uses Business Rules or Workflow Actions to update the Assigned Date when an asset’s State changes to "In Use" or when the asset is linked to a ticket indicating it has been issued to a user.
For example, if you associate the hardware asset with a Deployment Task or a Transfer Order, the Assigned Date is typically updated automatically.
Installed Date:
The Installed Date is intended to reflect when the asset was physically installed or placed in its intended environment (e.g., a server rack).
OOB, the Installed Date does not auto-populate because it requires confirmation of physical installation, which is often a manual process, especially for fixed hardware like servers, blades, or networking equipment.
For movable assets like laptops or desktops, the Installed Date might be updated via discovery tools or manual updates, as these devices frequently change locations.
You can create a Business Rule that updates the Installed Date when the asset’s State changes to "Installed" or "In Use".
Hope this will help you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-11-2024 05:53 PM
@DillynITPDC Assigned Date:
This field is usually auto-populated when the asset is associated with a user or a request (e.g., a fulfillment task or incident).
OOB, ServiceNow uses Business Rules or Workflow Actions to update the Assigned Date when an asset’s State changes to "In Use" or when the asset is linked to a ticket indicating it has been issued to a user.
For example, if you associate the hardware asset with a Deployment Task or a Transfer Order, the Assigned Date is typically updated automatically.
Installed Date:
The Installed Date is intended to reflect when the asset was physically installed or placed in its intended environment (e.g., a server rack).
OOB, the Installed Date does not auto-populate because it requires confirmation of physical installation, which is often a manual process, especially for fixed hardware like servers, blades, or networking equipment.
For movable assets like laptops or desktops, the Installed Date might be updated via discovery tools or manual updates, as these devices frequently change locations.
You can create a Business Rule that updates the Installed Date when the asset’s State changes to "Installed" or "In Use".
Hope this will help you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2024 08:41 AM
Very insightful, thank you @Abhay Kumar1. I think our team will have to go the route of a Business Rule to Auto-populate when someone reaches the network, or when the Assigned to is auto-updated.