Professional Documents
Culture Documents
EC Alerts and Notifications
EC Alerts and Notifications
In this step, you create a workflow for defining the To-Do and email reciepients.Approvers recieve a To
Do Alert.Cc Role’s recieve an email Notification.A reciepient need to be both an Approver and a Cc Role,
to recieve both an Alert and Notification.
Go to Admin Tools-> Manage Organisation, Pay and Job Structures, Create a workflow.
Step 5: Define Business Rules for Alerts/Notifications
Create the backbone of the Alert and notifications services,The business rules to define the checks based
on which Alerts/Notifications will be triggered.
The IF conditions is the logical part where we can define different criterias based on which the Alerts will
be generated.
The THEN condition define the actions which will be done once any records in the HRIS Element satisfy
the logical conditions.
Here we use the workflow information defined in step 3 to define the reciepients, set the effective date on
which alerts/notifications will be sent and the actual message for that particular scenario as shown in the
attached screen.
If we do not define any alert message, the default message formet will be:
Email Header/todo name: Alert for “subject user name”, “event reason”
Email Body/todo detail: Alert fot “subject user name”, “event reason” on “effective start date”.
We can use Date Plus() function to define when the alert will be sent. If you wish for the alert to be
triggered days before or after the Probation End date.(-10 means 10 days before)
Step 7: Create and run the “EC Alerts and Notifications” Job in Provisioning
Here we create a recurring job which should be running daily to have a consistent notifications behaviour
across the board. Whenever we create a job having gaps in between, there have been inconsistencies
observed for Alerts/Notifications.
The rules dont have anything in the IF condition and would have created an Alerts/Notifications whenever
there was a save on the Job_Information HRIS element. The Alerts/Notifications would have been sent 1
month prior to contract end date to the reciepients defined in the managerAlert workflow.
This would have created multiple and duplicate notifications for the same records. Also customer wanted
to have no Alerts/Notifications for the dates in the past. Also there should not be any Alerts/Notifications
for the Inactive employees as well.
This forced us to amend the business rules as well. the new rules which was according to customer
requiement were as follows:
Here the first two conditions ensures there was no multiple/duplicate Alerts/Notifications send.
Third conditions ensure no Alerts/Notifications for the past dated records.
The last conditions ensures that no incative employee recieves the Alerts/Notifications.
Now the Provisioning Jobs needs to be created with LAST MODIFIED SINCE as the date on whcih we
created the new business rules. This was to ensure no notifications is sent using the old business rules.
Key Learnings for EC Alerts/Notifications:
Alerts are triggered when the ‘IF’ condition of the business rule is meet when clicking save on the
corresponding portlet.
The alert message is then triggered and waits statically in the system until the effective date is
reached.
When the effective date is reached and the ‘EC Alerts and Notifications’ job in provisioning is ran
the alerts are sent.
The Job should be created as recurring and run daily.
When creating a Business Rule to trigger an EC Alert & Notification, you should use a ‘Model’
Base Object.
It means the Alerts/Notifications are created based on the business rules IF conditions and then
provisioning job checks records which are modified from a particular date (For recurring job, its the last
date since job run) and sends the alerts.