You should have a Reconciliation job setup to handle "Purge" which deletes CI's that have been flagged for delete.
Your User permission is the Asset User for CI's where the user is in the supported by role or Asset Admin for any CI.
You do not want to give Asset Admin to very many people since it has CMDB super powers, can create/edit any an all CI's and relationships.
Now, whatever user has permission for the particular CI can change the status on the CI (in the asset management forms) to Delete.
Then your "Purge" job will take care of it based on the rules setup for the Recon Job.
The Recon Job you mean is creating job in CMDB?
So based on your experience there is no permission except Administrator that could delete the CI record?
I think we could stand with Asset Admin then. because what we prevent is user as Asset Specialist/Coordinator cannot change any of foundation data like People. then we will consider again in making job that could do that action.
1 of 1 people found this helpful
The Asset Admin can change the status to Delete. You either need to have the recon job to "Purge" those items, or your Remedy Administrator will have to perform the delete. But having the Remedy Administrator perform the delete will generate errors that doesn't completely delete the records, and the Remedy Administrator will/may have to perform a delete on multiple behind the scenes records. Work with BMC Support to get your Purge job setup correctly and set the Asset record to Delete status.
Thanks for your explanation Bob, I think so. Deleting CI records with Admin permission is not the best option. So I may contact BMC support to assist me in purge job setup.