PeopleSoft Page and Field Configurator

This blog post is the second in a series of blog posts in which we will guide you through the benefits, options and complexities of reducing customisation in PeopleSoft. We take a look at the various tools that Oracle offers to replace customisation by configuration. Today we take a look at the Page and Field Configurator and how it could be leveraged to isolate or prevent customisation. Step away from complex and costly PeopleSoft maintenance and upgrades by keeping your level of customisation low.
Configure; don’t build
In my previous blog post we discussed why it is important to reduce the number of (disruptive) customisations to PeopleSoft. We also found that we can keep the level of customisation low by leveraging PeopleSoft's configuration options. The Page and Field Configurator is one example of using native tools to minimize the need for customisations.
What is Page and Field Configurator?
Page and Field Configurator is a configurable framework built upon PeopleTools Event Mapping. It provides you with the ability to:
- Modify labels
- Hide fields
- Disable fields for data entry
- Require a field for data entry
- Specify a default value for a field
- Hide an entire page
- Make a page read-only
- Mask data in fields
- Track information changes by users.

Page and Field Configurator is usable on both classic as Fluid pages. And this all without the use of Application Designer!
How to use Page and Field Configurator
Page and Field Configurator can be found under Navigator > Enterprise Components > Page and Field Configuration > Page and Field Configurator. Based on the type of change you want to make you need to select a configuration type.
Configuration types
Page and Field Configurator delivers three configuration types that each provide a unique set of capabilities. These configuration types are:
- Standard Configuration Type - which allows for modifying fields and hiding pages
- Masking Configuration Type - which allows for masking of data within fields
- Change Tracking Configuration Type - which allows for tracking user made changes.
You can define multiple configurations for a component based on different user roles, system variables and multiple criteria based on the component fields. This enables you to selectively apply the configuration at run time based on actual values. For example this enables you to set a different set of default values per business unit. Or hide specific fields from a page for users from a specific business unit.
Steps to configure a component
To configure a component using Page and Field Configurator you need to follow three high level steps:
- Define the page and field level changes to be made in the selected component using the Page Configuration page.
- Define the list of users to whom the configuration needs to be applied using the User List page.
- Map the configurations to the corresponding portal registry entries using the Map to Portal Registry page.
Change tracking
Where the standard configuration and masking functionalities speak for themselves, the change tracking functionality might need some additional explanation. The change tracking functionality gives you the ability to track changes that are made by users to the information (or data) on the page. Changes can be tracked on specific fields and on specific components using criteria such as fields on the page and the users role.

These changes can then be displayed as related content to other users. This gives your users insight into the transaction history of the information displayed on the page. For each tracked field the following information is shown:
- The field that changed
- The date of the change
- The user who made the change
- The new value of the field
- The prior value of the field.
Migration Page and Field Configurator configuration
All page and field configuration can be exported as an Application Data Set (ADS) file. By this means you can import it to the desired target database. The data set definition EOCC_CONFIGURATION can be used to export the Page and Field related configuration. As Page and Field Configurator also leverages PeopleTools Event Mapping (which will be discussed in a future blog post) behind the scenes, you additionally need to export the event mapping configuration. For the event mapping configuration the data set definition RCF_SERVICES needs to be included in your ADS project.
Limitations
Although Page and Field Configurator is a powerful tool that allows organizations to tailor delivered PeopleSoft pages without making changes to the underlying PeopleCode or component structure. It’s not the holy grail that solves all your requirements. Using Page and Field Configurator has some limitations:
- You cannot add fields that are not already present on the existing page definition (as in Application Designer)
- You cannot make a required field optional
- Default values work only when adding new data
- In classic pages hidden fields are shown as white space; the page is not adjusted for hidden fields.
Release information
The minimum PeopleTools version required for using Page and Field Configurator is PeopleTools 8.55.
For PeopleSoft FSCM general support is added in image 25. The following extensions were delivered in later images:
- Image 29: Support for Fluid components
- Image 32: Support for Secondary Pages
- Image 35: Support for Field Masking
- Image 36: Field Masking Extended to Lookup Fields
- Image 39: New Advanced Options page
- Image 40: Support for comments, sequence descriptions
- Image 41: Support for system variables
- Image 47: Support for masking custom records on Configurable Search pages
- Image 48: Support for tracking user made changes
- Image 49: Support for Search Pages and Prompts
- Image 52: Support for Change Tracking notifications.
For PeopleSoft HCM general support is added in image 24. The following extensions were delivered in later images:
- Image 28: Support for Fluid components
- Image 31: Support for Secondary Pages
- Image 33: Support for Field Masking
- Image 34: Field Masking Extended to Lookup Fields
- Image 37: New Advanced Options page
- Image 38: Add Support for comments, sequence descriptions
- Image 40: Support for system variables
- Image 48: Support for Search Pages and Prompts
- Image 51: Support for Change Tracking notifications.
Can we help you?
Whether it’s replacing customisations by configuration, isolating them so they don’t impact future updates or removing customisations entirely, Blis Digital can help you make your customisation process as smooth as possible.
Step away from complex and costly PeopleSoft maintenance and upgrades with our demodification services. Or find if you are in control on the level of customisation of your PeopleSoft application with our customisation due diligence quick scans. Feel free to contact us to learn more about our services and how we can help you.