X

An Oracle blog about PeopleSoft Technology

Top 3 Enhancements to the Page and Configurator

Guest Author
This is a syndicated post, view the original post here

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 lower-level fields including fields at level one.
  2. Extending PFC to field change events meaning page displays can change as the user enters data on the page.
  3. Streamlined selection of fields for complex components.

 

1. Extending Field-Based Criteria to Level 1 Fields

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

Select field

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.

Component record field

 

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. 

advanced options

Here’s how it could work for you:

  1. The functional user describes the use case to the technical resource including what they’d like to change and what to use as criteria.
  2. The technical resource uses the Advanced Options tab to locate the specific fields of interest and selects to ‘Include in the Criteria List’ and/or ‘Include in the Field List’.  This is a one-time action.
  3. The functional user completes the configuration and selects the ‘Restricted to fields from Advanced Options’ option when adding criteria or fields for configuration.  Only the fields selected on the Advanced Options tab are displayed eliminating time searching through long lists of fields in the prompt.  The functional user continues to maintain the configuration, adding sequences and adjusting criteria as required. 

select fieldThis 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.

 

Additional Features

  • New option to ‘Set a Field Value to Blank’.  If a field is hidden or display only it can also be set to blank ensuring no value is saved in the database.   
  • Data masking.  In addition to masking sensitive and personal information consider using PFC to mask bank account and supplier pricing information in Financials based on role.
  • Applying Sequences Additively allows multiple configuration sequences to impact the page displayed.  This is required to apply data masking configurations ‘in addition to’ standard configurations.  You may also want to use the Apply Additively selection when you have many sequences, all with unique, mutually exclusive criteria and additional sequences with less criteria that should also take effect.  As an example, there may be fields on a page that are never used.  These fields could be hidden using a separate sequence with the Apply Additively option selected.  This sequence would always be evaluated and if criteria is met, would change the page displayed in addition to changes from another sequence where more specific criteria is used.

 

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.

 

Joe Willever This blog post has been authored by Joe Willever, Product  Management Director at Oracle.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.