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 |
|
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 | button on the toolbarFor internal use only. This application event and its actions are specific to and integrated with a Core process. |
GenericSendEmail |
|
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 Data Maintenance Wizard | in theFor internal use only. This application event and its actions are specific to and integrated with a Core process. |
LocalizeDataLake | When someone clicks the Data Lake Data Populator form | button on the|
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. |