Event Mapping is a useful feature that was introduced in PeopleTools 8.55, and we've been enhancing it ever since. We've added additional events that can have event mapping code injected, and we've introduced features in App Designer to make it easier for the developers to maintain their event mapping code.
Event Mapping doesn't make writing customizations easier, but it removes or greatly diminishes the impact and cost of customizations when you take new images. This makes new image uptake easier, cheaper, and faster and allows you to continue to meet unique, important requirements.
The basic concept is straightforward: Event Mapping enables you to inject custom code before or after delivered event code. There are some key benefits of Event Mapping:
A developer writes their Application Class custom code in App Designer. Note that as of 8.57, the PeopleCode Editor provides an Event Mapping button in the Application Designer toolbar as a visual indicator of custom PeopleCode programs mapped to events of a component, component page, component record, or component record field. The indicator is enabled when the PeopleCode is being viewed for one of these events. In addition, the Find Definition References tab on the output window lists the events that are mapped to custom PeopleCode programs, along with the application class. The Find Definition References tab lists references to other components where the custom PeopleCode programs of the selected application class are used.
Mapping your custom code is done through the Related Content Framework, which enables us to keep your code separate from the delivered logic.
The list has been growing ever since Event Mapping was introduced.
Component Level events:
Component Record level events:
Page level events:
Field level events:
We've added several enhancements to support broader usage of event mapping with Drop Zones, for data privacy, and other uses. Event mapping now supports FieldDefault, FieldEdit, SearchInit, and SearchSave events for component record fields, and SearchInit and SearchSave events for component records.
Event mapping now also supports records and record fields on subpages and secondary pages at any level of nesting, not just for primary pages explicitly defined in the component. This enhancement extends support to the page Activate event for secondary pages and to derived work records.
Developers can now use a single application class service ID for multiple configurations. This enhancement simplifies PeopleCode development because multiple blocks of code can be delivered in a single application class. Then, during configuration, you can use a new event mapping parameter to selectively invoke the specific block of code that pertains to a specific event.
Customers that have heavily customized their PeopleSoft applications should look seriously at Event Mapping to isolate those customizations to provide a better PeopleSoft life cycle. Event Mapping can even be used in concert with other configuration features to dramatically reduce the impact of customizations.
For more information on Event Mapping and other configuration features, see this page on peoplesoftinfo.com.