Application events

This table lists and describes the application events that ship with the system. To use these application events, you can employ the event handlers, if any, that already exist for these application events; or you can create your own handlers.

Event name Trigger Context attributes to be passed as event parameters, in addition to the object name
AssignUserToAdminLicenseModule Internal UserId (UserId from the UserNames table)
AssignUserToLicenseModule Internal Username (Username from the UserNames table) and Modulename (ModuleName from the Modules table)
GenericNotify
  • When the Task List (or anyone else) fires this application event for a reminder
  • When the NotifyPublicationSubscribersSp stored procedure is called for a subscriber who has no email address
ToVar, SubjectVar, CategoryParm, BodyVar, HTMLBodyVar (To, Subject, Category, and whether the Body is expressed in HTML, of the Notify action)
GenericNotifyWithAttachments When someone clicks the Send Email for the current object button on the toolbar For internal use only. This application event and its actions are specific to and integrated with a Core process.
GenericSendEmail
  • When the NotifyPublicationSubscribersSp stored procedure is called for a subscriber who has an email address
  • Upon receipt of a SyncPulseNotification or SyncPulseAlert BOD, if ION pulse interface process default is set to 1
EmailTo, EmailCc, EmailSubject, EmailMessage, EmailHTMLFormat (To, Cc, Subject, Body, and whether the Body is expressed in HTML, of the Send Email action), AttachmentFileList, AttachmentNameList, AttachmentDocTypeList (lists of files to attach to the email, their names, and document types)
GenericSendPulseAlertBOD Not applicable. This application event is not used directly by the framework. This application event is available for applications to fire. UserEmail, MessageSubject, MessageDescription, MessageBody
ProcessNewDataMaintenance When someone clicks Finish in the Data Maintenance Wizard For internal use only. This application event and its actions are specific to and integrated with a Core process.
LocalizeDataLake When someone clicks the AES Insert button on the Data Lake Data Populator form
PurgeHistoryData When the trigger is made active using the Command Line Interface (CLI).

When the trigger is made active from the Event Service.

PurgeDBMethodToCall: PurgeEventDataSP, DaysOld
TaskListCheck When the TaskListCheck event trigger fires from the Event Service None. There is no reason to fire the application event apart from the existing event trigger.