Development Management I frequently get asked about managing development output when using Update Sets. Previous articles have covered individual aspects of update sets and batching before, but this entry will try to put the parts together. ServiceNow has update sets, application repository, plugins, store, share, and GitHub to hold and deploy application files. On top of development itself also contains best practices, code reviews, conflict management, manual testing, automated testing.
Release Process Properly managing your development work and how it is stored and released is often as important as the development work itself. None of us want to have the management of our update sets jeopardize successful releases. I will share some of the tips and methods for making the ServiceNow release process easier from my experience managing the release process at multiple companies. Batching With the Jakarta release, and improvement to update set management was introduced.
Reviewing Skipped Items The London release introduces a new tool for debugging upgrades and we will look at an overlooked but time-saving Jakarta release item as well. As a customer and partner, I have done quite a few ServiceNow upgrades. Helping others in the community with their upgrades has been a long-running theme. There are some newer platform features which I think are worth sharing with the community. There are several reference documents for the full upgrade process here.