Adding content

This commit is contained in:
LizRoss 2017-05-09 08:54:33 -07:00
parent 288e85095d
commit 1286b825ff
3 changed files with 54 additions and 8 deletions

View File

@ -0,0 +1,46 @@
---
localizationpriority: low
ms.mktglfcycl: deploy
ms.pagetype: appcompat
description: Details about how Approvers can approve open change requests in the Enterprise Mode Site List Portal.
author: eross-msft
ms.prod: ie11
title: Approve a change request using the Enterprise Mode Site List Portal (Internet Explorer 11 for IT Pros)
ms.sitesec: library
---
# Approve a change request using the Enterprise Mode Site List Portal
**Applies to:**
- Windows 10
- Windows 8.1
- Windows 7
- Windows Server 2012 R2
- Windows Server 2008 R2 with Service Pack 1 (SP1)
After a change request is successfully submitted to the pre-defined Approver(s), employees granted the role of **App Manager** or **Group Head**, they must approve the changes.
## Approve a change request
The Approvers get an email stating that a Requester successfully opened, tested, and submitted the change request to the Approvers group. The Approvers can accept or reject a change request.
**To approve a change request**
1. The Approver(s) log onto the Enterprise Mode Site List Portal, **My Approvals** page.
## Next steps
After the Approvers approve the change request, it must be scheduled for inclusion in the production Enterprise Mode Site List. For the scheduling steps, see the [Schedule a production environment change using the Enterprise Mode Site List Portal](schedule-production-change-enterprise-mode-portal.md) topic.
Approving a change request
An e-mail will be sent to the list of approvers.
After signing in, the employee will land on the My approvals page, or can navigate to the page by clicking Approvals pending in the sidebar.
The employee can select individual ticket IDs and verify the information provided in the change request.
The employee can approve or reject the ticket.
An e-mail will be sent to the Requester, Approvers, and Administrators with the status of the ticket.
The employee can also view the status of other tickets in his/her group by clicking the In progress, Closed, and Rolled back links in the sidebar.

View File

@ -27,7 +27,7 @@ Employees assigned to the Requester role all have the ability to create a change
**To create a new change request**
1. The Requester (an employee that has been assigned the Requester role) signs into the Enterprise Mode Site List Portal, and clicks **Create new request**.
The **Create new request** screen appears.
The **Create new request** page appears.
2. Fill out all of the required fields, based on the group and the app, including:

View File

@ -22,7 +22,7 @@ ms.sitesec: library
>[!Important]
>This step requires that each Requester have access to a test machine with Administrator rights, letting him or her get to the pre-production environment to make sure that the requested change is correct.
After the Requester successfully submits a change request to the Enterprise Mode Site List Portal, he or she gets an email, including:
The Requester successfully submits a change request to the Enterprise Mode Site List Portal and then gets an email, including:
- **EMIE_RegKey**. A batch file that when run, sets the registry key to point to the local pre-production Enterprise Mode Site List.
@ -31,15 +31,15 @@ After the Requester successfully submits a change request to the Enterprise Mode
- **EMIE_Reset**. A batch file that when run, reverts the changes made to the pre-production registry.
## Certify your results in the pre-production environment
After the Requester tests the changes, he or she must go back into the Enterprise Mode Site List Portal, **Pre-production verification** screen to certify whether the testing was successful.
The Requester tests the changes and then goes back into the Enterprise Mode Site List Portal, **Pre-production verification** page to certify whether the testing was successful.
**To certify changes and send to approvers**
1. On the **Pre-production verification** screen, the Requester clicks **Successful** and optionally includes any attachments (only .jpeg, .png, .jpg and .txt files are allowed) to support the change request and testing results.
**To certify changes and send to the Approver(s)**
1. On the **Pre-production verification** page, the Requester clicks **Successful** and optionally includes any attachments (only .jpeg, .png, .jpg and .txt files are allowed) to support the change request and testing results.
2. The Requester reviews the pre-defined approvers, and then clicks **Send for approval**.
2. The Requester reviews the pre-defined Approver(s), and then clicks **Send for approval**.
**To rollback your pre-production changes**
1. On the **Pre-production verification** screen, the Requester clicks **Failed** and optionally includes any attachments (only .jpeg, .png, .jpg and .txt files are allowed) to support the change request and testing results.
1. On the **Pre-production verification** page, the Requester clicks **Failed** and optionally includes any attachments (only .jpeg, .png, .jpg and .txt files are allowed) to support the change request and testing results.
2. Add a description about the issue into the **Issue description** box, and then click **Send failure details**.
@ -47,7 +47,7 @@ After the Requester tests the changes, he or she must go back into the Enterpris
3. The Requester clicks **Roll back** to roll back the changes in the pre-production environment.
After the Requester rolls back the changes, he or she can update the requst and re-submit the ticket.
After the Requester rolls back the changes, the request can be updated and re-submitted.
## Next steps
If the change request is certified as successful, the Requester must next send it to the Approvers for approval. For the Approver-related steps, see the [Approve a change request using the Enterprise Mode Site List Portal](approve-change-request-enterprise-mode-portal.md) topic.