Interested in a ServiceNow event built for developers? Registration for now[dev]26 is officially open!

Collision Avoidance

marclindsay
Tera Guru

I found a feature called Collision Avoidance in ServiceNow Studio Classic:

https://www.servicenow.com/docs/r/xanadu/application-development/servicenow-studio-classic/collision...

However, it appears to be specifically related to the Legacy ServiceNow Studio experience and is no longer supported beginning with the Xanadu release.

 

Does anyone know if an equivalent feature exists in Zurich or later releases?

 

The reason I am asking is that, while we use Git for source control, developers can only commit the current version of an object. There are situations where multiple developers modify the same object without realizing it, resulting in changes being unintentionally excluded from Git.

 

Example Scenario

  • Developer A modifies a Script Include, with the changes captured in Update Set A.
  • Developer A does not commit the changes to Git because testing is still in progress.
  • Developer B modifies the same Script Include, with the changes captured in Update Set B.
  • Developer A completes testing and commits Update Set A to Git, unaware that Developer B has since modified the Script Include.
  • From Git's perspective, the Script Include changes originally made by Developer A are no longer part of the current version of the object and are therefore not included in the commit.

As I understand it, the Collision Avoidance feature would have notified Developer B that Developer A was already working on the same object before Developer B started making changes. This helped prevent developers from unknowingly overwriting each other's work.

 

I am trying to determine whether a similar capability exists in Zurich or later releases to help identify potential development conflicts before changes are made.

0 REPLIES 0