Handling application events

An application event requires an event handler to do an action in response. Otherwise, the application event serves no practical purpose. If there is no handler for an application event, the event does nothing when generated.

Note: Some events can exist without an associated event handler. Infor includes framework events as part of the system. Infor does not include handlers for these events. These events were created to provide events that other developers can use with their own custom event handlers.

When application events can be generated

An application event can be generated when:

A system user performs an action on a given form or when a business process is involved.
A database calculation is performed that results a certain value.
Another event results in generating this application event.
An amount of time has passed.

For example, these kinds of situations and conditions can fire application events:

A sales representative saves a record in the Customers form.
A manager changes the credit hold status of a customer.
A factory manager adds a new item to the list of manufactured items in that facility.
The first day of each month arrives, for example, an application event can be used to generate a monthly report.
The quantity-on-hand of an item is less than zero.

Where application events can be generated

With the Application Event System, application events can be generated from any tier.

In the client tier, the application event can be generated by using a form that has a form event handler with a Generate Application Event response type.
In the middle tier, the application event can be generated by invoking an appropriate .NET method.
In the database tier, the application event can be generated by using an appropriate stored procedure.
In any tier, an application event can generate another application event by using the Generate Event action type.