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


---

# Add events to track components with unsaved changes

# Add events to track components with unsaved changes {#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

Locate dirty state components through event configuration.

## Antes de Iniciar

Role required: ui_builder_admin

## Por Que e Quando Desempenhar Esta Tarefa

You can add the Screen status changed to dirty event to check which components have unsaved changes. This avoids having to manually inspect advanced properties on events for each individual component.
Once added, the event remains available in the configuration panel for direct access.

## Procedimento

1. Navigate to AllNow Experience FrameworkUI Builder.
2. Open an experience to work in or create an experience by selecting CreateExperience.  
   See [Configure how users interact with your applications in UI Builder](https://servicenow-prod.fluidtopics.net/dUVGdKGQs6AbFNSw~vNKcQ "Learn what an experience is in UI Builder. Understand what an experience contains.") for more information on creating experiences.
3. Create or open a page.
4. In the content tree, select + Add content to add a component.
5. Select a component from the toolbox and select Add.  
   For example, select a Button.
6. Add an event to the component.
   1. Select the Events tab in the configuration panel.
   2. Under Button clicked, select Add handler.
   3. Under Choose a handler, enter <kbd class="ph userinput">isDirty</kbd> (or <kbd class="ph userinput">dirty</kbd>) into the search bar.
   4. Select the Screen status changed to dirty event and select Continue.  
   5. Select the Screen is dirty check box to mark the property as `true`.
   6. Select Add.

   {#dirty-state-event__substeps_b2v_hyj_jgc}  
   The dirty state event now appears in the configuration panel, enabling you to quickly check the `isDirty` property and determine if the component has unsaved changes without adding additional events.