To understand how the Change Notification Assistant works, we have to look at the Audit Log in EventPro.
The Audit Log records an entry of any time there is a change in the EventPro database, including these examples:
•A record is created
•A record is edited
•A record is deleted
•A user logs in
•A user logs out
•And more
In the Audit Log entry for any given change, EventPro will record information, such as:
•the Operation
•the Table Name
•the Object Description
•the Member Name
•the User Name
•And more
A Change Notification Assistant is set up to scan the Audit Log looking for specific entries that indicate the certain type of change you wanted to monitor.
Upon finding a matching entry that also meets any other set criteria, the Assistant will send the notification emails to defined recipients.
You can set a Change Notification Assistant to monitor pretty much any change in the database, as long as you can identify:
•which table to monitor,
and
•which operation should trigger the notification.
You can further refine the triggering change by setting criteria on:
•the Audit Log entry itself,
and/or
•the Object to which the Audit Log entry is pointing.
The Assistant will check to see if the Audit Log entry meets the Audit Criteria, and then check the Object to see if it meets the other Criteria.
IMPORTANT: When creating Change Notification Assistants, ensure that the Audit Operations you want to monitor have not been excluded.
You can choose to Exclude Audit Operations in General System Settings in order to speed up the process of saving records.
However, if you want to use a certain Audit Operation for a Change Notification Assistant, it needs to be active.
To create Change Notification Assistants, follow the instructions below:
•Logs
