What it is?Event Mapping is a new subcomponent of the Related Content Framework. PeopleTools released Event Mapping with version 8.55. What makes it relevant today is enhancements for 8.56. Imagine this scenario: A functional user approaches you with changes he or she would like you to make to a PeopleSoft page. These changes include hiding a couple of fields and changing some labels. For the most part, this is a simple request, but you hesitate to accept the request. Why? Because the user just asked you to modify a delivered definition and you know that you will spend the rest of your PeopleSoft life paying for any simple change you make today. Because there is business value (and you prefer to remain employed), you choose to implement the requested changes. But you ask yourself, how can I make these changes while minimizing upgrade impact? Historically speaking, a good developer, recognizing that these changes are possible through PeopleCode, would create a FUNCLIB or Application Class to hold custom code, and then call that reusable definition from the appropriate location within the delivered event PeopleCode. With the introduction of Event Mapping in PeopleTools 8.55, we now have a new option: we can map an Application Class event handler into a delivered PeopleCode event. This is a configuration that won’t dirty your compare reports. Since your code is no longer merged into Oracle’s code, your changes remain after applying updates.
What is new for 8.56?PeopleTools 8.56 introduces the following long awaited enhancements to 8.56:
- You can now configure multiple handlers for the same event,
- PeopleTools exposed the PageActivate event, which is important for some scenarios to work properly,
- Event mapping now supports the Component Record Field FieldChange event, and
- Event mapping works in Component Interfaces (technically arrived in 8.55.09).