---
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 - De-noise your source control commits

# Legacy - De-noise your source control commits {#ariaid-title1}

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

As a source control developer, you can merge the Git branches, without getting noise
from the fields that are auto-updated by the system.  
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.").

## Overview of de-noising {#denoise-source-control-commits__section_i34_mxc_35b}

In Studio, the Source Control feature packages application files as XML
payloads, when they are exported to Git repositories. When a user merges Git branches in a Git
repository as part of the application development workflow, the user must resolve any conflicts
in the XML files. These conflicts are typically in the fields that are system generated, like
sys_updated_by, and represent non-user generated changes. The user must be careful when they are
resolving conflicts in these fields because this process might create more noise.

## Saver Exempt attribute {#denoise-source-control-commits__section_kl2_qxc_35b}

Features have been added in Source Control to de-noise the XML payloads, to assist the user in
resolving the conflicts when the Git branches are merged.

By default, the system sets the saver_exempt attribute for certain fields in tables whose
values are auto-generated by the system. For more information on the saver_exempt attribute, see
[Dictionary attributes](https://www.servicenow.com/docs/access?context=c_DictionaryAttributes&version=australia&pubname=australia-platform-administration&ft:locale=en-US).

The following table contains the saver_exempt values.
{#denoise-source-control-commits__table_x1y_m1d_35b__entry__4}

| Fields | System Tables | saver_exempt values | Outcome expected |
|-|-|-|-|
| * sys_updated_on * sys_updated_by * sys_mod_count {#denoise-source-control-commits__ul_t3j_q1d_35b} | * sys_metadata * sys_choice * sys_package * sys_app_customization * sys_claim * sys_package_dependency_m2m {#denoise-source-control-commits__ul_c5f_t1d_35b} | exempt_vcs_only | The fields are not written to the corresponding XML representation of a record for the table during the packaging of the application for Git commits. |
| Sys_id | * sys_dictionary * sys_documentation * sys_choice {#denoise-source-control-commits__ul_q44_z1d_35b} | exempt_vcs_only | The sys_id field is not written in the XML representation of the record of three tables during the packaging of the application for Git commits. |
| Fields with loader_exempt=true |   | exempt_always | The fields that have loader_exempt set to True are not loaded in the instance. They are not written to the XML representation of the records in the tables during the packaging of the application for Git commits |
[Tabela 1. Saver Exempt attribute table]

{#denoise-source-control-commits__table_x1y_m1d_35b}

## Disabling the tracking property {#denoise-source-control-commits__section_cbp_qbd_35b}

An admin can disable the
`glide.source_control.disable_tracking_of_update_fields` so that the fields do
not display user-generated values.  
Nota:  
The following fields are not written to XML during source control commits, and their values in the instance are loaded from a Git commit. If an admin wants the system to write these fields to XML and use the system-generated values for these fields, the admin can set the property `glide.source_control.disable_tracking_of_update_fields` to False.

The following fields are the system-generated values that the admin sees:

* sys_updated_by = commit user
* sys_updated_on = commit time
* sys_mod_count = zero
{#denoise-source-control-commits__ul_dkb_fcd_35b}

## sys_id fields for tables {#denoise-source-control-commits__id_asf_zl2_35b}

The sys_id field for tables are saved in the corresponding "dictionary/\<tablename\>.xml" so
that they are not regenerated during the installation in the instance, other than when tables
are created. The result is that the noise is reduced from all the XML files that reference the
sys_id of the table or represent the sys_db_object record for this table.