Configuring Global Event Mapping

Global event mapping enables you to map application class PeopleCode programs to the PostBuild event of all components at a global level.

Global events are triggered after any existing PRE/OVERRIDE/POST event mapping configurations associated with the PostBuild event of the target components are completed.

Currently, PeopleTools does not deliver a configuration page to define global events. Global events can be configured using the delivered methods of the PTCS_GLOBALEVENTMAPPING application package, such as CreateGlobalEventMappingConfig and DeleteGlobalEventMappingConfig.

For more information on the delivered methods, see PeopleCode API Reference: GlobalEventMapping Class Methods.

Considerations for Using Global Event Mapping

When you plan to perform event mapping on a global level, you should consider the following:

  • You must ensure that global event mapping does not impact the loading of components from performance and error handling perspectives.

  • You should ensure that errors are handled gracefully.

  • You should be aware that if a page has multiple components, component-based grouplets, component-based pagelets, or component-based modals and so on, the configured global events run on each of the loaded components. Therefore, your PeopleCode logic should conditionally identify or filter the components, component-based grouplets, component-based pagelets, or component-based modals to ensure that the required logic is run only for the required components.

    For example, if a page contains a target component and a component-based grouplet, and you want to run it only for the target component, then your PeopleCode logic should perform a conditional check to exclude the component-based grouplet.

Prerequisites

Before you create a global event mapping configuration using the CreateGlobalEventMappingConfig method, you must create a related content service definition.

See Creating Service Definitions for Event Mapping for more information.

Verifying the Global Event Mapping Configuration

The following database tables – PSPTCS_SRVCFG and PSPTCSSRVCONF – store the event mapping configuration data. After you create a global event mapping configuration using the CreateGlobalEventMappingConfig method, you can verify the configuration using the following SQL statements:

  • SELECT * FROM PSPTCS_SRVCFG WHERE PORTAL_OBJNAME LIKE 'PTCS_EVMAP_GBL_%'

  • SELECT * FROM PSPTCSSRVCONF WHERE PORTAL_OBJNAME LIKE 'PTCS_EVMAP_GBL_%'

WARNING:

Oracle recommends that you do not directly modify these database tables containing configuration data using SQL.

You can identify the global event mapping configuration by the data contained in the PORTAL_OBJNAME and the PTCS_PROCSEQ columns of these tables.