New and Improved Features
Product Level Change
- PMP-88714 : Show the 'Other(List)' values in the Summary Reports
- PMP-88698 : Show the section headers in the Summary Reports based upon permissions
- PMP-83890 : Entire Lessons learned functionality to be driven based on Investigation configurations
- PMP-87570 : Handle security by realigning permissions
Configurable
- PMP-83012 : Allow single root cause selection from the picklist
- PMP-87104 : Capture employees who are part of the Investigation team but not users of the system
Anchor | ||||
---|---|---|---|---|
|
Configurable: No
- Title: NA
Public/Private: NA
Default: NA
...
Impacts: No impact
Anchor | ||||
---|---|---|---|---|
|
Configurable: No
Title: NA
Public/Private: NA
Default: NA
...
Screenshot 2: Section headers (without permissions) were still shown in the Summary Reports
Anchor | ||||
---|---|---|---|---|
|
Configurable: No
- Title: NA
Public/Private: NA
Default: NA
Existing System:
- The 'Lessons Learned Details' link is shown in a disable mode on the 'Investigation Summary' screen even if the user doesn't have the 'View Lessons Learned' permissions. This creates confusion for the end user.
Purpose:
- Drive the entire Lessons Learned functionality on the basis of Investigation configurations
Enhanced System:
- The entire functionality should be driven based on 'Investigation Requirement Configuration' i.e. only if Lessons Learned Statement is configured for an Incident Type then other parts of the functionality (i.e. Lessons Learned Detail link on the Summary screen, Lesson Learned Menu item and Lessons Learned Permission section) should be visible in the system.
Impacts: No impacts
Screenshot 1: Complete 'Lessons Learned Statement' marked as 'Not Applicable'
...
Anchor | ||||
---|---|---|---|---|
|
Configurable: No
- Title: NA
Public/Private: NA
Default: NA
...
- Investigation Responsible team members will be able to view the Incidents even if they do not have 'Others' - 'View Incident' permission for the respective Incident type.
Impacts: Mobile
Screenshot 1: Investigation Responsible team member doesn't have 'View Incident Report' permission
Anchor | ||||
---|---|---|---|---|
|
Configurable: Yes
Title: Single Root Cause Selection
Public/Private: Public
Default: No
...
*Note: Multiple root cause will not be shown in this section.
Anchor | ||||
---|---|---|---|---|
|
Configurable: Yes
- Title: To display the additional team picklist
- Public/Private: Private
- Default: No
Existing System:
- Investigation responsibilities can be assigned using the 'Responsible Team' field (in the Investigation Responsibility screen) which allows to select a list of users of the system. If the investigation team members are not the users of the system then their names cannot be captured.
- There are cases where certain employees also contribute to the investigation, and they are part of Investigation team, but they are not system users.
...
Screenshot 1: 'Additional Team' has been added between 'Responsible Team' and 'Target Completion Date'
Screenshot 2: 'Additional Team' field in the Summary Reports