Workplan Mapping
What is Workplan Mapping?
Mapping the Task Templates from the Workplan to auto-create CR and sequencing the execution of Task Templates by specifying an Execution Order is called Workplan Mapping.
Workplan Mapping
Workplan Mapping allows admin to seamlessly align the execution of Tasks which is linked to the CR automatically. All the Tasks or few Tasks from the Workplan can be mapped to the CR.
To configure Workplan Mapping, perform the following steps:
Navigate to Change > Configuration > Workplan Mapping.
Figure: Workplan Mapping NavigationNote:
Workplan Mapping can be navigated from Workplan. To achieve this perform the following:
Click Workplan Mapping from ACTIONS panel.
Figure: Workplan Mapping Navigation from Workplan- Select Tenant.
Workplan Mapping List is displayed.
Figure: Workplan Mapping List Click ADD NEW.
Workplan Mapping page is displayed requesting for the admin to enter the required details.
Figure: Workplan MappingField Description Tenant Specifies the Tenant Name. Name Mentions the Name of the Workplan. CR creation Specifies CR is auto created from SR.
Note:
Maps the Tasks to CR and the CR is created automatically for a SR based on the Catalog to Change Mapping Configuration.
Service Catalog Specifies name of the Catalog. Workplan Specifies name of the Workplan. Active Indicates if the Workplan Mapping configuration is Active on the list. 1. Conditions
Specifies the systematic approach on which the Tasks are linked to the CR as following:
- Based on Conditions: The system will allow us to define a set of conditions based on Service Catalog selection. The mapping of a Workplan to a CR will take place only if the defined condition matches for the Task. The condition is set using the Field, Operator, Value approach. The added conditions can also be grouped logically to form a single condition for a Task.
No Condition: The Tasks can be mapped to the CR irrespective of the SR attributes from the Service Catalog.
Figure: Workplan Mapping with No ConditionNote:
Tasks will be triggered for the CR based on the conditions subject to Service Catalog and Service Request fields. Tasks will be triggered for CR without conditions as well.
2. Actions
Specifies the the Task Name, the Type of its execution and if multiple Tasks exist the order in which it should execute.
Field Description Task Name Mentions the Name of the Task Task Type Specifies the Type of Task.
Note:
The Task execution will be in following order:
1. Implementation
2. Rollback
3. Post ImplementationExecution Order Specifies the order of Execution.
Note:
Execution Order for the Task Type will be from the lowest to the highest.
The following table describes the icons on the task mapping process.Icon Action Description Add - Add new condition for Task (Based on Condition).
- Add new Task (No Condition).
Delete - Delete condition for Task (Based on Condition).
- Delete Task (No Condition).
Note:
In the above example, Task (OS Installation) is executed only if the Field value matches to Software_Details_Publisher AND Priority.
- Based on Conditions: The system will allow us to define a set of conditions based on Service Catalog selection. The mapping of a Workplan to a CR will take place only if the defined condition matches for the Task. The condition is set using the Field, Operator, Value approach. The added conditions can also be grouped logically to form a single condition for a Task.
Click ADD.
Condition and Action is mapped.
Figure: Task Action- Click SUBMIT.
Task, CR, and Incident Relationship
Upon the creation of Workplan with a set of Tasks. A workplan is mapped to a CR and if the Workplan gets triggered then the tasks associated with it will be part of the CR. Now, these tasks templates will get converted to Tasks for the CR. The newly created Tasks for CR will be part of Task List.
To view the Task List, perform the following:
- Navigate to Change > Users > Task List.
List of Tasks are displayed.
Figure: Task List
To view the Tasks on the CR, perform the following steps:
Navigate to Change > User > Change Record List.
Change Record List is displayed.
Figure: Change Record ListNote:
The CRs created from SR to CR process can be viewed on Change Record List and marked with an amber color line below the CR ID for identification.
- Click CR NO.
Change Record is displayed. Click RELATIONSHIP.
Tasks will be linked to the CR.
Figure: CR Relationship with TasksNote:
All the tasks added through a workplan will be displayed based on color code. The heading of the Task is where the Task ID is displayed with different colors based on the Task Type.
The colors associated with each Task Type is defined as following:
Implementation: Light Aqua Blue.
Post Implementation: Light Green.
Rollback: Light Orange.
To view the Tasks on the Incident, perform the following steps:
- Navigate to Incident > Manage Incidents > Incidents List.
Incident List is displayed. - Click Incident ID.
Incident page is displayed. Click RELATIONSHIP tab.
Task linked to the Incident can be viewed.
Figure: Incident and Task RelationshipBased on the Task status set for the Incident, an Incident is logged.
Note:
- The Task will be in Draft status before the CR approvals are completed and can be edited.
- The Analyst will not be able to edit the tasks linked to the CR once the CR completes all the approvals.
- The option to Link, Delink or Create a Task on the Relationship tab of Change Record will be disabled via SR to CR Process.
Confluence Cloud Migration Alert: Please refer to known issues you may encounter in Confluence Cloud: https://eitdocs.atlassian.net/wiki/x/wDGwAQ