New and Improved Features

Configurable

Product Level Change

Configurable: Yes

Existing System:

ThereDoes 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.

Purpose:

Restrict users to modify incident information based on incident status to maintain data integrity

Enhanced System:

Has a configuration to enable/disable incident locking
- the configuration is applicable for all incident types
- This configuration will be effective if “Display Incident Status” configuration values is Yes
When enabled,
- System will lock Incident Detail, Investigation section and Management Review when Incident status is set to Closed by a user.
  - A confirmation message will be displayed when user changes the status to Closed.
- There is option to edit locked sections of an incidents or delete locked incident based on a new permission "Edit Locked Incident".
- Lock symbol will be displayed in Incident Summary screen for respective sections and in the list screen next to Closed status.
- Reopen option will not be available.
There is new notification event available for Incident Status change
- This will be available only if “Display Incident Status” configuration values is Yes
- The notification would trigger to configured recipients every time the Incident status is changed irrespective of locking configuration
- Subject: <System Name> - <Event Name> Changed to <Incident Status Value> for <Incident ID> | <Incident Type> - <Incident Sub Type>
Existing incidents where status is already Closed, will not be locked, even if user navigates to summary screen
- If such incident should be locked, status should be changed once again.
- A bulk locking can also be done on demand.

Note: Incident locking is not available in Mobile in this version. Customers using Mobile Pro should not enable this feature.

Impacts: Insight

Image Added

Configurable: No

Existing System:

ThereDoes 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

Image Added

Versions Compared