I have a question around migrating licenses from legacy ITAM tool to ServiceNow sub-PROD using entitlement import in Software Asset Workspace , and then promoting those licenses from sandbox to higher env using XML export.
We have a few sub-PROD environments like Sandbox , DEV , QA and Finally PROD
My proposal is going to be that we need to perform import using entitlement import in Software Asset Workspace in all env (For entitlements / licenses. Allocations is a different things. We are currently creating allocations manually but I have advised them that manually creating allocations is okay only in sub-PROD, but in PROD it needs to happen via Integrations and Discovery)
However, I need to provide evidence that XML export is a bad idea vs running import job from Software Asset Workspace being a good idea.
For this , I have come up with this -
In sandbox , I have performed importing from SA Workspace. If I try to delete a license from alm_license table , system throws a warning saying the related relationships will also be deleted
Then, I just take an XML export of licenses in sandbox and create licenses in DEV using the XML export. I try to delete the license from DEV alm_license and the system just throws a casual dialog box asking “are you sure you want to delete this record”?
Is this good enough? Would you please advise a better idea to demonstrate that XML export is a bad idea as compare to full fledged entitlement import ?
