Page History

Assign and update change requests

To assign a change request, please perform the following steps:

1. Navigate to Change Enablement → All Change Requests and open a the change request you need want to assign.
2. Click a On the Notes tab, click the magnifier icon in next to the Assigned User or the Assignment Group field.
3. Select the responsible a person or a group to assign the change request to.
4. Click Save or Save and Exit to apply the changes.

To update a change request, please complete the steps below:

1. Navigate to Change Enablement → All Change Requests and open a the change request you need want to update.
2. Update the necessary fields.
3. Click Save or Save and Exit to apply the changes.

All activities will be shown in the Note tab of the change request. 

Schedule and plan change requests

Change request implementing requests must be planned and scheduled carefully. Planning and scheduling change requests allow for minimizing disruption to vital business function disruptionfunctions.

When scheduling the a change request implementation, remember about time overlaps; minimize the effect caused to the multiple services or CI's at implementation time. 

To schedule a change request, please complete the following steps:

1. Navigate to Change Enablement → All Change Requests and open the change request you need.
2. Open On the Schedule tab, and enter the date and time when the request has to be started and finished processing into the appropriate fields.
3. After the request was processed, enter the actual date and time.

Schedule tab fields

To plan a change request, complete the following steps:

1. Navigate to Change Enablement → All Change Requests and open the change request you need.
2. On the Planning tab, fill in the fields as required.

following fields in the Planning tab :fields

Change request authorization

The change requests that are not Change requests of non-standard type must go through authorization procedure (the . For standard change request, the state changes to the Scheduled automatically automatically, without authorization stage).

The authorization is a request approval by Change Authorities change authorities of different levels, depending on the risk level and probability levellevels. The higher the risk and probability levels are, the stricter the authorization procedure is.

In SimpleOne, once a change request requiring authorization is registered, it goes to the authorization stage. The state of the request changes to the Authorization. For this, approval tickets should be sent to all necessary authorities, depending on the Change Authority the change authority level. In such a ticket, every recipient is proposed prompted to approve or reject a request.

If all approval tickets have been approved, the change request is considered to be successfully approved. The state of the request changed changes to the Scheduled.

If there is even one a single approval ticket rejected, then:

• all other approval tickets must have been are rejected automatically too.
• the change request is considered to be rejected and goes back to the authorization stage.
• the state of the request is changed back to Registered.

For the emergency changes, due to their high importance for business services or CI's, the relationship between the Registered and Authorization states is of one-way type. It means that emergency tickets cannot be rejected. Refer to the Change Enablement State Modelenablement state models article to learn more.

Change Authority level

The following table shows the dependency between the change request risk level and the authority level.

Customize a CAB

A default CAB structure is described above, but you may need to modify it according to the organizational structure or business needs. You can do it in several ways:

• Modifying an include script containing parameters responsible for CAB gathering. These modifications will affect all change requests created later.
• Adding new participants to a specified change request CAB while processing it.

Modifying Modify a CAB script

To bring in some global modifications into a default CAB, please complete the steps below:

1. Navigate to System Definition → Script Includes.
2. Click the magnifier icon at the top of the list; the search string appears.
3. Enter calculateCAB to into the Name field and press Enter; the relevant script should be found.
4. Click on the script title to open it.
5. All role sets for different CABs are defined in this script with a corresponding comment, like thisas follows:

  // Complex CAB
    const roles = [
      'change_manager',
      'problem_manager',
      'incident_manager'
    ];

Add or delete a role into an appropriate section to modify any CAB, basic or complex.

For example, you want request managers to participate in the Complex a complex CAB, and, at the same time, you want to relieve problem managers from these duties. Then you need to delete the problem_manager role from the script and add the request_manager role.

Modifying Modify a specified CAB

You can also modify a CAB for any specified change request with no effect to further requests. For example, you want a particular change request to be approved by some specified employees. For this, please complete the steps below:

1. Navigate to a the change request you need to be extendedextend.
2. Make sure that State IS Registered and Change Type IS NOT Standard.
3. Navigate Select to the Schedule tab of the Related lists area.
4. Click the Customize CAB button and select the necessary persons users from the list (you can select as many users as you need).
5. Click Add.

Change templates

You can create a template that can be used later to create change requests with pre-defined predefined tasks. In addition, templates make the processes easier by populating the fields automatically.

You can create a template of any complexity , pre-filling and prefill any fields, including assignments. A template can be nested, so you can include change tasks into it if necessary.

Templates can be created in two ways:

• from scratch
• from the change request processed earlier.

Templates can be created for Standard standard or Normalnormal changes. The difference between the two options is that a standard change template is already authorized. So any standard change request created out of the change template does not go through the authorization stage. And both the normal change template and its change request will be created with the Authorization state.

To create a change template from scratch, please complete the steps below:

1. Navigate to Change Enablement → Change Request Templates.
2. Click New and fill in the fields.
3. Click Save or Save and Exit to apply the changes.

Change template form fields

Change template state model

The following picture describes the state flow of change templates:

In the The following table , you can see state descriptions lists and describes states and available transitions.

Creating a template out of a change request

To create a template out of a change request, please complete the following steps:

1. Navigate to Change Enablement → All Change Requests and open the change request you need.
2. In the hamburger menu , select the Create Template item.
3. Edit the change request template form. 
4. Click Save or Save and Exit.

As a result, created template appears in the Change Request Template table and inherits all attributes from the parent record. That means, for example, if the request had some change tasks, the newly created template would have relevant related change tasks templates. The template will have a reference to the change request on the base of which it was created in the Created From Change Request field.

Closure information

Based on the SimpleOne state model, the change request has to be closed, when it has been fully processed. The responsible person can provide the closure code, when closing the change request.

Closure code

This code specifies an option of the closure. SimpleOne has the following options: