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


---

# Request app deployment

# Request deployment for your app from Creator Studio to production {#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

After you've tested your app's forms, playbooks, and workspace category on a non-production instance, for example a development instance, deploy it to a production instance so users can access it.

## Antes de Iniciar

Your admin must set up a deployment pipeline before you can submit your app for review. Contact your admin if you need a pipeline configured.

To request that your app is deployed to production, you must be given permission to work on the app.

## Por Que e Quando Desempenhar Esta Tarefa

You can't cancel the review cycle after you submit an app for deployment review, so make sure that your app is ready to go.

## Procedimento

1. Go to AllApp EngineCreator Studio to see all the apps on the Creator Studio home page.
2. Open the app that you want to deploy to production.
3. In the navigation panel, select Submit for review.  
   Figura 1. Submit for review
4. Select Continue on the Submit app for review modal.
5. Now you need to choose which published forms are visible to users in the catalog. In the Ready for review section of the Review request forms modal, select which of the app's published forms that you want to be available after the app is deployed by selecting the Visible to others option.  
   Figura 2. Review request forms for deployment
6. Select Continue when you're happy with the forms being deployed to production.
7. Next, you must decide which of the app's activated playbooks will run on production after the app is deployed. In the Review playbooks modal, select the Run on production option for each playbook that you want to run on records that the app generates.  
   Nota:  
   If you can't select a playbook, you need to go back to the Automations section of Creator Studio and activate it. If you need a refresher on that, check out [Activate a playbook in Creator Studio](https://servicenow-prod.fluidtopics.net/SKdgWzxszZpuiR3It_BUcQ "Activating a playbook means that it will run when its related form is created or updated on your non-production, development instance. However, the app must still be deployed to production.").

   Unactivated playbooks still get deployed to production with the app, they just won't run on the records unless your admin activates them on production or redeploys the app with the playbook activated.
8. Select Continue when you're happy with the playbooks being deployed to run on production.
9. Finally, make sure that all the release details for the published app are correct.  
   {#creator-studio-deploy-app-to-prod__table_a5n_phs_m1c__entry__2}{#creator-studio-deploy-app-to-prod__cs-version-guidelines-ph}

   | Field | Description |
   |-|-|
   | New version | [Version number](https://servicenow-prod.fluidtopics.net/ACNUyxL3haCoieGCkodBsQ#gloss-version-number "A number assigned to the app that increases with each subsequent time it's deployed.") of the app you're requesting for deployment. Creator Studio automatically generates an updated version number, but you can change it. Follow your organization's versioning guidelines, or use the x.y.z format, where x = major update, y = minor update, and z = patch. |
   | [Release notes](https://servicenow-prod.fluidtopics.net/ACNUyxL3haCoieGCkodBsQ#gloss-release-notes "The information about what's included in each new version of the deployed app. Release notes help administrators to track what the changes are between app versions.") | Details on what's changed in this new version of the app, or a general description of what the app does if this is its first version. |
   [Tabela 1. Versioning options for deployment]

   {#creator-studio-deploy-app-to-prod__table_a5n_phs_m1c}

   Read more about this step of requesting deployment in [App versioning and release notes for Creator Studio apps](https://servicenow-prod.fluidtopics.net/98F0eC6a9z6nvt5YYdjR3A "Each deployed version of an app must have a version number and release notes, which helps administrators track app usage and changes.").  
   Figura 3. App versioning info
10. Select Submit for review when everything is correct and ready for your admin to review and deploy.

## Resultado

Woohoo! Your app is ready to be reviewed for deployment.

## O que Fazer Depois

Your admin uses Pipelines and Deployments to deploy the app to production. You can still make changes to the app after it's been deployed, you'll just need to request re-deployment when it's ready.

If you're an admin, check out [Managing deployments using Pipelines and Deployments](https://servicenow-prod.fluidtopics.net/p4KWA05EBxVSP7BKabQFYg "Manage deployments using Pipelines and Deployments in the App Engine Management Center (AEMC).") for the scoop on deploying apps.