---
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 - Using MID Server with source control

# Legacy - Using MID Server with source control {#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

The ServiceNow® MID Server enables communication and the movement of data between a ServiceNow instance and external applications, data sources, and services.  
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.").

## How bundle files work with MID Server {#tips-source-control-midserver__section_m1g_dnd_sqb}

The .bundle file helps source control function with a MID Server. A
bundle file is the way Git packages a local repository in a single file. This makes sharing or
moving the repository simpler and more streamlined. The file is then sent to the MID Server,
which passes it on to the remote repository.

The `outgoing.bundle` (commit operations) and `incoming.bundle`
(apply remote changes) are attached to the MID Server attachment table \[ecc_agent_attachment\]
for any request that goes to the MID Server. The `outgoing.bundle` is created on
the instance while the `incoming.bundle` is created on the MID Server.

After an operation completes successfully, the bundle file is "promoted" into a
`golden.bundle` that is attached to the Repository configuration table
\[sys_repo_config\]. It's used to initialize the repository on a node that has not performed any
Source Control operations yet.

The Auto Flush tool \[sys_auto_flush\] is a "table cleaner" that removes any
`ecc_agent_attachment` record older than 30 days. This action removes the
corresponding attachment as well.

The bundle files are kept on the MID Server and then saved to the Import directory on the MID
Server.

On the MID Server, the bundle file is saved in the Import folder. This folder is under the
user directory defined by the system property (user.dir), which users can configure. The bundle
file is removed as part of the system flushing at the end of every operation.

## Working with the MID Server {#tips-source-control-midserver__section_zyp_yxm_4qb}

Nota:  
Source control operations can take more time for larger applications when using an MID server, as the entire app is bundled after an export and is dependant on the size of the app.  
* Avoid conflicts with Discovery and create files for the system attachment \[sys_attachment\] table: [MID Server](https://www.servicenow.com/docs/access?context=mid-server-landing&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US)
* Learn about system properties restrictions: [Configure attachment system
  properties](https://www.servicenow.com/docs/access?context=t_DisablingTheDragAndDropFeature&version=australia&pubname=australia-platform-administration&ft:locale=en-US)
{#tips-source-control-midserver__ul_klq_npd_sqb}