Advantages of the Application Event System

Application events and event handlers are tagged at the time of their creation with a special identifier (Access As) that prevents them from being modified or deleted by other development organizations. This identifier also prevents your custom events and handlers from being overwritten when Infor or another developer issues updates to their events and handlers.

The application event system provides an infrastructure that allows both the framework and application code to generate application events, and for developers and system administrators to create handlers for those application events. Event handlers can augment or replace the default framework or application behavior associated with the application event. You can design event handlers so that maximal work can be performed without requiring new procedural code.

Event handlers are defined using metadata. Metadata refers to the practice of using uncompiled code and information about data formats that are interpreted during run time, rather than compiled code or procedural code.

The application event system offers several significant advantages over hard-coded systems:

• The application event system provides the power and flexibility to customize the way the system performs without modifying the basic code. Therefore, business processes are easier to modify. You can modify application processes and policies without directly modifying the application code and without writing any procedural code. This means that the amount of procedural code that is required to implement functionality can be greatly reduced or even eliminated altogether.
• You can use your event handlers with events created by others to gain control of the application flow and take appropriate action, rather than being forced to call into the application using APIs.
• Because event handlers are defined using metadata, there is no upgrade problem, and no collision problem if other developers also have event handlers for the same event.