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-88714: Show the 'Other(List)' values in the Summary Reports

Configurable: No

• Title: NA
• Public/Private: NA
• Default: NA

Existing System: 

• If 'Other(List)' is selected as an option for 'Contributing Factors' / 'Nature of Injury/Illness' / 'Cause of Injury/Illness' / 'Cause of Incident', the actual value provided for the 'Other(List)' is not shown in the 'Incident Summary' and 'Email Incident Summary' reports.

Purpose: 

• Allow users to see the complete set of details in the 'Incident Summary' and 'Email Incident Summary' reports.

Enhanced System:

• Shows the actual value for 'Other(List)' option in the Summary Reports in the format : Other(List) - <value provided>.
• This change has been implemented in the following sections:

       a. Contributing factors

       b. Environment Incident Details

c. Property Damage Incident Details

  Impacts: No impact

Back to top

PMP-88698: Show the section headers in the Summary Reports based upon permissions

Configurable: No

• Title: NA

• Public/Private: NA

• Default: NA

Existing System: 

• Shows the section headers in the 'Incident Summary' and 'Email Incident Summary' reports even if the user doesn’t have permission for those sections.

Purpose: 

• Align the section headers shown in the Summary Reports as per the UI.

Enhanced System:

• Show the Section headers in the ‘Incident Summary Report’ and ‘Email Incident Summary Report’ based on the permissions. If the user doesn’t have permission for any of the sections, then the respective header should not be shown in the Summary Reports.

Impacts: No impact

Screenshot 1: User doesn't have permissions for some sections

Screenshot 2: Section headers (without permissions) were still shown in the Summary Reports

Back to top

PMP-83890: Entire Lessons Learned functionality to be driven based on Investigation configurations

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'

Screenshot 2: 'Lessons Learned' permission section will not be shown if the 'Lessons Learned Statement' configuration is marked as 'Not Applicable'

Screenshot 3: 'Lessons Learned Details' link and 'Lessons Learned' sub-menu will not be shown

Back to top

PMP-87570: Handle security by realigning permissions

Configurable: No

• Title: NA
• Public/Private: NA
• Default: NA

Existing System: 

• Users assigned as a member of the Investigation Responsible Team are not able to view the Incident on the List screen if they do not have 'Others' - 'View Incident' permission for the respective Incident Type.

Purpose: 

• Allow the Investigation Responsible team members to view the incidents on the List screen even if they do not have 'Others' - 'View Incident' permission for the respective Incident Type.

Enhanced System:

• 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

Back to top

PMP-83012: Allow single root cause selection from the picklist

Configurable: Yes

• Title: Single Root Cause Selection

• Public/Private: Public

• Default: No

Existing System: 

• Allows users to select multiple root cause in the picklist.

Purpose: 

• Enhance the current system to provide flexibility in the Root cause picklist popup to make it single select or multi select as per need. 

Enhanced System:

• Allow the users to select single/multiple root cause based on the configuration.
• This configuration has been defined in the Setup > Module Setup > Incident Management > Field Level Configuration > Root Cause Analysis > Single Root Cause selection.
• The default value for the key 'Single Root Cause Selection' is 'No'.
• This configuration is applicable to all the Incident types.
• If the 'Single Root Cause Selection' is turned ON then the users will be allowed to select only one root cause from the picklist. Moreover, the single root cause will be shown under the 'Investigate' section on the 'Incident Detail Summary' screen. 

Impacts: No Impact

Screenshot 1: Single Root Cause selection configuration is turned on

Screenshot 2: Every ‘Contributing Factor’ will have a corresponding ‘Root Cause’ row with an Add button (“+”) underneath the ‘Root Cause’ column

Screenshot 3: User will be allowed to select only one root cause at a time as the 'Single Root Cause Selection' configuration is turned on

Screenshot 4 :Selected Root cause is shown underneath the 'Root Cause' column

Screenshot 5: Validation message will be shown when user tries to add another root cause

Screenshot 6: Single Root cause shown in the 'Investigate' section (Incident Detail Summary screen) when the configuration is turned on

 *Note: Multiple root cause will not be shown in this section.

Back to top