Skip to content
This repository has been archived by the owner on Jun 17, 2024. It is now read-only.

Scenario guide

jayrenn edited this page Feb 2, 2017 · 6 revisions

Table of contents

Overview

Enterprise Mode, a compatibility mode that runs on Internet Explorer 11, lets websites render using a modified browser configuration that’s designed to emulate older versions of Internet Explorer, avoiding the common compatibility problems associated with legacy web apps. Any website that is not compatible with Microsoft Edge can be redirected to Internet Explorer using the best browser configuration via the Enterprise Mode Site List. The objective of this portal is to govern the process of site list management.

Features

The Enterprise Mode Site List Portal is a web-based application, which helps enterprises:

  1. Manage site lists from any device supporting Windows 7 or greater;
  2. Submit change requests;
  3. Operate offline via an on-premise solution;
  4. Provide role-based governance;
  5. Test configuration settings before releasing to a live environment;
  6. Have access to the same operations as the client tool, ideal for smaller lists.

Desired user experience

As an app owner, I need to manage my Enterprise Mode Site List from any device running Windows 7 or greater for all of my apps at my own convenience.

Sample workflow:

  • Change request submitted
  • Change verified with the pre-production site list
  • Change approved by group of approvers
  • Production change scheduled
  • Change verified with the production site list
  • Change request signed off and closed

Tool deployment

You can learn how to deploy the tool in your environment here.

Role operations

Requester role

An employee with a role of Requester will be able to perform the following operations:

  • Create a change request
  • Validate change with the pre-production environment
  • Roll back change in case of failure
  • Send request for approval
  • View requests created by himself/herself
  • Sign off and close request

Creating a change request

  1. The employee signs into the portal with a Requester role and navigates to the Create new request page.
  2. After filling at least all the mandatory fields, the employee clicks Save and continue.
  3. A success message with the Request ID will be displayed, and the change request will be made to the pre-production site list.
  4. An e-mail notification is sent with next steps.
  5. The employee will have to set up a test machine to verify the change with the pre-production environment. The detailed steps for verification are sent with the e-mail notification, along with a batch script for configuration.
  6. If the validation passes, the employee will send the change request for approval by selecting Successful and clicking Send for approval.
  7. If the validation fails, the employee can roll back the change in pre-production or ask for help from an administrator.
  8. The employee can navigate to each stage of the ticket using the workflow links provided at the top of the page.

Scheduling a production change

  1. The employee can see who has approved his/her request. A reminder can be sent to those who have not yet approved the change.
  2. Once everyone has approved, the employee can schedule the production change.
  3. The production change can be made immediately, or set for a future date. To make the change immediately, the employee will click Now then Save. To schedule for a future date, the employee will click Schedule and choose the desired date and time, then click Save.
  4. Following the production change, another round of validation will take place for the production environment.
  5. If validation passes, the employee can sign off.
  6. If validation fails, the employee can contact an administrator for help.

Approver role

An employee with a role of App Manager or Group Head will be able to perform the following operations:

  • Approve requests for his/her group
  • Validate change with the pre-production environment
  • Roll back change in case of failure
  • Send request for approval
  • View requests created by himself/herself
  • Sign off and close request

Approving a change request

  1. An e-mail will be sent to the list of approvers.
  2. 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.
  3. The employee can select individual ticket IDs and verify the information provided in the change request.
  4. The employee can approve or reject the ticket.
  5. An e-mail will be sent to the Requester, Approvers, and Administrators with the status of the ticket.
  6. 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.

Administrator role

An employee with a role of Administrator will be able to perform the following operations:

  • Add employees to the portal
  • Assign roles to employees
  • Approve registrations to the portal
  • Configure portal settings (e.g. set freeze schedule, set pre-production and production XML paths, set attachment upload location, etc.)
  • Use the Enterprise Mode Site List Manager standalone page
  • View reports
  • Approve requests
  • Validate change with the pre-production environment
  • Roll back change in case of failure
  • Send request for approval
  • View requests created by himself/herself
  • Sign off and close request

Roll back changes in pre-production

  1. If validation fails in pre-production, the Requester will have sent failure details to the administrators.
  2. The employee can click Roll back to roll back the changes in pre-production.
  3. Once the request has been rolled back, the Requester can re-submit the ticket.

Roll back changes in production

  1. Once a production change has been made, an e-mail will be sent asking for sign-off.
  2. The Requester will navigate to the Production validation page for that ticket.
  3. If the verification fails in production, the Requester will report the failure details. Screenshots or any relevant attachments can be uploaded with the details.
  4. The employee can click Roll back to roll back the changes in production.
  5. The change will be appropriately handled in the production site list.

Grant access to the portal

  1. When a request to gain access to the portal is submitted, an e-mail will be sent to the administrators.
  2. In the Employee management page, select the individual employee and click Edit.
  3. Approve the request by checking Active, then click Save.
  4. An administrator can also add the employee to the portal by clicking Add a new employee .
  5. An administrator can deactivate an account by un-checking Active on the Edit employee page.

Configure the settings

  1. Navigate to the Settings page.
  2. The employee can update the pre-production and production XMLs, as well as the attachments location, by providing the appropriate credentials to access the file paths.
  3. The freeze dates define a window of time in which no changes can be made to the production site list.
  4. A new group can be created by clicking Group details and filling out the fields in the Add group tab. An existing group can be edited by filling out the fields in the Edit group tab on that same screen.
  5. The role names for App Manager and Group Head can be renamed by clicking the edit icon next to their name. You can also toggle whether that role is required for approvals on that same screen by checking/un-checking Mandatory.

Enterprise Mode Site List Manager

This page provides the same functionality you would receive from the Enterprise Mode Site List Manager tool. With it, you can perform the following operations.

  • Add a site to the site list
  • Convert the v.1 schema to the v.2 schema, and vice versa
  • Bulk add sites from an existing XML file
  • Merge multiple XML files and save as one XML file
  • Export the site list
  • Import the site list
  • Bulk add the sites to the portal production list

View the site list

The current production list can be viewed by everyone who has access to the portal. An employee can view this list by navigating to the Production sites list page.

Troubleshooting

  • If an XML already exists, make sure it is syntactically correct.
  • If an update or delete operation failed, check if the entry already exists in the site list.
  • If a user is not able to sign in, the account might not have access. Ask an administrator to check if the account is marked as active.