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

Scenario guide

Jump to bottom
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 Requester role 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

Clone this wiki locally