PeopleTools 8.55- Pivot Grid Enhancement

 People Tools 8.55 introduces a number of important enhancements to the Pivot Grid functionality, beginning with the Fluid UI adoption of PeopleSoft Related Content framework. By using enhanced Pivot Grids, users can access a wide variety of transactional and analytic content online, in context with their daily work, rather than requiring them to produce static reports.

Pivot Grids content will be available to users within dynamic Fluid Tiles, on the Related Content pane, on Fluid Dashboards as well as a number of other easily accessible uses within the PeopleSoft applications.

New Pivot Grid enhancements in 8.55 release of People Tools span multiple aspects of this important functional area. People tools 8.55 focused more on concerns for performance as well as the ease of use of Pivot Grids for developers and business analysts to design, construct and publish Pivot Grids. From People Tools 8.55, Composite Query is added as a source for Pivot Grid content, a feature that greatly extends the reusability of a portfolio of underlying modular query sources.

Pivot Grids also provides the option for users to “Save As,” so that users  can name and save a Pivot Grid definition for their own future use. This section describes the new features for Pivot Grid, including:

• Simplified Analytics
• Introducing Editable Facet in Fluid
•  Introducing  Single select and Multi select Facets
• Sort Data in Pivot Grid Fluid
•  Drilling URLS in Fluid
• Format Date Fields in Pivot Grids Charts/Grid
•  Introducing new Aggregate Function ‘Count Distinct’
•  Introducing new Dual Y Axis
•  Display Mode Section now Removed
•  Introducing Threshold Settings Configuration
•  Introducing Composite Queries as Data Source
•  Copy Pivot Grid Model Now available for all users.

Create Contextual Reports using Simplified Analytics:

1.       Starting People Tools 8.55, Simplified Analytics feature enables users to create contextual reports when accessing an application page.

2.       The Simplified Analytics feature is only available for fluid components, and this feature must be enabled for fluid components before users can use the Simplified Analytics wizard to create and view analytic reports.

3.       Users can create own Pivot grid models for Simplified Analytics, starting People Tools 8.55!

4.       Associate one or more pivot grid models to a component

5.       Map page fields to the prompts that are associated with the template model and define the required context.

Introducing ‘Editable Facet’ for Fluid:

1.       Use the Editable Facet field in Pivot Grid Wizard to enable the data source columns as editable facets (prompts) in fluid view.

2.       Enable this option for the columns that are set as Axis or Value and not Display in the column type.

3.       Different operators are available for different type of fields.

4.       Editable facets are valid only while viewing the Pivot Grid models in fluid view.

Note: Editable facets are not applied while viewing the pivot grid in classic view.

Introducing Single-select and Multi-select Facets:

1.       Use the Specify Data Model Options page, Fluid Mode Options section, Facet Selection region to set the facet display options to display the single-select and multi-select facets as charts and as lists in fluid views.

2.       In the chart facets, drill down by clicking the chart data point in the facets.

Note: Update Filters option can be used in the Menu Options list to add or remove existing facets in the model.Inorder to sort data in facets and filters, use the Facet Sort icon at the top-right of each facet

  Sort Data in Pivot Grid Fluid:

   Sorting the data is possible in four areas of the Pivot Grid fluid views: detailed view, facets or filters, charts, or grids, (sorting facts only).

  Drilling URLs in Fluid:

1.      Use the Specify Data Model Options page, Fluid Mode Options section, Drilling URL Options region to define how mapped drilling URLs will appear in fluid view.

2.      The available options are Full Page Modal, Modal Window, New Window, and Replace Window.

   Format ‘Date’ fields in Pivot Grid charts/grids:

1.       Use the Date Format field on the My Preferences page (Main Homepage, My Reference, and Regional Settings) to set the format of the date fields in Pivot Grid charts and Pivot Grid grids.

2.       The format settings at this page are applied for all date values in fluid view.

   Note: This applies to classic view as well.

   Introducing new Aggregate function ‘Count Distinct:

1.       Beginning from People Tools 8.55, additional option Count Distinct is available to define the aggregate functions.

2.       Note that Count or Count Distinct aggregates are available for the fact fields that are set to character.

   Introducing new ‘Dual Y Axis’:

