New and Improved Features

Product Level change

• PMP-50639 As a end user I want to have IMS module view in Home page
• PMP-64154 As an end user I would like to see Driver information auto-populated from Employee Profile
• PMP-63155 As an end user from US location I do not want Start Date of LT/RD to be counted if it is same as Incident Date
• PMP-61460 As a System admin I would like OSHA counts updated when Nature of Injury/Illness Category is updated
• PMP-63224 As an end user should not see records in List screen without view permission
• PMP-63857 As an end user I would like to get Mobile Push notification for Incident created from Web for any Incident Type
• PMP-62536 Monopolistic State forms deprecation

Configurable

• PMP-64056 As an end user I would like to map Incident Action Item to Investigation Root Cause

Other Stability Items

• Not Reproducible CRIs fixed as part of 19.2.1

PMP-50639 As a end user I want to have IMS module view in Home page

Configurable: No

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

Existing System: 

• Does not have a dedicated view that shows quick statistics related to Incidents

Purpose: Create Incident statistics system view 

Enhanced System:

• Has system view for IMS module showing quick statistics.

Impacts: No Impact

Back to top

PMP-64154 As an end user I would like to see Driver information auto-populated from Employee Profile

Configurable: No

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

Existing System: 

• Does not auto populate driver information. There is no linkage between Employee and Driver information

Purpose:

• Reduce manual data entry by making use of Driver information available in Employ Profile

Enhanced System:

• Auto populates driver related information available in Vehicle Incident Summary section based on selected employee profile
• Licence number field value will be always encrypted so no one can view it (same as SSN field)
• IMS Field level permissions for Driver's Licence Number is deprecated
• Length of Service field Year and Week field data will be populated after calculating the same based on date available in Employee Profile

Impacts: Mobile Pro, Feed (To be updated based on need)

Back to top

PMP-63155 As an end user from US location I do not want Start Date of LT/RD to be counted if it is same as Incident Date

Configurable: No

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

Existing System:

• Counts case days including Incident date (if selected as case start date). However OSHA says that Incident Date should not be counted as LT/RD day

Purpose:  To be aligned with OSHA guide lines for US locations.

Enhanced System:

• While it will allow to select Incident date as Case Start Date, it will ignore while counting case days for US locations
• This is done because in other countries Incident date is required to be counted in Case Days
• This business rule is added in Help Text

Impacts: No Impact to existing data

Back to top

PMP-61460 As a System admin I would like OSHA counts updated when Nature of Injury/Illness Category is updated

Configurable: No

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

Existing System: 

• Does not update OSHA 300 log counts for existing Incidents when category is updated for a Nature of Injury/Illness look up value and it is already used in an Incident

Purpose: Avoid mismatch in count

Enhanced System:

• If category is updated for a Nature of Injury/Illness look up value and it is used in an Incident, system will provide below options
  • Update All Incidents
  • Update Current Year Incidents
  • Cancel
• This is applicable for inactive look-up values as well which is associated to an Incident

Impacts: No Impact to existing data

Back to top

PMP-63224 As an end user should not see records in List screen without view permission

Configurable: No

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

Existing System: 

• Displays records in Case Management, Claims and Management Review list screens even if user does not have view permission for that Incident Type
• As the list screen has most of the fields available as column, users can view all those information without view permission for that Incident Type

Purpose: 

• Enhance the data security and align data display with permission

Enhanced System:

• Displays records in respective list screen based on logged user's view permission for the Incident Type
  • Case Management List screen - View Case Permission
  • Claims List screen - View claim, View Cost & Notes and View Adjuster notes permissions
  • Management Review List screen - Edit/View Management Review permission
    • In case of integrated Incident, record will not show if user does not have view permission for all the involved incident.
• Screens like Metrics, Dashboard, Widget etc will display Incident Count irrespective of logged-in user's permission

Impacts: No Impact

Back to top

PMP-63857 As an end user I would like to get Mobile Push notification for Incident created from Web for any Incident Type

Configurable: No

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

Existing System:

• Sends a push notification in Mobile Pro App on Detail Report Created event only for Incidents created from the Mobile App
• Only for Near Miss incidents Push notification is sent irrespective of Mobile or Web

Purpose:

• Extend Push notification feature for Incidents created from Web as well

Enhanced System: 

• Sends push notification in Mobile Pro for all Incidents created from Web
• No change to existing functionality

Impacts: No Impact

Back to top

PMP-62536 Monopolistic State form deprecation

Configurable: No

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

Existing System: 

• Monopolistic State forms reports are built using Crystal Report

Purpose: 

• Due to Web Server upgrade these reports were to be rebuilt to SSRS
• Based on the existing report usage (Heap report) we found that these reports are not being used

Enhanced System:

• Monopolistic State form reports have been deprecated from system
• Print button on these forms will not be available
• Link to these reports will not be available from Summary screen

Impacts: No Impact

Back to top

PMP-64056 As an end user I would like to map Incident Action Item to Investigation Root Cause

Configurable: Yes (in Action Item Configuration)

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

Existing System: 

• Does not provide ability to map Action Items to Investigation Root causes
• Cannot identify which Action Item is created for a certain Root Cause

Purpose: 

• Provide ability to map Action Items to Root Cause

Enhanced System: 

• Has a Auto Complete field in Action Item detail screen where user can select multiple Root Cause that relates to the Action Item
• Display only Root Causes identified for that Incident as selection options
• If Root Cause section is not complete, the field in Action Item details screen will be blank
• If a Root Cause is mapped to an Action Item, it cannot be unchecked from Root Cause Analysis screen
• The field is also available in Manage Action Item list screen in IMS module for selection in view
  • Not included in Default view

Impacts:Report Central, Cognos, Mobile Pro (20.1)

Back to top

List of Not Reproducible CRIs fixed as part of 19.2.1

Back to top