PeopleSoft Technology Blog
Customers and partners have asked us for guidelines and standards for developing with PeopleSoft's Fluid UI. To support that, we've just posted the PeopleSoft Fluid User Interface CSS Guide on the FLUID UI: PeopleSoft Fluid User Interface Documentation Updates page on My Oracle Support (Doc ID 1909955.1). This guide contains descriptions of CSS styles that PeopleSoft delivers. You'll find this information helpful for creating custom Fluid applications as well as extending current CSS features delivered in your PeopleSoft applications. The document provides descriptions of nearly a thousand CSS styles delivered with PeopleTools 8.54. The styles are divided in these categories:
- PeopleTools System Default CSS Styles: These styles are used to control basic elements of the fluid infrastructure provided by PeopleTools, such as the NavBar, the fluid banner, homepages, tiles and so on.
- Application Content CSS Styles: These styles are used to control application content deployed in fluid mode.
Creating fluid applications relies heavily on CSS 3.0 for the look, feel, and layout of the runtime application. If you intend to customize or create any fluid application, expert knowledge off CSS is required. Prior to working doing any fluid style development work, make sure you are familiar with the documentation provided in PeopleSoft PeopleTools 8.54: Fluid User Interface Developer’s Guide, “Adding Page Controls,” Applying Styles.Refer to the FLUID UI: PeopleSoft Fluid User Interface Documentation Updates MOS page to receive important information about the PeopleSoft Fluid User Interface.
Questions often arise on the PeopleTools versions for which Critical Patch Updates have been published, or if a particular PeopleTools version is supported.
The attached page shows the patch number for PeopleTools versions associated with a particular CPU publication. This information will help you decide which CPU to apply and when to consider upgrading to a more current release.
The link in "CPU Date" goes to the landing page for CPU advisories, the link in the individual date, e.g. Apr-10, goes to the advisory for that date.
The page also shows the CVE's addressed in the CPU, a synopsis of the issue and the Common Vulnerability Scoring System (CVSS) value.
To find more details on any CVE, simply replace the CVE number in the sample URL below.
Common Vulnerability Scoring System Version 2 Calculator
This page shows the components of the CVSS score
Example CVSS response policy http://www.first.org/_assets/cvss/cvss-based-patch-policy.pdf
All the details in this page are available on My Oracle Support and public sites.
The RED column indicates the last patch for a PeopleTools version and effectively the last support date for that version.
Applications Unlimited support does NOT apply to PeopleTools versions.
Many customers contact us for information on best practices for deploying the Secure Enterprise Search-based global search in PeopleSoft. To assist with this, we've created a Knowledge Document in My Oracle Support that contains lots of useful information. This document has links to the following subjects and more:
- How to implement High Availability
- PeopleTools Online help for Search
- Reference material like the Administrator's guide and the Installation guide
- Performance guidelines
The PeopleSoft Interaction Hub has been on the continuous release model for some time. Now, we're taking the next step and moving the Hub to the Selective Adoption model. All PeopleSoft applications have gone to Selective Adoption, and soon Interaction Hub customers will be able to take advantage of the this breakthrough release process and all the tools--like PeopleSoft Update Manager--that make it so powerful.
There is a paper on My Oracle Support that describes how customers should prepare for the move to Selective Adoption. Go to the PeopleSoft Update Manager home page on MOS, then select the PeopleSoft Update Image Home Pages tab, and choose the Interaction Hub Update Image Page. That page contains a link to a white paper that explains what customers need to do to get ready for using the PeopleSoft Update Manager and the Selective Adoption Process. This page is also where Interaction Hub update images will be posted when they become available.
Why are we doing this? The Selective Adoption process provides many benefits to customers. This new process streamlines the maintenance and update process and employs virtualization and the latest PeopleSoft lifecycle tools to make the process faster, cheaper, and more efficient.
- Updates are quicker, less expensive
- Business lines benefit from the latest functionality resulting in higher ROI
- Enhancements are delivered regularly, new business value provided incrementally, no long waits for enhancements
- Eliminate major upgrades
- Can be done on your schedule
- Can retain strategic customizations
PeopleSoft just published a new Red-Paper that describes how to convert an existing Classic Component to a new Fluid UI Component. It's a great resource for anyone that is interested in learning more about Fluid UI and the steps required to move a Pixel-Perfect Component to a new responsive Fluid UI Component.
The Red-Paper is called Converting Classic PIA Components to PeopleSoft Fluid User Interface. You can find it on My Oracle Support, document Id 1984833.1
There are a few things I want to point out that are in the document.
- It gives great instruction with an example of how to convert a Component to Fluid UI.
- There is a very important section on classic controls that are not supported in Fluid UI, or require some type of conversion. I can't stress how important that is.
- There is an appendix that identifies the delivered PeopleSoft style classes. You'll find that appendix extremely valuable when you're looking for the right style to get the UI you want.
Of course converting an existing component is only one way to take advantage of the new Fluid UI. Refactoring existing components to optimize them for the different form factors, or building components are certainly possible. In many cases, developers want to leverage existing components to take advantage of tried and tested business logic.