Creating a Closure Task
Closure tasks mark the end of a request. A Closure task can be used to set the implementation reason and request status for a request.
A request can have multiple Closure tasks depending on the workflow path. They can be automated or manually run by an analyst.
If the request does not have a closure task, the request manager must manually close the request.
You have the same options for closing the request within a closure task as you do when performing the completion within the request itself. Success and failure can still be specified, as can additional information about the nature of the success or failure and descriptive information. Email notifications can also be sent.
If a closure task becomes active and attempts to close a request while it is currently being actioned on by the request manager, the closure task will automatically complete once the request is free. A note will be added to the task history stating that the completion of the closure task has been delayed due to the request being locked.
Creating a Closure Task
On the dependency diagram, double-click the icon to view the Change Window Task Details window.
Complete the common task fields on this task.
Expand the Implementation Details section to set the request closure parameters.
After you have completed the fields, save the task
