The Event Notifications log displays events that happen within the Workflow, or Non-workflow, BPs according to the conditions defined by the designer, in uDesigner.
Note: Unifier runs automatic purge every day in order to delete the notification records that are older that one month.
By design, the event notifications are generated for all active (Active) BPs (within the project or shell).
If you do not want to generate event notifications for certain WF BPs (within the project or shell), then Oracle recommends that you use a new WF that does not have the notification setup.
Note: If it has been set up in uDesigner, you cannot avoid generating even notifications for Non-WF BPs. Unifier generates notifications for all of the records that meet the setup conditions.
If any BP record moves to the step which is set up to generate event notifications by way of web service or CSV, then the event notifications is generated and recorded in the events log, also. This applies to WF and Non-WF BPs.
Event Notifications toolbar options:
View | Similar to the View option in BP log (Logs node), Standard View, it enables to use one of the following system-defined default views:
|
|---|---|
Edit View | Similar to the Edit View option in BP log (Logs node), Standard View, it enables you to edit the:
|
Refresh | Similar to the Refresh option in BP log (Logs node). |
Similar to the Print option in BP log (Logs node). | |
Search | Similar to the Search option in BP log (Logs node). |
Find on Page | Similar to the Find on Page option in BP log (Logs node). |
Event Notifications grid (Workflow BPs):
For the Workflow BPs, the grid displays a record of all of the workflow actions that are taken within the BP records, and which are set with the Generate event notification option as checked, in uDesigner.
A Workflow BP step completion policy does not impact the creation of the notification row. Regardless of the completion policy, if an action (which is setup to generate an event notification) is taken in the Workflow BP record, then the notification row is inserted in the log.
If there are multiple assignees on a step, then the final action on the Workflow BP record, which moves the record to the next step, determines what will be included as an event notification row in the grid, not each action taken by an assignee.
If a task is reassigned and the new assignee takes an action that moves the record to the next step, and the record is configured to generate a notification, then Unifier inserts an event notification row in the grid, also.
Unifier populates the grid columns within the newly inserted notification row with the values of the Workflow BP records.
Event Notifications grid (Non-workflow BPs):
For the Non-workflow BPs, the grid displays all workflow actions that are set with the Event Notification status (BP status) as "Yes", in uDesigner. When the Non-workflow BP record reaches a status, as set in uDesigner, then Unifier inserts a notification row in the grid.
Note: If a user clicks Edit on a Non-workflow BP record and proceeds to click Finish Edits without making any changes, but the status change is set to generate notifications per the design in uDesigner, then Unifier inserts a notification row in the grid, also.
Unifier populates the grid columns with the values of the newly inserted notification row from the values of the Non-workflow BP records.
Event Notifications grid columns:
Column Name | Description | Applies to WF BPs | Applies to Non-WF BPs |
|---|---|---|---|
Shell Number | Populates with the project or shell number where the event was triggered. | Yes | Yes |
Shell Name | Populates with the name of the project or shell where the event was triggered | Yes | Yes |
Object Type | Populated as, "Business Process." | Yes | Yes |
Object Sub-Type | When the Object Type = Business Process, then the Object Sub-Type is populated as Workflow or Non-workflow, based on the type of the BP. | No | Yes |
Object Name | Populated with the name of the Business Process in which the event was triggered | Yes | Yes |
Record Number | Populated with the "record_no" value of the BP record that triggered the event. | Yes | Yes |
Event Date | Populates with the date and time, when the event was triggered. The content of this column is in descending order, which is the default sort format. | Yes | Yes |
WF Step From | Populates when the event notification is for a WF BP. This column is populated with the name of the starting step of the record that have triggered the notification generation. | No | Yes |
WF Step To | Populates when the event notification is for a Non-WF BP. This column is populated with the name of the final step of the record that have triggered the notification generation. | No | Yes |
WF Action Name | Populates with the WF action name that was taken for the BP record that triggered the notification. Note: The same BP could go through several events which trigger the notification generation. Each such event inserts a corresponding row in this log. | No | Yes |
Old Status | The original status of the BP record (before the event got triggered). | Yes | Yes |
New Status | The final status of the BP record which satisfies the event trigger condition. | Yes | Yes |
To set the Event Notifications node permissions:
- Go to the Company Workspace tab and switch to Admin mode.
- Click Access Control in the left Navigator.
- On the right pane, select Administration Mode Access > Event Notifications to open the Permission Settings for Event Notifications window.
- Set the View permission to users and groups as needed.
Users or groups with the View permission have the ability to:
- See the Event Notifications node in the left Navigator.
- Take actions using available options in the log toolbar.
- View all notifications records within the log.