Versions Compared
compared with
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Comment:
Merged branch "DOC0000957" into parent
The change request process allows the caller to be informed about the work progress.
In SimpleOne, this process is implemented as Notifications sent by email. Notifications delivered "out-of-the-box" are described below:
| Notification | Description | Target Audience | ||
|---|---|---|---|---|
| Change request is created | This notification is sent after the change request is just created and registered. | Change Manager | ||
| Change request is completedin progress | This notification is sent after the change request state changes to Completed.to the assigned users stating that the work on the change tasks to be started. | Assigned UserChange Manager, Stakeholders* | ||
| Change request is assigned | This notification is sent after the change request is assigned to a responsible group or person. | Follower, Assigned User, Assignment Group | ||
| Change request is scheduled | This notification is sent after the change request state changes to Scheduled. | Follower, Assigned User, Stakeholders* | ||
| Change request requires authorization | This notification is sent after the change request state changes to Authorization. | Follower, Assigned User | ||
| Change request requires your authorization rejected | This notification is sent after the change request authorization failed (request state changes to Registered). | Follower, Assigned User | state changes to Authorization. | Approvers |
| Change request has been authorizedNew comment is added | This notification is sent after the change request has additional commentschange request has been successfully authorized (state changes to Scheduled). | Follower, Assigned User | ||
| Change request requires authorization rejected | This notification is sent after the change request state changes to Authorization. | Approvers | authorization failed (request state changes to Registered). | Follower, Assigned User, Approvers |
| New comment is addedChange request has been authorized | This notification is sent after the change request has been successfully authorized (state changes to Scheduled).change request has additional comments. | Follower, Assigned UserApprovers | ||
| Change request is in progresscompleted | This notification is sent to the assigned users stating that the work on the change tasks to be started.after the change request state changes to Completed. | Change ManagerAssigned User, Stakeholders* | ||
| Change is implemented | This notification is sent when the change request is completed with a closure code Implemented. | Change Manager, Stakeholders* | ||
| Change is partially implemented | This notification is sent when the change request is completed with a closure code Partially Implemented. | Change Manager, Stakeholders* | ||
| Change failed to be implemented | This notification is sent when the change request is completed with a closure code Not Implemented (Rollback). | Change Manager, Stakeholders* | ||
| Change is cancelledcanceled | This notification is sent when the change request is completed with a closure code Not Implemented (CancelledCanceled) because the change authority (CAB) authorization failed or was cancelledcanceled. | Change Manager, Stakeholders* | ||
| Change request post-implementation review | This notification is sent when the change request status changes to Post-Implementation review. | Stakeholders* | ||
| Change Tasks | ||||
| Change task is cancelledcanceled | This notification is sent when a change task has been cancelledcanceled. | Assigned User | ||
| All change tasks are completed | This notification is sent upon completion of all related change tasks. | Change Manager, Assigned User | ||
| Change task is ready | This notification is sent when a change task has been created or edited. | Assigned User | ||
| Change task plan is ready | This notification is sent after the associated change task is saved with the Plan Ready checkbox selected. | Assigned User | ||
*Stakeholders – here: the people who may need or want to track the work on the change request. They are not responsible for any part of the change request workflow. Read the article to see how to add them to the recipients list.
| Tip |
|---|
To learn how to create new notification rules or modify existing ones, read the NotificationsNotification Handling article. To learn how to add more recipients, read the Additional Notification Recipients article. |