The latest enhancements to the Page and Field Configurator (PFC) expand the potential usage on pages significantly in addition to improvements in the user interface for the Page and Field Configurator administrators. We found these three capabilities most compelling:
1. Extending Field-Based Criteria to Level 1 FieldsSince the beginning, customers have used PFC to display a page differently based on criteria. You can have multiple sequences for a component, each with its own unique criteria and changes to the display. Up until now, the fields available as criteria were limited to those at ‘level zero’ which are higher-level fields and not always practical for use as criteria, especially in many of the core pages in HCM.
We extended the fields available to use as criteria to include those at ‘level one’. The example below shows the prompt for criteria on the job data component including Action and Action Reason codes. Hide fields, make a field required, display only, or change a label using the fields at level one as criteria.
The extension to include level one fields as criteria leads directly into the next item on the list of enhancements – creating field change events in the Page and Field Configurator.
2. Extending PFC to Create Field Change Events
Now that we can include level one fields as criteria, it’s important that we extend PFC to trigger page changes as the user updates fields on the page. In the latest release, all fields used as criteria will include a field change event in event mapping. As the user updates the page, if the field being changed is used as criteria, PFC will trigger, criteria will be evaluated and if met, the page display will change. This includes both level one fields and level zero fields which you may already have as criteria.
The field change events are created in event mapping when you Apply Configuration, meaning it’s important that you select the Apply Configuration anytime you make changes to criteria. Here is what the event mapping component looks like with field change events populated from PFC.
3. Streamlined Selection of Fields
Who in your organization maintains Page and Field Configurator? Is it limited to technical resources or do functional users maintain the configurations? We have found customers are split on this. If your functional users are overwhelmed by the list of fields to choose from, a new Advanced Options tab can help make the selection easier.
Here’s how it could work for you:
This is optional functionality created to help filter the list of fields in prompts, modeled after the PFC data masking functionality to limit selections in the prompts to the data privacy framework. Leave the option unselected to view the complete list of fields. We envision this being helpful on large complex components with a large number of fields. This could also provide your technical resources input on the fields being selected and through standard security, functional administrators could be given read-only access to the Advanced Options tab if required.
For more information
Isolating and eliminating customizations using tools such as the Page and Field Configurator continues as a high priority for customers. You can find additional documentation on the Page and Field Configurator using the PeopleSoft Online Help for Enterprise Components.
This blog post has been authored by Joe Willever, Product Management Director at Oracle.