E1: 54HS: Notifications Logic To Be Incorporated In Incident Management Process Work Flow
(Doc ID 1925037.1)
Last updated on APRIL 04, 2019
Applies to:JD Edwards EnterpriseOne Health & Safety Incident Management - Version 9.1 to 9.1 [Release 9.1]
Information in this document applies to any platform.
Notifications Logic to be incorporated In Incident Management Process Work Flow
Today notifications are sent to users only during incident entry.Also to whom notifications are sent is configurable in processing options which will increase the number of versions in play.
A new simple logic is provided here to have multiple notifications flowing through the entire incident management life cycle.
1. On incident entry, in who section, whoever person entered should get a notification on incident saving.
If HSE rep’s address is entered, then notification should go to him. There will be different processing options like send notification to a.victim only b. Victim & HSE rep or c. HSE rep only.
2. When incident investigator & Handler are assigned on the Incident master screen, then notifications should go to them. This again controlled through PO values. A) To send notification to creator only. B) To investigator & handler. C) Don’t send any notifications.
3. When tasks are assigned & approved, notifications to go to task assignees, investigation leader & Incident Handler. Whenever task status gets changed, again notifications to go to task assignee investigation leader & handler controlled through PO (a)assignee only, b)assignee & Investigation leader & handler, c). all the three
4. Whenever incident status changes different type of notifications should go to incident investigator & Handler in most cases.This would be based on the entries in notification table.
5.Cross reference between notification template id's # & incident statuses.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document