Overview |
|
Tasks |
|
Included with |
Tivoli Change Management user |
Specifying approvers |
A user or a Change
Control Board (CCB) that reviews a change are approvers. The approvers for a
change are responsible for reviewing a change and assigning a status to the change. Common
status types are Approve, Reject, Freeze, and Hold. There are three ways to add approvers for a change:
When you create a change, if there is a model associated with the category you select, approver information may be filled in automatically for the change. If not, you can add users, CCBs, or yourself. You can add additional approvers to the list associated with models and rules as well. If there is a conflict between the approvers you add and the approvers specified by a model or rule, the model or rule takes precedence and can override your manual entries. Note: You cannot delete approvers who are added as a result of a rule or model unless you have either the TCM Model Rule Value Override or TCM System Administration Rights. |
Notification priorities | When you submit a change, approval notifications
are issued to the approvers who should review and approve the change first. You can
specify who receives notifications first, second, third, and so on by setting a priority
for each approver. The priority defaults to 1 for each new approver. For approvers that you add manually, you can change the default priority. However, if an approver is added by a model or a rule, you cannot delete or change the approver or the priority without special rights. Priority numbers can range from 1 to 99 and do not have to be in sequential order. The approver with the lowest numeric priority receives notification first. When all approvers with first priority approve the change, Tivoli Change Management issues approval notifications to approvers with the next highest priority. For example, if you wanted to make sure that your manager approves the change before your director receives a notification, you could set your manager to priority level 1 and your director to priority level 2 |
Approval methods | When you assign approvers for a change, you can
also specify how they approve a change. For each approver, you have two choices:
You can also modify the approval method for an approver, under the following conditions:
Note: The approval method of activities associated with the change follows the approval method of the parent change. If you change the approval method from Depends On Activity to Approves All Activity, approval requirements for an activity are displayed in the Approvals tab of the Change dialog box with the following:
In addition, if you change the approval method of a root change from Approves All Activity to Depends On Activity, any associated activities that have a disabled approval method of Approves All Activities are now enabled and become part of the approval process. Tip: Activities of an Approves All Activities change are automatically approved when the change is approved. Therefore, to minimize Tivoli Change Management processing time, do not define approval requirements for activities if the change is Approves All Activities. |
Adding a user as an approver |
You can add as many users as necessary to review
and approve a change. To add a user as an approver:
|
Adding a CCB as an approver |
You can add as many CCBs as necessary to review
and approve a change. To add a CCB as an approver:
|
Specifying a notification priority | You can specify a notification priority other
than 1. To specify a notification priority:
|
Specifying the approval method of the change |
You can specify the method of approval for a
change. To specify an approval method:
|
Ensuring notification upon approval |
As a requester, by default you receive
notifications only when a change is rejected, frozen, or held. However, you can receive an
approval notification when all approvers have approved the change. To receive notification when a change is approved:
|