Restricting which handlers run

There might be times when you want or need to disable the event handlers created by one or more development organizations, including yours, at least temporarily. This occurs typically when you are troubleshooting problems with the Application Event System (AES).

You can disable event handlers by using the Event Handlers form or the Session Access As form.

  • To disable event handlers temporarily using Event Handlers form, clear the Active check box.
    Note: You cannot use this technique to disable Core event handlers.
  • To disable (or enable) all the event handlers that are created by your development organization all at once, use the Session Access As form.
    Note: To accomplish the same thing for individual handlers with your Access As value, open the Event Handlers form. For each event handler that you do not want to include in testing or debugging, clear the Active check box.

For example, suppose a customer has a problem that he suspects is caused by something that he did in the event system, but he is not sure what. He places a call to Infor Customer Support.

The Customer Support representative verifies that the customer’s custom event handlers are not causing the problem. The Customer Support representative asks the customer to temporarily disable all custom event handlers so that the operation can be tested with only standard functionality in place. The Customer Support representative instructs the customer to use the Session Access As form to perform one of these actions:

  • In the Include Access As field, specify Core,BaseAppAccessAs, where BaseAppAccessAs is the Access As identifier associated with the base application installed on the system.
    Note: This option allows only the Infor framework and base application event handlers to execute. Custom event handlers that are created by the end-customer do not execute.
  • Leave the Exclude Access As field blank, and select the Exclude Blank Access As check box.
    Note: This option allows all Infor and business partners event handlers to operate. Only the customer’s event handlers are ignored.

To disable or enable event handlers using the Session Access As form, use any of these options:

  • In the Include Access As field, specify the Access As identifiers for event handlers that are recognized during this session.
    Note: To include multiple Access As identifiers, specify them and separate them only with commas (no spaces).

    If this field is left blank, the system recognizes and executes all event handlers.

  • In the Exclude Access As field, specify the Access As identifiers for event handlers that are to be ignored during this session.
    Note: To exclude multiple Access As identifiers, specify them and separate them only with commas (no spaces).

    If this field is left blank, the system recognizes and executes all event handlers. The only exception to this occurs if the Exclude Blank Access As check box is selected. In this case, all event handlers are recognized except event handlers for which the Access As identifier is null (blank).

  • Select the Exclude Blank Access As check box to exclude the event handlers that have a blank Access As identifier.