New and Improved Features
...
Product Level Change
Anchor | ||||
---|---|---|---|---|
|
Configurable: Yes
- Title: Enable Incident Locking
- Public/Private: Private
- Default: No
Existing System:
Does not have the functionality to lock the incidents based on Incident Status and information can be modified at any point in the workflow.
This inability to restrict users from modifying incident information, especially at later stages of the workflow leads to data integrity issues.
...
Note: Incident locking is not available in Mobile in this version. Customers using Mobile Pro should not enable this feature.
Impacts: Insight
...
Configurable: No
- Title: NA
- Public/Private: NA
- Default: NA
Existing System:
Does not have OSHA 300/301 API integration to do e-submission directly from the system
- Does not have character limit validation on "Incident Location" and "Incident Description" fields in OSHA 300 Review
- As of now these fields are auto populated from Incident Detail report and in that screen the source fields allow to enter more characters
Purpose:
- Make it easy to e-submit OSHA 300A, 300 and 301 case data directly from the system
- Align character on fields as per OSHA ITA specification
Enhanced System:
Has a new button to do OSHA 300 and 301 case data submission using API
- Supports data submission for all locations under a Level
- Has character limit validation in OSHA 300 review screen as per OSHA ITA specification
- There is flag displayed in the OSHA 300/301 Case Data list with case number if Incident Location or Incident Description fields have more than 255 characters
- In this case user cannot do e-submission via CSV or API as system will display in alert
- When user navigates to OSHA 300 review screen, respective field have more than 255 characters will be highlighted
- There is a help icon placed against these fields for users' reference indicating that fields have a character limit of 255 characters
- Up on save system will once again validates if these fields have less than or equal to 255 characters
- There is no impact to any existing data
- Has Activity log to track data submission and submission status
...
Location
...
Module
...
Screen Name
...
Action
...
Activity
...
<Location Name>
...
Incident Management
...
OSHA 300/301 Case Data List
...
Exported
...
<Establishment Name> Data Exported via API from Location | <Count of Records>
Impacts: No Impacts