...
Anchor | ||||
---|---|---|---|---|
|
Product Level Change
PMP-94956 - User would like to have the access implemented in the summary report so that only authorized users can see the investigation dataNone
Configurable
PMP-94330 - User would like to have the ability to generate and export OSHA 300-301 CSV file
PMP-95310 - User would like to edit DOB field in OSHA 301 screen based on a configuration
PMP-95710 - User would like to submit 300A data using the API Token
Performance
PMP-94436 - IMS-Autocomplete Control Performance Improvement
Technology
PMP-94407 - AAP Retail Calendar - DB Design & Script to load data
PMP-94443 - IMS-Checkmarx Version Upgrade (9.5.0)
PMP-94777 - IMS Datamart - SQL Server Upgrade 2019
PMP-93190 - IMS-SQL Server Upgrade 2019 - Feed
Anchor | ||||
---|---|---|---|---|
|
Configurable: Yes
Title: OSHA 300/301 Case Data E-Submission
Public/Private: Public
Default: No
...
All Cases - Previous Year (Default View)
All Cases - Current Year
300 & 301 Review Status Display & Validation:
300 & 301 Screen review status will be displayed on the list.
Only if all required fields are completed and saved, then 300 & 301 review is treated as complete.
Only CSV can be generated only once both screens screen's status turns 'Complete', only then CSV can be generated.
Generate CSV :
There will be a 'Generate CSV' button at the top right corner of the screen.
There won't be any separate permission to enable/disable this button.
...
Anchor | ||||
---|---|---|---|---|
|
Configurable: Yes
Title: IMSEmpDOBPrivacyInfoShowYN
Public/Private: Public
Default: Yes
...
User will be able edit DOB field in OSHA 301 based on permission and configuration.
The existing custom setting (Which is already in use in the reporting screen) is used in the OSHA 301 screen as well.
Additionally, if the user has edit OSHA 301 permission, then the DOB field would be visible and available for editing.
If the user only has view OSHA 301 permission, then DOB field would just show as “Privacy Information”.
Impacts: None.
...
Anchor | ||||
---|---|---|---|---|
|
Configurable: No
Title: OSHA Form 300A Electronic Submission using API Token
Public/Private: NA
Default: NA
Existing System: Currently, the system doesn't have an option to submit 300A data to OSHA's ITA (Injury Tracking Application) using the new API Token process as the 300A data was previously transmitted to OSHA’s ITA by entering ITA account credentials
Purpose: To comply with regulatory requirements.
Enhanced System:
Enhanced the submit using OSHA API option to allow users to paste an API Token copied from OSHA’s ITA (Injury Tracking Application) in order to transfer a location's 300A data to ITA.
Added guidance information to the information pop-up.