What is Event Mapping Framework?
If any delivered page has to be customized, user can simply modify and add the business logic to the necessary events. However, in the selective adoption model, user will be forced to retrofit customisations every time on a new image, fix etc.
The Related content event mapping frame work, a part of related content framework (RCF), enables users to inject custom code to component/component field events without modifying the actual objects. It is essentially a driver to create built on solutions for applications. This still involves customizations but is easier to maintain and retrofit.
How to implement Event Mapping?
Step 1: Application class with business logic
- Identify the target event, have good understanding on the context and component buffer.
- The app package should extend PT_RCT:ServiceInterface
- The business logic should be present in the Execute method
Step 2: Create a related content service definition
- Create a new related content service definition in the below navigation.
- Provide the application package name and class which contains the business logic.
Step 3: Map the related content service to the event
- · The mapping is done in the following navigation
- Navigate to event mapping tab and select the component to inject the business logic.
- Select the event to inject the business logic and the sequence in which it should be executed.
- Component events/Component record events can be selected.
Migration of Event Mapping Framework
Include the following object into project
o Related content definitions – ensures the migration of related content definition and application package.
o Related content services (Related content configurations & related content layouts) – ensured the migration of event mapping configuration.
- Allows customizing delivered functionality without modifying any delivered objects. This makes maintenance and retrofitting customization much easier.
- Users can include all modifications for a module in a single application package with sub packages for each component and each customization should be its own class.
- A single app package would be the entire module which makes migration, documentation and knowledge transfer much easier.
- Map generic application class to multiple components. If the same business logic is needed in many components the event mapping is sufficient.
Users can insert code before or after the event code. If the business logic requires the customization in between the existing code this feature does not support it.
Author: Eileen Franklin
Kovaion Consulting- PeopleSoft Practice