---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/application-development

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Legacy - Collision avoidance

# Legacy - Collision avoidance {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

Avoid modifying an application file across different update sets to ensure seamless
experience during the commit process.  
Importante:  
Starting with the Xanadu release, the legacy version of ServiceNow Studio is being prepared for future deprecation. It will be hidden and no longer activated on new instances but will continue to be supported. For details on the deprecation process, see the [Deprecation Process \[KB0867184\]](https://support.servicenow.com/kb_view.do?sysparm_article=KB0867184) article in the Now Support Knowledge Base.

Try building and editing apps in the current version of ServiceNow Studio instead. For more information, see [ServiceNow Studio](https://servicenow-prod.fluidtopics.net/HJE5fDsb~bjmVZ9BqGtS8w "ServiceNow Studio provides a unified experience for all ServiceNow development activities, enabling admins and developers to extend base system solutions and create custom apps with ease. Use ServiceNow Studio to build apps and app files with integrated tools, access and edit app metadata in scoped and global apps, and package app changes for deployment, all in one powerful development tool.").
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__ul_bfb_qqk_plb}  
User can make changes to the application file only after selecting the required update set.  
Nota:  
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](https://www.servicenow.com/docs/access?context=r_AvailableSystemProperties&version=australia&pubname=australia-platform-administration&ft:locale=en-US) 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](https://www.servicenow.com/docs/access?context=r_AvailableSystemProperties&version=australia&pubname=australia-platform-administration&ft:locale=en-US) 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.