How to get Change Management back to OOTB after several changes

[bostonsnow]

Hello,

What is the best way to reset Change Management back to OOTB? We made several changes to some of the forms that were deemed to be too complicated and our MT is wanting to go back to OOTB. All of the changes were captured in Update Sets but when I try to back them out they are all displaying the following error:

"The change was not backed out because changes were made to the record after the update set was committed, or if multiple edits were made then the outside change may have been between edits. You can still revert to a particular version from the record"

Any help you can offer is greatly appreciated.

Thanks!

Mike

[williamsun]

This is usually referred to as "getting bank into the box"  XD

It is complicated because things will even change from release to release.

I think the easiest way would be to request a developer instance (which comes free and completely out of the box) or ZBOOT one of your sub-production instances (making it out of the box) and then just comparing side by side what fields you might have removed or added.

Do you know if other changes were made?  Like business rules, client scripts or UI Actions that relate to that table/form?

[bostonsnow]

Hello Williamsun,

Thanks for your reply! The changes were limited to form layout and custom field changes. Is it possible to ZBOOT just one module and not the entire instance? I just need to get Change Management back in the box without affecting our other modules. If not I'll take your other suggestion of firing up that dev instance.

Thanks!

Mike

[williamsun]

I don't believe you can reset just one particular item.

There is another option, to go to the Customer Updates table.  This is where every single customization is stored, and find those customizations that were done on the change_request form.

this will take you to that list of updates to form layout on the change table:

https://your_instance.service-now.com/sys_update_xml_list.do?sysparm_query=type%3DForm%20Layout%5Etarget_name%3DChange%20Request

you could try to revert the changes if you are able to make a list of them here, but then, this is just a longer way of doing the dev instance compare.

Another way might be to simple delete the form and form sections, but this might cause problems as you might get stuck with a blank form.

I think the cleaner/safer option is to fix it by compare to a new dev instance, and then in the future, whenever you want to add or change stuff for testing, you might want to create a new "view" and modify that, while leaving the Default view with the out of the box config.