About application events

An application event is defined as a uniquely named situation that can be triggered by these things:

• Actions performed by users working in the system
• Conditions that occur while the system is running
• Certain values that are exceeded in a database record
• Another event’s handler
• Other similar occurrences

Application events can be one of these general types:

• Framework events: These are events that Infor has defined and built in to the system. They are tagged with an Access As identifier of Core and a Framework indicator on the Events form.

  These events generally fall into one of these categories:

  • Business process-related events that are generated when certain IDOs (Intelligent Data Objects) are invoked

    These IDOs include IdoOnItemInsert, IdoOnLoadCollection, IdoOnInvoke, and others. You can identify these events easily by their names, which begin with the letters Ido.

  • Session events that are generated when certain session activities take place

    These include SessionOnLogin, SessionOnLogout, and SessionOnVarChanged.

  • Business Object Document (BOD) events that are generated when certain BOD-related operations occur

    You can identify these events easily by their names, which begin with the letters Bod.

  • Task events that are generated when certain operations are initiated by the TaskMan service

    You can identify these events easily by their names, which begin with the letters Task, excluding TaskListCheck.

  These events are always synchronous and transactional. Some can optionally be suspended to await user responses.

• Application-specific events: These are application events that typically have been created by Infor, its business partners, and authorized vendors. They are tagged with an Access As identifier that indicates what application or development organization they belong to, which can include Core.
• Customer-defined events: These are events that a developer in an end-customer organization has created. They are normally tagged with a blank Access As identifier, which indicates that they were created by and belong to the customer.