App Engine Management Center

Enable citizen developers to submit their ideas for applications by activating the Apply for Citizen Development catalog item. This is the first step in configuring the App Engine Studio (AES) Application Intake app.

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.

If you want to add additional conditions to enable ReleaseOps deployments, modify the Deployment Migration to ReleaseOps decision table.

Learn about the App Engine Management Center user interface.

The App Engine Management Center (AEMC) provides an innovative experience for you to manage the full life cycle for custom app development. You can use AEMC to handle application intake, configure pipelines, oversee developer productivity, and view insights about custom applications across your development environments, all in one centralized location.

As you work through the App Engine Studio (AES) Application Intake guided setup, you must perform different configuration tasks.

App Engine Admins can use the App Readiness and Compliance Report dashboard to check if the apps they’re creating are ready to go live.

Assign Developer Sandboxes packs to managed instances from the App Engine Management Center (AEMC).

Cancel a scheduled app deployment in App Engine Management Center (AEMC) if you no longer need to deploy the app to production. Canceling the scheduled deployment request cancels the scheduled deployment and also the entire request itself.

Complete ReleaseOps guided setup in AEMC to configure your ReleaseOps ecosystem to handle your deployments.

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.

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.

Use the Pipelines and Deployments guided setup to complete the initial configuration of Pipelines and Deployments. Detailed instructions for each step are provided in subsequent sections of the product documentation.

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.

Configure your app development pipeline so that your administrator can quickly move an application from one environment to another.

Use the App Engine Management Center (AEMC) guided setup to step through the initial configuration of the Application Intake and Pipelines and Deployments applications. The Application Intake guided setup is optional, but if you want to use AEMC, the Pipelines and Deployments guided setup is required.

Use OAuth credentials in your pipelines to add another level of security to your pipeline. This task helps you create and configure OAuth credentials for use in your pipelines.

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.

Complete ReleaseOps guided setup in AEMC to start using ReleaseOps for your deployments.

With App Engine Management Center (AEMC), you no longer need an active deployment pipeline to get started. Complete the standalone environment setup to start deploying changes quickly. You can add a pipeline later when you're ready to automate deployments.

Update the sn_deploy_pipeline.migrate_releaseops system property to enable deployments using ReleaseOps.

Learn about the configuration process for AEMC.

Create OAuth API endpoints to enable your controller instance to have two-way communication with your non-production instances. Follow and complete each step carefully on the specified instances before moving on to create your third-party OAuth provider records.

Configure credentials in your production instance so that the flows used by the App Engine Management Center (AEMC) can access different instances.

Create third-party OAuth provider records to enable each of your instances to access the API endpoints you've created.

Create a custom app intake experience for your organization by editing the fields and questions on the App Engine Studio (AES) App Intake form in Catalog Builder.

Learn about the deployment process in AEMC.

The Deployment Request form is accessed from within the Pipelines and Deployments section of the App Engine Management Center.

AEMC enables you to deploy changes to production through deployment requests. Learn more about what deployment requests are and where to view them in AEMC. Starting with version 28.2.1 of AEMC, you can also manage ReleaseOps deployment requests from AEMC.

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.

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.

Enable the ReleaseOps system property to have AEMC fetch data from the environments configured in ReleaseOps.

Learn about how the App Engine Management Center (AEMC) can help to centralize and streamline your application development and governance at scale.

The App Engine Management Center (AEMC) application provides tools for locating requests. You can perform a global search for request records or filter the list of current requests to locate the ones you want to work on.

To get help with App Engine Management Center, your ServiceNow instance, plugins, permissions, and more, watch a short video to contact the ServiceNow admin who works in your company.

You can track and approve or reject app intake and collaboration using the App Engine Management Center (AEMC).

Control which user groups are available for admins to give Creator Studio and App Engine Studio app development permissions to during the Application Intake process. These groups are managed on the User Groups Permission Types [sn_app_intake_permission_type] table.

View and manage new app requests in App Engine Management Center (AEMC) that users with the Creator Studio Restricted role (sn_creator_studio_restricted_user) submit for apps they want to create.

As an admin, view and approve or reject collaboration requests in the App Engine Management Center (AEMC) from developers who want assistance building their applications.

Review custom app metrics and manage apps through the development life cycle using the App Engine Management Center (AEMC).

Review and approve or reject deployment requests in the App Engine Management Center (AEMC) as applications move from development to production.

Manage deployments using Pipelines and Deployments in the App Engine Management Center (AEMC).

View details about developers working on apps in App Engine Studio and Creator Studio using App Engine Management Center (AEMC).

View details of intake requests submitted by developers in App Engine Studio in the App Engine Management Center (AEMC) dashboard, and approve or reject them.

Track and manage requests for new applications, collaboration requests, and insights into developer contributions and custom app production across your organization. You can also assign Developer Sandboxes licenses to managed instances.

If your ReleaseOps deployment request has custom states, you must configure the Deployment Request State Map table so that your ReleaseOps deployment request states map to the correct App Engine states.

Starting with version 28.2.1 of AEMC, you can migrate your existing App Engine pipelines to ReleaseOps. Learn more about the migration process and benefits of migrating to ReleaseOps.

You must complete several tasks to migrate your App Engine pipelines to ReleaseOps.

As you work through the Pipelines and Deployments guided setup, you must perform different configuration tasks on each of your instances.

As you manage requests for app deployment in App Engine Management Center (AEMC), use this workflow to understand how app deployments move through your pipelines in version 24.1.2, released in November 2023.

After completing ReleaseOps guided setup in AEMC, run trust profile setup to complete the configuration process.

Schedule apps to deploy to production at a future time to load balance your systems using the App Engine Management Center (AEMC).

Test App Engine Management Center (AEMC) on a non-production instance to confirm that everything is working as expected before moving to production.

Testing an application helps to ensure the viability of the changes on the production instance. Learn about how testing works in AEMC and the different kinds of tests that automatically run during the deployment process.

Change the details of a deployment request in App Engine Management Center (AEMC).

Create credential records on each of your instances to enable OAuth use in your pipeline.

AEMC enables you to manage app development and deployments, all in one centralized location. Learn about how you can use AEMC to govern your organization's app development.