1.       This is available only for the columns that are set to Y axis.

2.       Use this column to set the corresponding Y axis column as a dual Y axis on the Pivot Grid charts; this means that the system will display a second Y axis on the chart.

3.       The values for the second Y axis will be plotted like a Series on the chart.

4.       Now use Multiple Columns as Y-Axis.

5.       When Pivot Grid Wizard is used to specify axis information, multiple columns can be set as Y axes, and these Y axes will be plotted as series on the charts.

   Display Mode’ section now removed:

1.      Beginning from People Tools 8.55, the Display Mode section is no longer available in Pivot Grid Wizard, Specifying Data Model Options page.

2.      Use the Pivot Grid Viewer search page to open and view the Pivot Grid models in either fluid view or classic view.

PeopleTools-8.54

PeopleTools-8.55

  Introducing Threshold Settings Configuration:

Ø  Use the Configure Thresholds page to configure the basic threshold settings for the grids and the charts. 

  Note:All threshold settings are applied for both classic and fluid views.

   Introducing Composite Queries as Data Source:

1.       People Tools8.55 onwards, composites queries can be associated as the data sources while creating Pivot Grid models.

2.       The steps used to create composite query Pivot Grid models are similar to the steps used to create PS Query or component Pivot Grid models.

   Copy Pivot Grid Models’- now available for All Users:

1.       In the previous People Tools releases, only Pivot Grid administrators could copy an existing Pivot Grid models while viewing the models in Pivot Grid Viewer.

2.       Beginning from People Tools 8.55, all users can use the Save As option in the Menu Options list to copy the current Pivot Grid model and save it as a different one.

3.       If personalisation are defined for the current Pivot Grid model, then personalisation are also copied and included in the new model.

   Pivot Grid Configuration

   While creating a pivot grid model, the configuration is stored as application data in numerous People Tools Pivot Grid Tables.    

   Application Data can be migrated using either:

•     Data Mover ->  No compare or validation.
•       Data Migration Work Bench -> Ability to perform a compare

   Migrating Pivot Grids Models with Data Mover:

1.       On the source database, select Reporting tools, pivot grid, pivot grid Administration.

2.       Select the Generate Scripts Tab.

3.       Search for and select the pivot grids to export.

4.       Optionally include personalization.

5.       Click Generate Scripts.

6.       Copy the Export Scripts to a file.

7.       Copy the Import Script to a file.

   To Export the Pivot Grid Model:

1.       Sign onto Data Mover for the source database

2.       Open the export script in Data mover.

3.      Modify the script for the output file locations and name, if desired.

4.      Execute the script.

5.      The .dat and Log files are created.

    To Import the Pivot Grid on the Target Database:

1.       Sign on to data mover on the target database.

2.       Open the import script in Data Mover.

3.       Modify the script for the output file locations and name, if desired.

4.       Execute the script.

    NOTE: This will import the Pivot Grid only-the PS Query for the pivot grid must exist on the target database.

    Data Migration Work Bench

  ·         Ability to perform a compare

   Best Practices:

•       Use query with no joins and unions

•       Don’t use the query that has and expression as the axis field.

•        Make sure that Query performance should be efficient enough to render quickly in the grid and in the chart.

•       Pivot Grids offer a strong option for analytical reporting needs.  

•       The data needed to manage the company will be at user’s fingertips.

•       PeopleSoft Pivot Grids enables users to drill down to the transactional level. 

•       Eliminates the need for exporting the data to excel and pivoting it over there

•       Another added advantage is that user could configure related actions.

  Benefits:

•       Pivot Grids offer a strong option for analytical reporting needs.  

•       The data needed to manage the company will be at user’s fingertips.

•       PeopleSoft Pivot Grids enables users to drill down to the transactional level. 

•       Eliminates the need for exporting the data to excel and pivoting it over there

•      Another added advantage is that user could configure related actions.

    Limitations:

•       It does not have a vertical scroll bar for viewing data, but it displays all possible rows based on the current layout.

•        Pagination is not available.

•        Pivot Grid supports up to 75 axes and values and the character limit for each is 30.

Author: Keerthi Chaitanya P

Kovaion Consulting- PeopleSoft Practice

Email:keerthi.chaitanya@kovaion.com 

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