The PeopleSoft Partner Summit at COLLABORATE 19

The PeopleSoft Partner Summit at COLLABORATE 19

New this year, Oracle held their annual PeopleSoft Partner Summit at the end of COLLABORATE 19. The PeopleSoft Partner Summit is an opportunity for Oracle and the PeopleSoft Partner community to exchange ideas and information. Both at COLLABORATE 19 and at the Partner Summit, configuration and de-customization were large elements of the messaging. Although a number of tools (i.e. drilling URL’s, fluid pivot grids, fluid navigation collections and simplified analytics) have been around for several years now and have their own influence on reducing customizations, there were four primary tools that were the focus of this year’s messaging.

Page and Field Configurator

The Page and Field Configurator allows users to change the look of the fields and page content.  Users can change field labels, hide fields and even make fields required or display only. All of this is now a part of configuration and no longer needs to be customized using the application designer. Click here to watch a MIPRO Video Blog on the Page and Field Configurator.

Event Mapping

Event Mapping is a PeopleSoft delivered framework which helps applications and customers adapt PeopleSoft to business needs with minimum upgrade impact. Benefits include extension and modification of PeopleSoft for specific business needs, the introduction of Business Logic as configuration instead of customization, the developing of a re-usable code and artifacts, and customer code not being overwritten by PS delivered code during an upgrade.  Click here to watch a Quest webinar on Event Mapping.

Drop Zones

The ability to add new fields to pages for future processing without customization.  Click here to watch an Oracle video on PeopleSoft Drop Zones.

Forms and Approval Builder

For processes outside of PeopleSoft, users can configure a data entry form, capture the data, and leverage approvals.

There are many capabilities which offer organizations both the ability to avoid customizations and de-customize what currently is in place.  Organizations are starting to put de-customization on their list of priorities, and it should become an activity made part of the PUM update process.

If you would like more information on any of the above topics, please email me at

+ posts