Avoid modifying an application file across different update sets to ensure seamless experience during the commit process.

Important: You've landed at the legacy version of Studio, which will be supported until the Australia release in Q1 2026. Try building and editing apps in the new version of ServiceNow Studio instead. For more information, see Building applications with ServiceNow Studio.
When the logged in user opens an application file that was modified in an update set different from the user’s current update set for the corresponding application:
  • Collision is detected in the application file and a warning message is displayed.
  • Logged in user to prompted to choose an update set.
  • Read-only protection policy is applied to the application file.
Collision avoidance message
User can make changes to the application file only after selecting the required update set.
Note: This feature is applicable to only those applications that are linked to GIT.

Enable or disable the collision avoidance feature using the glide.ui.vcs.collision_avoidance property in the System Property [sys_properties] table. By default, the feature is enabled. See Available system properties for more information.

When the feature is enabled, users can't work in the default update set of the application. If a user is assigned the default update set, a unique update set is created when the user logs in to the application for the first time after the collision avoidance feature is enabled. This new update set is specific to the user in current application.

Name of the update set specific to the logged in user is, User ID or user name based on the value specified for the glide.ui.vcs.updateset_identifier property in the System Property [sys_properties] table. See Available system properties for more information. By default, the update set name is set to user name of the logged in user. However, users can rename the update set.