Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Check differences between instances PROD > DEV

Igor Aguiar
Tera Contributor

Hello, I've started working with a client, and they gave me the task of mirroring the GRC application in the DEV instance. Here’s the problem: the client doesn’t want to clone the PROD instance, so I have to do it manually.

I’m tracking the sys_update_version list, but it feels very fragile to me — I’ll probably end up missing something. What do you guys think would be the best approach, or how could I best reduce the chances of missing artifacts?

I tried using SwissNow, but it only compares records, not structures — or maybe I’m not looking at the right records?

Context: the client made all the implementation in the PROD instance, but now they want it in the DEV instance so the helpdesk team can work on incidents and upgrades.

2 ACCEPTED SOLUTIONS

Ankur Bawiskar
Tera Patron
Tera Patron

@Igor Aguiar 

Not a good practice to directly make changes in PROD.

At least customer should have DEV and PROD.

It's a tedious task to go through customer update and see what was customized and then do the same changes in DEV.

To do exact replica you will require some high level document what was done in that GRC application or some stories etc.

If you follow the sys_update_version approach you are bound to miss something or other.

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

View solution in original post

Hi @Igor Aguiar 

 

Do you still have any open issues?

 

Refer these tables:

 

sys_plugins

Provides installed date and activation status.

sys_plugin_log

Log files for the corresponding plugin installation.

sys_upgrade_history

Installation Start and Installation End time

sys_progress_worker

This monitors the actual plugin installation timestamp.

sys_metadata

To view the installed files.

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************

View solution in original post

5 REPLIES 5

Ankur Bawiskar
Tera Patron
Tera Patron

@Igor Aguiar 

Not a good practice to directly make changes in PROD.

At least customer should have DEV and PROD.

It's a tedious task to go through customer update and see what was customized and then do the same changes in DEV.

To do exact replica you will require some high level document what was done in that GRC application or some stories etc.

If you follow the sys_update_version approach you are bound to miss something or other.

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader