I do not see a whole lot of conversation on this topic, and maybe it is just because I am somewhat new to the ServiceNow experience.
In any given instance the Clone History table shows where THIS SOURCE has been cloned TO. That is great information to know, but how about the reverse angle? If I am in any given instance, how can I know A) when THIS INSTANCE was established as a clone and B) Which instance was it's SOURCE? If I wanted to know the source where an instance was cloned from, I would have to check the clone history of all my instances
But why couldn't the cloning automation insert a record in the Clone History as a breadcrumb of the source information. That should be a simple addition to the process (at least I think it would be), and I think it would be value add. From any instance you could then see the history of clones where I am the source AND when I was the target, where my data came from.
In lieu of this being added to the cloning automation (a la ServiceNow engineer / back-end server-based scripting), how about running a post-clone cleanup script which inserts a breadcrumb record someplace? I'd suggest the Clone History table, but maybe that is an off-limits system-managed table. and entry that you would prepare in advance of the clone which would announce "This was cloned from PROD" or something else meaningful. Ideally I'd love to record the source, target, date, time, initiator (person), request number or change number, and maybe if there were other meta-datq about the event. Maybe even a note about what tables were included, excluded, preserved, etc.
Does anyone have this question or concern? Does anyone have this already solved in your shop?
Respectfully submitted to this great community.
Rob
