---
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 - Author elective and customer updates

# Legacy - Author elective and customer updates {#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

When you install an application from the application repository or ServiceNow® store, you can set a series of properties to define the behavior of
delete and choice processing. These kinds of choices are called an "author-elective" feature.  
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 author elective {#tips-customer-updates__section_wsf_fnv_mqb}

You can find details on these properties in the [Skipped records that occur during application installation](https://www.servicenow.com/docs/access?context=generation-skip-records-app-installs&version=australia&pubname=australia-platform-administration&ft:locale=en-US) topic. With these properties,
you can opt in and out of deletes and choice updates depending on whether you are using your own
or a third-party application.  
When you install from source control, however, these records do not skip, except when a global application file is claimed by a different global application. Other than com.glide.apps.include_my_deletes and com.glide.apps.include_global_deletes that disable the processing of the author_elective_update folder altogether, those properties are not effective for source installed apps.  
Nota:  
An "absent" file detected in Delta loading for source control is vastly different than a Delete payload housed inside the author_elective_update folder. Author_elective_update properties do not prevent Delta loading in source control from deleting the file.

Similarly, update sets protect customizations that you make in an instance against incoming
changes that force a preview decision. Before you commit an update set, a preview must be run to
attempt to detect collisions. You must address all preview problems before committing the
changes. Source control may ask you to stash a local change, but the outcome of the installation
is to load what is present in the source even if a change had been made locally.

Loading what is present in the source is challenging when properties must have different
versions based on the target of the installation. For example, it's difficult to resolve when a
property containing an integration URL differs based on instance production role. The
is_private flag is effective with a source control installation and does
not overwrite the property if set, mitigating this concern.