Hi @Erica2 ,
1. our preservers list (use condition to preserve only the data you want)
sys_properties // extract all properties by Application scope wise for dev and test
sys_user_has_role // impersonator roles and special role are given to some of my clients
sys_user // users manually created for testing purposes and integration user for dev and test
ecc_agent_config //mid server related table
sys_user_group // group only created for dev and test
sys_user_grmember // group members related to group.
Task table(incident+change) // filter the conditions as per the client request. these inc,change are created via integration for us which need to be tracked down
2. Our Exclusions list
Email properties // most important
mid server // mid server which we don't want to duplicate as its not required
discover schedule // the discovery jobs not required . individually import only if required
discovery status // they should not be cloned
logs // any kind of logs. they are already OOTB excluded
Any kind of table which provides real time data or its very big( 100 million records) we exclude it
3. you can create your own post-cleanup scripts. In our case we cleanup notification logs so that email notifications do not trigger which are in ready state (or simply add them in exclusion table)
4. post cloning dump the backup we have taken before monday morning.
There are total of 6 scenarios of cloning where it takes combination of exclusion and preservers
very well explained in this article
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0717012
If you have any doubt/query related cloning, everything is mentioned in this below article
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0715621
If you find it helpful, please mark my answer as correct so that it can useful to others.
Thanks & Regards,
Sumanth Meda
