Note: All Due Dates are the Build Date. Those stories will be released to production when the respective build is released.
22.3 Micro-Release items list
Jira Legacy
22.3 Micro-Release items list
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Table of Contents maxLevel 2 minLevel 2
22.3 Foundation Micro-Release Items
New and Improved Features
Product Level Change
- PMP-89387 - Changes to public user QR Code link re-direction so that user will navigate to QR Code location
Configurable
- PMP-91146 - Zendesk navigation without SSO authentication
...
|
Anchor Top Top
22.3 Micro-Release items by Module
| Top | |
| Top |
Table of Contents maxLevel 2 minLevel 2
22.3 Foundation Micro-Release Items
New and Improved Features
Product Level Change
- PMP-89387 - Changes to public user QR Code link re-direction so that user will navigate to QR Code location
Configurable
- PMP-91146 - Zendesk navigation without SSO authentication
| Anchor | ||||
|---|---|---|---|---|
|
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.
Purpose:
- Improve the usability where a user by default lands to a particular location without having to change the location manually.
Enhanced System:
- User would be able to land to a specific location that is mentioned on the QR Code.
- In case if user doesn't have scope to QR Code location, then the system auto-directs him to his preferred location.
Best Practices:
- Post entering data, the user needs to close the browser session. If the session is active, then the next time the user is scanning a QR Code, the system will land on the previously active location and not the location mentioned in the QR code.
- Always use light weighted forms where data is entered by the Public user as they always open up in a mobile browser. Controls like 'Action item' will have usability issues on mobile browsers as they are not responsive.
Impacts: No Impact
| Anchor | ||||
|---|---|---|---|---|
|
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.
Purpose:
- Improve the usability where a user by default lands to a particular location without having to change the location manually.
Enhanced System:
- User would be able to land to a specific location that is mentioned on the QR Code.
- In case if user doesn't have scope to QR Code location, then the system auto-directs him to his preferred location.
Best Practices:
- Post entering data, the user needs to close the browser session. If the session is active, then the next time the user is scanning a QR Code, the system will land on the previously active location and not the location mentioned in the QR code.
- Always use light weighted forms where data is entered by the Public user as they always open up in a mobile browser. Controls like 'Action item' will have usability issues on mobile browsers as they are not responsive.
Impacts: No Impact
...
Configurable: No
- Title: NA
- Public/Private: NA
- Default: NA
Existing System:
- Access Report Ticket / View Status using Application Authentication
Purpose:
- Zendesk account migration and access with non-sso authentication
Enhanced System:
- Open Zendesk URL and access through non-sso login
Impacts: No Impact
22.3 App Builder Micro-Release Items
New and Improved Features
Product Level Change
DAP-164 - Improve the usability of the list screen so that user can see the complete view name
Configurable
...
:
- Access Report Ticket / View Status using Application Authentication
Purpose:
- Zendesk account migration and access with non-sso authentication
Enhanced System:
- Open Zendesk URL and access through non-sso login
Impacts: No Impact
22.3 App Builder Micro-Release Items
New and Improved Features
Product Level Change
DAP-8029 - Ability to sync data sources before rendering the details screen on mobile
DAP-164 - Improve the usability of the list screen so that user can see the complete view name
Configurable
- None
| Anchor | ||||
|---|---|---|---|---|
|
Configurable: No
- Title: NA
- Public/Private: NA
- Default: NA
Existing System:
- The moment user lands on the home page, system would download App definitions, App data and Data sources.
- There was no sync symbol available which would indicate that the above download was completed.
- As the sync was happening in the background, users were able to click on an app and access List/ Summary and Detail screen (existing or new record)
- However, there were occasions where list would show up as 'No Records' and details screen is partially loaded with blank dropdowns and empty segmented buttons.
- Users were additionally clicking the sync icon on the list screen to ensure that data sources are properly downloaded.
Purpose:
Users should be able to see all data source values when they are in the detail screen
Users will not need to click on the sync icon on the list screen for the app to work.
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 the details screen
- Users can click on the cancel option to go back to the home screen.
Impacts: No Impact
| Anchor | ||||
|---|---|---|---|---|
|
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.
Impacts: No Impact
22.3 Incident Management Micro-Release Items
New and Improved Features
Configurable
- PMP-89335: Riddor Changes
- PMP-89839: Riddor Implementation for Near Miss Incident Type
- PMP-90700: Custom Setting Key for the Local Record Keeping question on the Case Management Screen
- PMP-88162: Hide totals based on OSHA 180 Rule for Non-US Locations
Product Level Change
- PMP-89083: Hide the Report button shown on the Incident Summary screen when it doesn't have any Report links
- PMP-77341: Outbound API for Property Damage Incident
- PMP-77342: Outbound API for General Liability Incident
| Anchor | ||||
|---|---|---|---|---|
|
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'.
- 'Riddor Forms List' screen
...
Impacts: Riddor Reports
| Anchor | ||||
|---|---|---|---|---|
|
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
| Anchor | ||||
|---|---|---|---|---|
|
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.
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
| Anchor | ||||
|---|---|---|---|---|
|
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 :
...
2. Case Management > Case Progression Tracking
| Anchor | ||||
|---|---|---|---|---|
|
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.
.png?version=2&modificationDate=1678873499370&cacheVersion=1&api=v2&width=1200)
| Anchor | ||||
|---|---|---|---|---|
|
...
- Has an outbound API available to extract the data for Property Damage Incidents
Impacts: No impact
| Anchor | ||||
|---|---|---|---|---|
|
...
- Has an outbound API available to extract the data for General Liability Incidents
Impacts: No impact
22.3 Occupational Health Micro-Release Items
...
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.
22.3 Performance Management Micro-Release Items
New and Improved Features
Product Level Change
- PMP-89474 As 92706 As an end user of Sustainability Module I want to bulk export KPI data using an API
- PMP-89783 As an end user of Sustainability Module I want to bulk export KPI Emission data using an API
- PMP-89786 As 92707 As an end user of Sustainability Module I want to bulk export KPI Emission Factors using an API
Configurable
- None
| Anchor | ||
|---|---|---|
|
...
|
...
|
...
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
...
- Has and outbound API, that can be used to export KPI data for one location and year
Impacts: No Impact
| Anchor | ||||
|---|---|---|---|---|
|
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
...
- Has and outbound API, that can be used to export KPI Emission data for one location and year
Impacts: No Impact
| Anchor | ||
|---|---|---|
|
...
|
...
|
...
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
...
- Has and outbound API, that can be used to export Emission Factor for one location and year
Impacts: No Impact
22.3 Operational Profile Management Micro-Release Items
New and Improved Features
Product Level Change
Configurable
- None
| Anchor | ||||
|---|---|---|---|---|
|
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
...
New and Improved Features
Product Level Change
- MP-9416 As an Audit Admin I want to see Conduct Audit confirmation message only when Audit is synced
- MP-9417 As an Auditor I want an indication in list screen if Audit is not yet synced
- MP-9418 As an Auditor I want an indication in list screen if answers are successfully synced or not
Configurable
- None
| Anchor | ||||
|---|---|---|---|---|
|
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
Enhanced System:
- Displays a sync message until the Audit creation completes
- Conduct Audit message is displayed only when Audit creation is complete
- It also has an option to Go to List screen in case the creation is taking longer time due to huge number of questions or slow network
- If user goes to list, this Audit Card will be displayed with Yellow background
- If user taps on the Audit Card "Sync in progress" message will be displayed
- The background will change once the creation is complete and it has synced with Web
- This is done so that user can continue to with other part of the module while Audit creation and sync continues in the background
Impacts: No Impact
| Anchor | ||||
|---|---|---|---|---|
|
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
| Anchor | ||||
|---|---|---|---|---|
|
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
...
- Respective Audit card in Audit List screen will be displayed with Yellow background
- This Yellow background will go away as soon as responses are saved and synced to Web
Impacts: No Impact
22.3 Mobile App Builder Micro-Release Items
New and Improved Features
Product Level Change
- DAP-8029 As an end user I want App data sources to be synced before details screen is rendered
Configurable
- None