PeopleSoft Event Mapping Framework

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.

Pros

• 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.

Cons

 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

Email:eileen.franklin@kovaion.com

PeopleSoft- Fluid Dashboards

Introduction:

Dashboards can be accessed through content reference link and are primarily used for decision making. Dashboards give higher management decision support with high level views of team activities, key metrics and real time analysis.

Fluid Dashboards are counterpart to Classic Dashboard and has the ability to extend them to FLUID tiles allowing access to key information from mobile devices and are introduced with PT8.55.

They are highly role based and provide the summary of visual information and performance. They are easy to configure and appear anywhere in menu structure. Users can personalize dashboards according to their needs and will have the information at their fingertips.

Business Benefits:

• Fluid dashboards are simple and intuitive to use.
•  Provide an easy way for the user to access key information and gives seamless user experience across multiple platforms.
•  They can be optimized across multiple form factors. 
• Provides end user personalization where users can personalize based on their day to day activities.

Similarities with Classis Dashboard:

• Both the fluid and classic dashboards offers similar functionality e.g., both can be configurable and provides the summary of visual information and are role based.
•   Definitions are stored in the portal registry accessed through the Structure and Content component

Differences with Classis Dashboard:

Pagelets are used to modify the objects in Classic dashboard whereas Tiles are used in Fluid dashboard.

Steps in Developing Fluid Dashboard:

Step 1: Dashboards are managed under Manage Dashboard Pages component and please find the navigation below.

Navigation: MainMenu > PeopleTools > Portal > Dashboard > Manage Dashboard Pages

Step 2: Provide the required details as shown below and save the page.

Step 3: New dashboard has been created in Fluid Dashboards section. Access the tiles property and select the necessary tiles to publish the content on the dashboard.

Note: By default, tile property is set to optional which makes the tile hidden from the user. In order to make the tile visible change the property to required and save the page as shown below.

Step 4: Access the dashboard from the parent folder where it was created. Below is the screenshot of newly created dashboard.

Step 5: To access the dashboard from homepage directly, click on actions list button and select add to homepage and select the homepage from which the dashboard needs to be accessed as shown below.

Limitations:

• Unlike classic dashboards, due to some performance reasons, certain types of tiles are restricted for use on FLUID Dashboards only, and cannot be displayed on FLUID Homepages.

      Author: Lakshmi Deepak P

      Kovaion Consulting -PeopleSoft Practice

      Email: lakshmi.deepak@kovaion.com