---
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


---

# Working with update sets

# Working with update sets in ServiceNow Studio {#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

An update set is a group of configuration changes that can be moved from one instance to another. This feature allows administrators to group a series of changes into a named set and then move them as a unit to other systems
for testing or deployment.

If you're an admin, you might work with update sets in ServiceNow Studio to move changes through your instances. Access update sets from within an individual application or from the Deployment tab. Most of the ways you can interact with update sets
in ServiceNow Studio are very similar to how you would use them on the ServiceNow AI Platform. For more information about tasks you can accomplish with update sets, see [System update sets](https://servicenow-prod.fluidtopics.net/2n0mjX_i1izL9pTdrKeFbQ "An update set is a group of configuration changes that can be moved from one instance to another. This feature allows administrators to group a series of changes into a named set and then move them as a unit to other systems for testing or deployment.").  
Administrators have the following options with update sets.

* Create an update set to store local changes.
* Select the current update set to store local changes.
* Commit an update set to prepare it for distribution.
* Report on the contents of update sets.
* Compare update sets to determine what differences they contain.
* Merge separate update sets into a single update set.
* Create an external file from an update set.
* Retrieve update sets from remote instances.
* Apply retrieved update sets.
* Back out changes applied from an update set.
* Set system properties related to update sets.
* Promote update sets for deployment via ReleaseOps. For more information, see [ReleaseOps](https://servicenow-prod.fluidtopics.net/al3hlKK44SVWAPJk1IOg8A "ReleaseOps automates deployment of changes across your pipeline, increases predictability and reliability of deployments, and reduces the risk of releasing changes to production.").
{#working-with-update-sets-in-servicenow-studio__ul_sjh_5pf_5cc}  
Delegated developers have the following options with update sets in ServiceNow Studio.

* Create an update set to store local changes.
* Switch between update sets easily using the update set picker.
* Package changes for deployment using the Publish button in any app.  
  Nota:  
  If your app was created in ServiceNow IDE and converted to Fluent, you must switch from ServiceNow Studio back into the ServiceNow IDE for the publishing and deployment process.
{#working-with-update-sets-in-servicenow-studio__ul_dzm_n5f_5cc}
* **[Create an update set in ServiceNow Studio](https://servicenow-prod.fluidtopics.net/6kjiOQEKQW0U7fFe5LhSGg)**   
  Create an update set to package app changes for deployment in ServiceNow Studio.
* **[Mark an update set complete in ServiceNow Studio](https://servicenow-prod.fluidtopics.net/E1Y_cT8dBdzDoiGX2gfybA)**   
  Mark an update set as Complete in ServiceNow Studio to enable your changes to be retrieved by other instances.