Page Comparison

Note: All Due Dates are the Build Date. Those stories will be released to production when the respective build is released.

...

Anchor
#PMP-89387 #PMP-89387

PMP-89387 - Changes to public user QR Code link re-direction so that user will navigate to QR Code location

Configurable: No

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

Existing System: 

• When a QR Code is scanned, it takes the user to the default preferred location instead of the location mentioned on QR Code.

...

...

Anchor
#DAP-164 #DAP-164

DAP-164 - Improve the usability of the list screen so that the user can see the complete view name

Configurable: No

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

Existing System: 

• The user wouldn't be able to see the complete view name (>35 Characters) in the list screen view dropdown as they are truncated. 

...

• Improve the usability of the list screen. 

Enhanced System:

• The view dropdown width is increased so that the bigger view names (Upto 60 Characters) are clearly visible without truncation. 
• This change is only applicable to the web platform. 

...

Anchor
#PMP-89335 #PMP-89335

 PMP-89335: Riddor Changes

Configurable: Yes

• Title: Display Incident Riddor Forms 
• Public/Private: Public
• Default: No

...

• Linkage between Incident and Riddor Form for the users to know which records to fill
  •  'Riddor Forms List' screen 
    • The existing column 'Incident ID' has been renamed as ‘Riddor ID’  and a new column ‘Incident ID’ has been added so that it’s easier for the user to link the Incident and Riddor form.
    • 'Incident ID' is the first column and 'Riddor ID' is the second column in the grid.
    • 'Riddor ID' will be shown as a link. 
      • Clicking on the ‘Riddor ID’ link will navigate to the Riddor Form screen incase the Incident already has a Riddor Classification
      • Clicking on the ‘Riddor ID’ link will navigate to the Reporting screen incase the Incident doesn't have a Riddor Classification
      • If the user doesn't have 'Edit RIDDOR Form' permission then the 'Save' button will not be shown on the Riddor Form screen.
    • Incase of an Incident with multiple injuries and different Riddor classifications, multiple rows will be shown in the 'Riddor Form List' with same 'Incident ID' and different 'Riddor ID'.

...

  Impacts: Riddor Reports

Back to top

Anchor
#PMP-89839 #PMP-89839

 PMP-89839: Riddor Implementation for Near Miss Incident Type

Configurable: Yes

• Title: Display Incident Riddor Forms 
• Public/Private: Public
• Default: No

Existing System: 

• Has RIDDOR implementation only for 'Injury/Illness' Incident Type but not for 'Near Miss' Incident Type

Purpose:

• Add the Riddor functionality for 'Near Miss' Incident Type 

Enhanced System:

• Addition of new permissions to handle Riddor Functionality for 'Near Miss' Incident type :
  • If the Custom Setting is turned ON, a new permission section ‘Riddor Form Reporting’ will be shown underneath the ‘Work Place Incident Report – Near Miss’ grid on the ‘Permission’ Setup screen.
  • ‘Riddor Form Reporting’ sub-section will have the following permissions:
    • View RIDDOR Form
    • Edit RIDDOR Form

...

    Impacts: Mobile, Report

Back to top 

Anchor
#PMP-90700 #PMP-90700

 PMP-90700: Custom Setting Key for the Local Record Keeping Question in the Case Management Screen

Configurable: Yes

• Title: Default value selection for Local Record Keeping question
• Public/Private: Public
• Default Value: Yes

Existing System: 

• As per current implementation, the field "Is this Case Recordable According to Local Recordkeeping Requirements?" (shown in the Case Management Screen) doesn't have a Custom Setting Key to handle the default value selection.

          Image Modified

Purpose:

• Introduce a Custom Setting key to handle the default value selection for the field - "Is this Case Recordable According to Local Recordkeeping Requirements?".

Enhanced System:

• A new Custom Setting key has been added to handle the default value selection for the question "Is this Case Recordable According to Local Recordkeeping Requirements?" in the Case Management Screen.

Impacts: Mobile

Back to top

Anchor
#PMP-88162 #PMP-88162

 PMP-88162: Hide Totals based on OSHA 180 Rule for Non-US Locations

Configurable: Yes

• Title: Show/Hide - Totals based on OSHA 180 Day rule for Non-US Locations
• Public/Private: Public
• Default Value: Yes

...

• 'Total based on OSHA 180-Day Rule' is confusing for the Non-US Locations who do not follow OSHA standards.

Enhanced System:

• A configuration has been introduced to show/hide the field 'Totals based on OSHA 180 Day Rule' for Non-US Locations. Based on this configuration, the OSHA 180 day rule calculation will be shown/hidden on the following screens :

...

Anchor
#PMP-89083 #PMP-89083

 PMP-89083: Hide the Report button shown on the Incident Summary screen when it doesn't have any Report links

Configurable: No

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

Existing System: 

