PIR Configuration Additional Scenarios
- Enterprise IT
Feature released in SummitAI Service Management (Tahoe SP3 HF01, Change Management)
What's New?
A few more scenarios are added w.r.t Analyst access and Workgroup configuration. (Change > Configuration > PIR Reviewer).
Benefits
- Improved User Experience
Additional Scenarios
Navigate to Change > Configuration > PIR Reviewer. The PIR Reviewer page is displayed. The following are the additional scenarios.
Use Case I- The CR with specific configuration precedes the record with generic configuration. The following example illustrates the same:
Scenario I - Generic Configuration
The following is the sample screenshot of generic configuration for PIR Reviewer with Change Type as ALL, Category as ALL, Workgroup as CMDB Workgroup, Change Category as Hardware and PIR Reviewer as Christian Marnell.
Figure: PIR Details page - Generic Configuration
Scenario II - Specific Configuration
The following is the sample screenshot of specific configuration for PIR Reviewer with Change Type as Normal, Category as Medium, Workgroup as CMDB Workgroup, Change Category as Hardware and PIR Reviewer as Fredrick Norton.
Figure: Figure: PIR Details page - Specific Configuration
In this case, PIR Reviewer (Christian Marnell) with generic configuration (Scenario I) and the PIR Reviewer (Fredrick Norton) with the specific configuration (Scenario II) will get PIR notification.
Use Case II - The configured PIR Reviewer has Analyst access to the same Workgroup as configured in CR configuration. The following example illustrates the same:
Change Record Configuration
The following is a sample screenshot of a CR configuration with Owner Workgroup as IT Infrastructure, Category as Medium, Change Category as Hardware, Change Type as Normal, Assigned Workgroup as CMDB Workgroup and Tenant as Information Technology.
Figure: CR Details page - Configuration
PIR Reviewer Configuration
The following is a sample screenshot of a specific configuration for PIR Reviewer with Change Type as Normal, Category as Medium, Workgroup as CMDB Workgroup, Change Category as Hardware and PIR Reviewer as Fredrick Norton who has got Analyst access to CMDB Workgroup.
Figure: Figure: PIR Details page - Specific Configuration
In this case, the PIR Reviewer (Fredrick Norton) who belongs to the CMDB Workgroup (Assigned Workgroup of CR) will be getting the PIR notification and will be able to perform the PIR review.
Use Case III - The configured PIR Reviewers do not have Analyst access to the same Workgroup as configured in CR configuration. The following example illustrates the same:
Change Record Configuration
The following is a sample screenshot of a CR configuration with Owner Workgroup as IT Infrastructure, Category as Medium, Change Category as Hardware, Change Type as Normal, Assigned Workgroup as CMDB Workgroup and Tenant as Information Technology.
Figure: CR Details page - Configuration
PIR Reviewer Configuration
The following is the sample screenshot of specific configuration for PIR Reviewer with Change Type as Normal, Category as Medium, Workgroup as HR Import, Change Category as Hardware and PIR Reviewer as Ryan and William James. The Workgroups CMDB Workgroup and HR Import belongs to the same Tenant Information Technology.
Figure: Figure: PIR Details page - Specific Configuration
In this case, the PIR Reviewers (Ryan and William James) do not have Analyst access to the CMDB Workgroup (Workgroup configured in CR), but has got Analyst access to the HR Import. Now, as the workgroups CMDB Workgroup and HR Import belongs to the same Tenant Information Technology, the PIR Reviewers (Ryan and William James) will be getting the PIR notification and will be able to perform the PIR review.
Use Case IV - The Workgroup is not defined for PIR Reviewer configuration. The following example illustrates the same:
Change Record Configuration
The following is a sample screenshot of a CR configuration with Owner Workgroup as IT Infrastructure, Category as Medium, Change Category as Hardware, Change Type as Normal, Assigned Workgroup as CMDB Workgroup and Tenant as Information Technology.
Figure: CR Details page - Configuration
PIR Reviewer Configuration
The following is the sample screenshot of specific configuration for PIR Reviewer with Change Type as Normal, Category as Medium, Workgroup as Select, Change Category as Hardware and PIR Reviewer as Ryan and William James who do not have Analyst access to CMDB Workgroup, but has got Analyst access to different Workgroups which belongs to the same Tenant Information Technology.
Figure: Figure: PIR Details page - Specific Configuration
In this case, the PIR Reviewers (Ryan and William James) having Analyst access to any Workgroup of the same Tenant (Information Technology) will be getting the PIR notification and will be able to perform the PIR review.
Use Case V - The PIR Reviewer configuration does not match exactly with CR configuration. The following example illustrates the same:
Change Record Configuration
The following is a sample screenshot of a CR configuration with Owner Workgroup as IT Infrastructure, Category as Large, Change Category as Hardware, Change Type as Normal, Assigned Workgroup as CMDB Workgroup and Tenant as Information Technology.
Figure: CR Details page - Configuration
PIR Reviewer Configuration
The following is the sample screenshot of specific configuration for PIR Reviewer with Change Type as Normal, Category as Medium, Workgroup as HR Import, Change Category as Hardware and PIR Reviewer as Ryan and William James who do not have Analyst access to CMDB Workgroup, but has got Analyst access to HR Import. The Workgroups CMDB Workgroup and HR Import belongs to the same Tenant Information Technology.
Figure: Figure: PIR Details page - Specific Configuration
In this case, the PIR Reviewer configuration does not match exactly with CR configuration as Category parameter is different for both the configurations. Hence, the PIR Reviewers, (Ryan and William James) will not be getting the PIR notification and will not be able to perform the PIR review.
Confluence Cloud Migration Alert: Please refer to known issues you may encounter in Confluence Cloud: https://eitdocs.atlassian.net/wiki/x/wDGwAQ