Deployment Request form in the Pipelines and Deployments app
The Deployment Request form is accessed from within the Pipelines and Deployments section of the App Engine Management Center.
To view a Deployment Request form, navigate to All > App Engine > Administration > App Engine Management Center. Then select the Requests page and open a record.
The fields that are included on a Deployment Request form are listed in the following table.
|
Field |
Description |
|---|---|
|
Number |
Number to track the deployment request. |
|
Assignment group |
Group to which the deployment request is assigned. |
|
State |
State of the deployment request. All states are automatically updated by the pipeline flows:- New The submitted request is new.
The submitted request is ready for review.
The submitted request has been deployed to the production instance.
The submitted request is not ready to publish. This state is enabled when you select Reject on the associated approval record at any time during the deployment process. The system then prompts you to include the reason why the application is rejected. These comments are then sent via email to the address included in the Requestor Email field on the Requestor Details related list.
This state is enabled when any of the pipeline flows or sub-flows fail for any reason.
The submitted request has been canceled. |
|
Assigned to |
The user in the assignment group to whom this request is assigned. |
|
Short description |
A brief description for the request. |
|
Release notes |
Text that appears on the ServiceNow Store for this application after it is published. |
|
App Details | |
|
App name |
Name of the submitted application. |
|
App version |
Version of the submitted application. |
|
App Sys ID |
System ID of the submitted application. |
|
App Development URL |
Link to app in App Engine Studio, Creator Studio, or ServiceNow Studio. |
|
Requestor Details | |
|
Requestor First/Last Name |
First and last name of the user who requested to the app deployment. |
|
Requestor User ID |
Identifier of the user who requested to the app deployment. |
|
Requestor Email |
Email address of the user who requested to the app deployment. |
|
Deployment Details | |
|
Originating Environment |
The instance of the originating environment. |
|
Pipeline |
Pipeline being used for deployment. |
|
Current Environment |
The target environment for the app. |
|
Notes | |
|
Additional comments (Customer visible) |
Any additional comments to be shared with the customer, including the app manifest, which lists the number of each type of file in the app, and any ATF or instance scan results are shown. |
|
Work notes |
Internal notes. |
Parent Topic:Managing deployments using Pipelines and Deployments
--- title: Deployment Request form in the Pipelines and Deployments app description: The Deployment Request form is accessed from within the Pipelines and Deployments section of the App Engine Management Center. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/application-development/app-engine-management-center/deployment-req-form-d-and-p.html release: australia product: App Engine Management Center classification: app-engine-management-center topic_type: reference last_updated: "2026-09-10" reading_time_minutes: 2 breadcrumb: [Manage deployments, Use, App Engine Management Center, Run, AI Workflow Factory Prime, Agentic app development, Building applications] --- # Deployment Request form in the Pipelines and Deployments app The Deployment Request form is accessed from within the Pipelines and Deployments section of the App Engine Management Center. To view a Deployment Request form, navigate to **All** > **App Engine** > **Administration** > **App Engine Management Center**. Then select the **Requests** page and open a record. The fields that are included on a Deployment Request form are listed in the following table. <table id="id_um3_4hq_rrb"><thead><tr><th> Field </th><th> Description </th></tr></thead><tbody><tr><td> Number </td><td> Number to track the deployment request. </td></tr><tr><td> Assignment group </td><td> Group to which the deployment request is assigned. </td></tr><tr><td> State </td><td> State of the deployment request. All states are automatically updated by the pipeline flows:- **New** The submitted request is new. - **In Review** The submitted request is ready for review. - **Closed - Published** The submitted request has been deployed to the production instance. - **Closed - Rejected** The submitted request is not ready to publish. This state is enabled when you select **Reject** on the associated approval record at any time during the deployment process. The system then prompts you to include the reason why the application is rejected. These comments are then sent via email to the address included in the **Requestor Email** field on the **Requestor Details** related list. - **Closed - Failed** This state is enabled when any of the pipeline flows or sub-flows fail for any reason. - **Canceled** The submitted request has been canceled. </td></tr><tr><td> Assigned to </td><td> The user in the assignment group to whom this request is assigned. </td></tr><tr><td> Short description </td><td> A brief description for the request. </td></tr><tr><td> Release notes </td><td> Text that appears on the ServiceNow Store for this application after it is published. </td></tr><tr><td class="sub-head" colspan="2"> App Details </td></tr><tr><td> App name </td><td> Name of the submitted application. </td></tr><tr><td> App version </td><td> Version of the submitted application. </td></tr><tr><td> App Sys ID </td><td> System ID of the submitted application. </td></tr><tr><td> App Development URL </td><td> Link to app in App Engine Studio, Creator Studio, or ServiceNow Studio. </td></tr><tr><td class="sub-head" colspan="2"> Requestor Details </td></tr><tr><td> Requestor First/Last Name </td><td> First and last name of the user who requested to the app deployment. </td></tr><tr><td> Requestor User ID </td><td> Identifier of the user who requested to the app deployment. </td></tr><tr><td> Requestor Email </td><td> Email address of the user who requested to the app deployment. </td></tr><tr><td class="sub-head" colspan="2"> Deployment Details </td></tr><tr><td> Originating Environment </td><td> The instance of the originating environment. </td></tr><tr><td> Pipeline </td><td> Pipeline being used for deployment. </td></tr><tr><td> Current Environment </td><td> The target environment for the app. </td></tr><tr><td class="sub-head" colspan="2"> Notes </td></tr><tr><td> Additional comments \(Customer visible\) </td><td> Any additional comments to be shared with the customer, including the app manifest, which lists the number of each type of file in the app, and any ATF or instance scan results are shown. </td></tr><tr><td> Work notes </td><td> Internal notes. </td></tr></tbody> </table>When you have saved the form, additional tabs for approval-related information display. The App Engine admin can use these tabs to approve the request. **Parent Topic:**[Managing deployments using Pipelines and Deployments](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/app-engine-management-center/manage-deployments-using-p-and-d-aemc.md)
| title | Deployment Request form in the Pipelines and Deployments app |
| description | The Deployment Request form is accessed from within the Pipelines and Deployments section of the App Engine Management Center. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/australia/application-development/app-engine-management-center/deployment-req-form-d-and-p.html |
| release | australia |
| product | App Engine Management Center |
| classification | app-engine-management-center |
| topic_type | reference |
| last_updated | 2026-09-10 |
| reading_time_minutes | 2 |
| breadcrumb | Manage deploymentsUseApp Engine Management CenterRunAI Workflow Factory PrimeAgentic app developmentBuilding applications |