This small utility allows ServiceNow developers to detect collision between update set before moving them to the upper-level environment. Additionally, it is also possible to analyse a specific developing element such as a business rule, script include, etc.
Disclaimer The utility relies on the release date attribute of an update set to identify which ones are already deployed to next environment. You can either manually set the release data every time you commit the update set to next environment or check out this other application which automates that job.
- Toggle on/off property allowing to disable the feature in the production environment.
- Analyse an update set which would be moved to the upper-level environment.
- Analyse a developing object which would be moved to the upper-level environment.
- Exclude out update sets already committed to upper-level environment.
- Exclude out update sets within the same batch.
The tool just finds update sets not yet delivered and not included in the same batch (if there is a batch...) than the update set in-hand that are touching the same configuration objects, but the tool do not check which one has update before or after the configuration object, therefore it is possible false positves.
Business rule My business rule has three versions in the following order:
- Update set
Update set Awhich has been delivered in the next environment. - Update set
Update set Bwhich has not been delivered yet. - Update set
Update set Cwhich has not been delivered yet.
Executing the tool over Update set B would return a collision with Update set C. In fact this is a false positive as the version Update set C was created only after the version Update set B thus moving Update set B is safe.
- Option 1. Clone repository