Customization vs Configuration

10382
Kilo Contributor

Is there a good definition on the difference between making a customization to a field or table in Service Now, versus making a configuration change?

I understand that if I customize a field, should there be changes to that field in a new release, that in my environment the upgrade changes would be skipped.

Is that correct?

A little fuzzy on the differences.

Thank you!

Julie

1 REPLY 1

davidself3
Tera Contributor

Yes, I recently went through an upgrade from Calgary to Eureka at a client. I was given the arduous task of going through the upgrade log and deciphering if things were simply looked at and updated or if they were legitimately changed and needed to be avoided. If nothing had been changed, I reverted it back to original in an update set and promoted that through QA and Prod.



Then we cloned the dev instance with my applied update set, and re-ran the upgrade. It worked, and upgraded the various areas as it should.



So to clarify, if you look at something like an ACL, and click "update" or "save" and make no changes, that alone will let the upgrade skip that sys_id.