Change Request Lifecycle

Overview

A change request lifecycle contains the following activities. These activities are done by different people at different times.

Create Workflow SecureChange Requester

In configured SecureChange deployments, Workflow Owners are responsible for creating and maintaining workflows. Workflows may be created for specific user groups, for example you may have a workflow to grant or remove access or a workflow to decommission a rule.

Workflows are created and maintained by Workflow Owners in the Workflows page, see Workflows Page.

Create Change Request SecureChange Requester

After administrators have created workflows, Requesters can submit requests based on a workflow. The types of requests available to a user is based on their role in the organization.

When a user submits a request, the request becomes a ticket in the SecureChange system. SecureChange moves the request on to the next person or group responsible for handling the request, according to the workflow configured for that request type. A task may be automatically or manually assigned to a handler. The assigned request handler receives an email notification, and the request appears in his personal tasks in SecureChange.

SecureChange continues to manage the request's lifecycle stages, until the request is closed in accordance with the workflow.

For further information, see Creating a Change Request.

Handling Tasks SecureChange Requester

Once the Change Request has been created, it is assigned to a Handler who reviews and implements the required changes, see Processing a Ticket.