--- 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 --- # Configuration tasks # Pipelines and Deployments configuration tasks {#ariaid-title1} * Versão de lançamento: Australia * * Atualizado 12 de mar. de 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 min. de leitura As you work through the Pipelines and Deployments guided setup, you must perform different configuration tasks on each of your instances. ## Setting up environments, pipeline records, and user access {#p-and-d-config-tasks__section_qw5_2qk_psb} The tasks for configuring Pipelines and Deployments are listed below, along with links to detailed instructions for completing them. These tasks build on each other, so it's important to complete them in the sequence listed in the Guided Setup. {#p-and-d-config-tasks__table_lqq_1qt_rhb__entry__3}{#p-and-d-config-tasks__otherprops-integration-3} | Instance | Task | Description | |-|-|-| | Production | Configure environment credentials. | Configure credentials for each instance in your pipeline so that the flows used by AEMC can access the instances in your pipelines. For more information, see [Configure environment credentials](https://servicenow-prod.fluidtopics.net/_7QF5y2NG0QDWG8cJjHU5A "Configure credentials in your production instance so that the flows used by the App Engine Management Center (AEMC) can access different instances."). | | Production | Configure environments. | Set up your production and non-production (that is, development, test, and/or staging) environments by adding the URLs and credentials used to access each instance. For more information, see [Configure your pipeline environments](https://servicenow-prod.fluidtopics.net/O2n_EgyX47hYCPl9AqEJuw "Set up your app development production and non-production environments (for example, development, test, and/or staging) by adding the URLs and credentials used to access each instance."). | | Production | Configure pipelines. | Set up and configure each pipeline by naming the pipeline, identifying each of the environments associated with the pipeline, and specifying the order in which apps are deployed between the environments in that pipeline. For more information, see [Configure your pipeline](https://servicenow-prod.fluidtopics.net/KMniirzfhMBai~xZXAc~Uw "Configure your app development pipeline so that your administrator can quickly move an application from one environment to another."). | | Production | Add users to the App Engine admin group. | Add users involved with this flow of tasks to the App Engine admin group. Nota: If already added users on the production instance using [AES guided setup](https://servicenow-prod.fluidtopics.net/SnfLL0O0LtImuZVYBJbVCg "App Engine Studio (AES) guided setup provides a sequence of tasks that help you configure AES on your ServiceNow instance.") or [Configure Application Intake](https://servicenow-prod.fluidtopics.net/1erz2wJla0W8e6tmOP0~GA "Use the App Engine Studio (AES) Application Intake guided setup to step through the initial configuration of the Application Intake application. Detailed instructions for each step are provided in subsequent sections of the product documentation.") guided setup, you can skip this step. For more information, see [Add users to the App Engine Admin group](https://servicenow-prod.fluidtopics.net/blJ5mUdv~f6sBi~_Lh956w "Add users to the App Engine Admin group in your production instance to give them administrative rights to App Engine Studio (AES). You must also identify a contact email address for the group. After you configure the email address of the App Engine Admin group, members can receive notifications for app development-related requests, including app intake requests."). | | Production | Add Automated Test Framework (ATF) and Instance Scan suites. | Add your customized test suites as part of an application deployment in addition to the instance scan and ATF testing suites that are standard in AEMC. For more information, see [Add ATF and instance scan suites for testing](https://servicenow-prod.fluidtopics.net/DH4BTDLvpVikENQnfjSRmA "Add your customized test suites as part of an application deployment in addition to the instance scan and Automated Test Framework (ATF) testing suites that are standard in AEMC."). | | Production | Enable Change Management integration | Connect an existing Change Management program with AEMC so that deployments through the pipeline to the production environment are automatically scheduled based on the Change request state and planned change window. For more information, see [Enable Change Management integration](https://servicenow-prod.fluidtopics.net/20wP81St3aoXJBil~igSIA "Enable Change Management integration with AEMC so that deployments through the pipeline to the production environment are automatically scheduled based on the Change request state and planned change window."). | | Production | Configure properties to integrate Change Management | Change requests and configuration items (CIs) are created using specifications set up in your existing Change Management program. If you want to change the change model, change template, or CI creation subflows used during app deployments, you must configure these properties during Guided Setup. For more information, see [Configure properties to integrate Change Management](https://servicenow-prod.fluidtopics.net/7lXN1eqZjygkrSZuazGCHA#configure-properties-integrate-cm "Configure predefined properties through the Pipelines and Deployments Guided Setup to tailor your Change Management and AEMC integration to your company's needs. Configuring these properties is optional."). | | Testing | Configure environment credentials | For more information, see [Configure environment credentials](https://servicenow-prod.fluidtopics.net/_7QF5y2NG0QDWG8cJjHU5A "Configure credentials in your production instance so that the flows used by the App Engine Management Center (AEMC) can access different instances."). | | Testing | Configure the controller instance | Identify the controller instance that contains the pipeline deployment flows, as well as all of the data associated with the pipeline. As each instance completes its assigned tasks, it communicates with the controller instance to determine where the next stage of deployment takes place. Nota: Your production instance should be identified as the controller. For more information, see [Configure your controller instance](https://servicenow-prod.fluidtopics.net/A7numAWl_~DeESZYoPIj3g "You must identify one of the instances in your app development pipeline as the controller instance. All communication between the instances in your pipeline, including the deployment order for applications in the pipeline, takes place in the controller instance."). | | Testing | Enable ATF properties on instances of type Testing. | Enable system properties that allow the ATF suite to run during the deployment process. If you do not enable these properties, a warning displays during the deployment process, but you can continue with the deployment. Nota: If you plan on cloning your production instance to one or more non-production instances, you should either create a data preserver for these settings or enable these settings on your production instance. For more information, see [Create a clone preserver](https://www.servicenow.com/docs/access?context=create-new-clone-preserver&version=australia&pubname=australia-platform-administration&ft:locale=en-US). For more information, see [Enable Automated Test Framework (ATF) properties](https://servicenow-prod.fluidtopics.net/1fRJnrcbWyr_POAFdLmI9Q "Pipelines and Deployments includes an Application Test Framework (ATF) suite called the Application Deployment Test Suite. Two system properties control whether the test runs automatically whenever an app is deployed to a Test environment."). | | Testing | Configure Automated Test Framework (ATF) suite | For more information, see [Exploring Automated Test Framework](https://servicenow-prod.fluidtopics.net/9Ae46m8fimKmphkxb4lNqg "The Automated Test Framework helps you ensure the integrity of your instance by enabling the creation and execution of automated tests following any changes."). | | Testing | Configure Instance Scan suite | For more information, see [Configuring Instance Scan](https://www.servicenow.com/docs/access?context=hs-intro-scans&version=australia&pubname=australia-platform-administration&ft:locale=en-US). | | Non-production instances that aren't of type Testing | Configure environment credentials | For more information, see [Configure environment credentials](https://servicenow-prod.fluidtopics.net/_7QF5y2NG0QDWG8cJjHU5A "Configure credentials in your production instance so that the flows used by the App Engine Management Center (AEMC) can access different instances."). | | Non-production instances that aren't of type Testing | Configure the controller instance in your non-production instances | For more information, see [Configure properties to integrate Change Management](https://servicenow-prod.fluidtopics.net/7lXN1eqZjygkrSZuazGCHA#configure-properties-integrate-cm "Configure predefined properties through the Pipelines and Deployments Guided Setup to tailor your Change Management and AEMC integration to your company's needs. Configuring these properties is optional."). | [Tabela 1. Pipelines and Deployments configuration tasks] {#p-and-d-config-tasks__table_lqq_1qt_rhb}