ServiceNow Best Practices: Track and Manage Configuration Changes Using Update Sets

[BillMartin]

ServiceNow developers and administrators configure and build changes to provide enhancements, fixes or probably add a new feature to an existing module.

Knowing and understanding what to change and the impact of the conversion gives confidence to the platform owners of what will be the future state of the target instance.

The ability to document information about the changes and the features to be added gives full recognition of the possible effect on what's to be provided.

However, inspite of all the quality controls in place the ability to commit and rollback the feature or fix that has been added gives a tremendous value in the ability to track and revert to the platforms original state.

Drilling down.

ServiceNow update sets does all of these capabilities. The faculty to cherry pick, merge and reverse changes to your production instance gives you the capacity what has gone right and wrong.

Managing a whole ecosystem starting from a small picture from the implementation until it goes complex and massive.

To See it in Action Here is How: ServiceNow Best Practices: Track and Manage Configuration Changes Using Update Sets

[Mark Manders]

And what is your question?

[BillMartin · Accepted solution]

hey @Mark Manders , i hope you understood the context that it is meant to be informative. let me know if you need help or further explanation.