Triggers when an applicant presses the button to request their data to be removed from the system, according to the GDPR right to be forgotten.

Triggers when an application is submitted for the first time. Note that there is a separate trigger for re-submitted applications.

Triggers when a priority (course, programme) was added to an application. This happens in conjunction with a new application being created, but it may also happen separately when the applicant decides to add another priority.

Triggers when a new invoice is issued. This can happen automatically using the rules engine or the API, but often invoices are also issued manually by the admissions administrator.

Triggers when a new applicant has registered (on their own). This is separate from an applicant being imported or entered by an advisor/agent.

Triggers when an application is created (either fresh, or by cloning an older application).

Triggers when an application is re-submitted (after being submitted and reopened before). This may trigger multiple times as applications can be reopened and re-submitted by applicants at will. Note that there is a separate trigger for catching just the first-time submitted applications.

Triggers when an invoice was marked as fully paid. This can happen when the applicant makes a payment using a payment gateway (PayPal, Flywire, Mollie, Authorize.net, Simplepay or others) or when the admissions administrator or accountant manually marks the invoice as paid.