• Incase of multiple injuries, the 'Incident Summary' screen shows a 'Report' button.
• Clicking on the 'Report' button shows a list of the following Report links based on the access permissions:
  • Claim Form
  • OSHA 300 Review
  • OSHA 301 Review
  • MSHA Report
  • BOCW
  • Factory Act
• Clicking on the 'Report' button opens a blank section when the user doesn't have permissions for any of the Reports.

Purpose:

• Enhance the current implementation so that it's easier for the user to understand. 

Enhanced System:

• Incase of multiple injuries, if the user doesn't have permissions for any of the Reports then the 'Report' button will be hidden on the Investigation Summary screen.

...

 PMP-90091 - OH -Sample ID for Drug test Encounter type screen

Configurable: No

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

Existing System: 

• Nissan needs the ability to track their “Drug Test” Results data in Occupational Health Module in ProcessMAP system that will eliminate the use of manual efforts needed to incorporate the results from Quest Diagnostics.Sample IDs used for the Drug tests act as unique identifiers that will help Quest to correctly map the samples. The sample ids used currently is generic and needs to be renamed.

Purpose:

• To re-name the sample IDs and create an internal ID for Quest to update. 

Enhanced System:

• The “Sample ID” will be re-named which currently displays as “Sample-1, Sample-2 etc” to “Location-Year-DRG-001-S001, Location-Year-DRG-001-S002“ and so on.

• Another field (non-mandatory) will be added under ‘Drug Testing Details’ as “Internal ID” and a free text box to be provided against it. This will be required by the Quest team to label the samples.

Image Modified

22.3 Performance Management Micro-Release Items

...

Anchor
PMP-92706 PMP-92706

PMP-92706 As an end user of Sustainability Module I want to bulk export KPI data using an API

Configurable: No

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

Existing System: 

• Does not have a way to export all KPI data for a year

...

Anchor
PMP-89783 PMP-89783

PMP-89783 As an end user of Sustainability Module I want to bulk export KPI Emission data using an API

Configurable: No

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

Existing System: 

• Does not have a way to export all KPI Emission data for a year

...

Anchor
PMP-92707 PMP-92707

PMP-92707 As an end user of Sustainability Module I want to bulk export KPI Emission Factors using an API

Configurable: No

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

Existing System: 

• Does not have a way to export configured Emission Factor for a year

...

Anchor
PMP-91159 PMP-91159

PMP-91159 As an Admin I do not want users to be able to delete Activity help attachment from Action Item

Configurable: No

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

Existing System: 

• Activity help document copy was created for every instance of the Activity in Calendar (Action Item)
• This is was resulting in huge duplicate document data causing system wide performance issue

...

Anchor
MP-9416 MP-9416

MP-9416 As an Audit Admin I want to see Conduct Audit confirmation message only when Audit is synced

Configurable: No

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

Existing System: 

• Conduct Audit confirmation message is displayed as soon administrator taps on Save after filling all details in Create Audit screen
• Administrator assumes that Audit creation is complete and force closes the app or logs out
• However the Audit creation does not complete by then

Purpose: 

• Hold the Conduct Audit message until the Audit Save is complete to prevent sync issues

...

Anchor
MP-9417 MP-9417

MP-9417 As an Auditor I want an indication in list screen if Audit is not yet synced

Configurable: No

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

Existing System: 

• If there is an Audit in Mobile device that did not sync to Web and App was closed, when user logs in next time the sync starts but there is no indication for user
• In this case user may start to work with same Audit that did not sync to Web completely and Sync is in progress
• This may result in data conflicts

...

• Provide indication for user if there is a save or sync process happening in the background for a particular audit

Enhanced System:

• Whenever user logs in to the App and navigates to Audit List screen, all Audit record with unsaved/un-synced data will be displayed in Yellow background
• The background will remain until the sync has completed
• If user taps on the Audit card, “Sync in progress” message will be displayed

Impacts: No Impact

Back to top

Anchor
MP-9418 MP-9418

MP-9418 As an Auditor I want an indication in list screen if answers are successfully synced or not

Configurable: No

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

Existing System: 

• On tap of Save in Questionnaire screen, app navigated to Audit List screen and users assume that their responses are saved and force close the app
• However, if there are more questions for the program it takes time for the responses to be saved and if app is force closed before responses are saved then it will not sync to Web
• This is causing gap between Mobile and Web and causing confusion among Users and Admins

...

Anchor
DAP-8029 DAP-8029

DAP-8029 As an end user I want App data sources to be synced before details screen is rendered

Configurable: No

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

Existing System: 

• App Data definition gets synced before the App data sources are synced
• In this case uses are able to access App detail screen (existing or new record)
• However fields are displayed blank because data source sync did not complete

Purpose: 

• Users should be able to see all data source values when they are in the detail screen

• Users need to click on sync icon on the list screen to refresh the data source

Enhanced System:

• App will validate if all data sources are synced before users can navigate to details screen either from App landing screen or App List screen
• If data sources are not Synced, users will see a loader which will stop them from navigating to detail screen
• Users can click on Cancel option to go back to Home screen

...