- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-30-2022 08:43 AM
Does your organization have a retention policy for specific types of hardware or hardware that contains/contained specific set of data? If so, did you try and use an OOB state and substate or did your organization create a custom State and/or substate? Is there a SN recommendation?
I'm putting in and idea request to have a CSDM Life Cycle Stage Status of "Legal Hold" created b/c I don't see any status that identifies this and I believe there are many organization that do have some sort of retention policy and this does not appear to be addressed by any of the OOB Life Cycle Stage Status options.
Thanks for any feedback on this.
Solved! Go to Solution.
- Labels:
-
Multiple Versions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-30-2022 10:02 AM
We frequently utilize the state of In Maintenance and then a custom field called Maintenance type with choices of Legal Hold and Temp Hold. Together with that we add Maintenance start date and Maintenance end date to be able to report on how long it's been in Legal Hold/Temp Hold
Temp Hold gives users one last chance to get something off the device. We often default the end date to two weeks out from the start date.
By having a seperate field for Maintenance type we can wrap additional permissions to read these records as the audience of who can see this records is typically reduced.
Also using In maintenance allows the assigned to not get wiped out and left at that users name.
Concerning upcoming CSDM Lifecycles, CSDM 4.0 has accounted for legal hold.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-30-2022 09:28 AM
For most of my customers, we have implemented 'Legal Hold' as a substate of "In Stock". Many also have a dedicated Stockroom and/or Location to associate items that are in a 'Legal Hold'. Implementing 'Legal Hold' as a substate of "In Stock" lets clients leverage the OOB functionality around changes to an asset's state.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-30-2022 10:02 AM
We frequently utilize the state of In Maintenance and then a custom field called Maintenance type with choices of Legal Hold and Temp Hold. Together with that we add Maintenance start date and Maintenance end date to be able to report on how long it's been in Legal Hold/Temp Hold
Temp Hold gives users one last chance to get something off the device. We often default the end date to two weeks out from the start date.
By having a seperate field for Maintenance type we can wrap additional permissions to read these records as the audience of who can see this records is typically reduced.
Also using In maintenance allows the assigned to not get wiped out and left at that users name.
Concerning upcoming CSDM Lifecycles, CSDM 4.0 has accounted for legal hold.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-30-2022 10:11 AM
Thanks for sharing this! This is exactly what I was looking for/wondering about.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2022 12:25 PM
Hi
Help me brainstorm this process, we have a team that recovers assets and wipes the device. When HR changes the employee status to inactive it triggers a workflow in ServiceNow an tasks are created to recover the device, these tasks are assigned to my group and we wipe it.
However, if there is a device that should be on legal hold, how can we trigger a workflow in servicenow that assigned the tasks to someone in legal department instead of it coming to my gorup, we cant wipe it so we wont be able to do anything about it, instead the task you go to legal team and they update the asset state?