An Oracle blog about PeopleSoft Technology

Fluid Header and Navigation is the New Standard

Matthew Haavisto
Product Management Director
Beginning with PeopleTools 8.55, PeopleSoft 9.2 applications will have a Fluid header on their classic pages that matches the fluid pages.  This unifies the user experience of classic pages with newer fluid pages and applications.  With the fluid user interface, user navigation is more seamless and intuitive.  Using fluid homepages, tiles, global search, related actions, and the new fluid Navigation Collection feature, users can more easily navigate to the information most important to them.  Refer to the PeopleSoft Fluid User Interface and Navigation Standards White Paper (Document ID 2063602.1) for more information on design best practices for navigation within PeopleSoft applications.
Part of this change that makes Fluid the default is the replacement of the drop down menu navigation.  In most cases, customers will want their users to simply use the Nav Bar in place of any classic menu navigation.  However, if there is a special circumstance where customers want to maintain the classic menus, they can do so.  There are two ways of displaying the classic menus:

 Method 1 – Switch back to default tangerine or Alt-Tang theme

1. Go to PeopleTools >> Portal >> Branding >> Branding System Options;
2. Change the system default theme back to default tangerine or alt-tang;
3. Sign out and sign in again to see the changes.


Method 2 – Unhide the drop down menu in default fluid theme

1. Go to PeopleTools >> Portal >> Branding >> Define Headers and Footers;
2. Search and open the DEFAULT_HEADER_FLUID header definition;
3. Copy the following styles into the “Style Definitions” field at bottom of the page, and then save;
.desktopFluidHdr .ptdropdownmenu {
    display: block;

4. Sign out and sign in again to see the changes.

We encourage customers to stick with Fluid navigation as the standard.  It's simply better and more intuitive. 

Join the discussion

Comments ( 24 )
  • guest Thursday, February 25, 2016

    Fluid makes sense for self-service but not for people who use PeopleSoft for their job. The menu bread crumbs make trying to duplicate a problem much simpler.

  • guest Thursday, February 25, 2016

    Fluid means more than just mobile and self-service use. We are refactoring navigation entirely. The bread crumbs and cascading menus were cumbersome, and although they could be used effectively, there are better ways of navigating now, but it takes thinking differently. For example, apps are building more role-based home pages so that the components one needs are at one's finger tips. Fluid nav collections, search, and other mechanisms make navigation easier, but it requires a different mind set.

  • Sasank Wednesday, March 2, 2016

    Thanks for sharing Matthew. This is very useful.

  • Dan Thursday, March 24, 2016

    Is there a way in 8.55 Tools to default a user's home page (classic default vs fluid default) by controlling which fluid roles they are granted? Wasn't that the original intent of allowing two different start pages ('page' and 'fluid home page' start pages) in the web profile configuration? I believe that is how it worked with 8.54. We are rolling out the fluid interface to a pilot group before the rest of our company. We need to be able to direct some users directly to fluid, and others to classic.

  • steve Wednesday, March 30, 2016

    I wonder if anyone has done any usability studies using the Fluid navigation with the New Window option. The Fluid navigation pretty much breaks the New Window feature, which is a real killer to power users that are moving around with multiple windows open. This is really easy to demonstrate. I'll provide a procurement example, but this works for any New Window link

    -Be in the Add/Update Purchase Orders component and do some work

    -Hit the New Window link and then try to navigate to Add/Update Receipts. You pretty much have to go back to the home page since you don't have breadcrumbs.

    -Now do dome work on the Receipts page.

    -Now go pack to your PO page and try to do something. You'll get an error.

    The reason for this is that there has been an issue with the New Window link ever since 8.0. When you pop a new window, the URL gets a suffix added into it. This is how your browser keeps the two windows separated while sharing the cookie. But, if you hit the Home icon in the new window, the suffix is lost. So, when you start jumping back and forth between windows, your browser cannot keep it straight as the cookie is being shared and you end up with getting "page no longer available" or being kicked into a page that mirrors the one that was in your first window.

  • Matthew Friday, April 1, 2016

    Steve: Thank you for your comment. Can you open a bug for this? We don't have New Window in Fluid, but we will work on a way to rectify this issue. You make a good point.

  • guest Thursday, May 26, 2016

    It appears the PeopleSoft development is following the way of Fusion development, where they enforce what customers can see, and not driven by customer's needs. While Fluid works for Self Service, unless and until all the pages/components are converted to Fluid screens, trying to take out the Classic Menu style doesn't help. Similarly, as it is called out by Steve above, the New Window feature is a must. I have seen Oracle EBS and Fusion lacking that, and now PeopleSoft joins that bandwagon!

    Change is always good, but that change needs to be good enough to justify the learning and the need for adopting that change.

  • Matthew Thursday, May 26, 2016

    Keep in mind that users can still access all the menus that they could previously by using the navigator (in the nav bar). However, we don't think this is the most efficient way to go. We'd rather see users employing role-based home pages, workcenters, and activity guides to present the content that users need and want. Also, keep in mind that Fluid home pages are highly personalizable by users, so they can put the content on their pages that they need most.

  • guest Tuesday, August 2, 2016

    Has anyone at Oracle actually performed usability tests for Fluid beyond Self-Service? The loss of breadcrumbs and a persistent left navigation menu bar hurt the usability of the product for the vast majority of the actual functional, back-office users. Remember that these are the people who control whether or not the system is accepted and successful at a client. Especially when you are trying to sell to sell products such as Financials that are primarily NOT self-service oriented.

    Selling such organizations on the Fluid strategy is impossible because it is a huge step backwards in their minds. Try thinking first, then designing and selling. One of the most promising features in Fluid (so called active tiles that are more than just large Favorites links) are mostly not even present.

    At least remove the final two sentences in this article, "We encourage customers to stick with Fluid navigation as the standard. It's simply better and more intuitive." It's insulting to long time PeopleSoft users.

  • guest Wednesday, August 3, 2016

    We have done usability testing. We understand the difference between self-service and power users. That is why 8.54 was primarily geared to SS. In 8.55 we introduced several features to improve nav for power users. It is a different mind set though, and I understand that significant change can be difficult especially when one has been used to a particular way for a long time. For power users we expect more people to use Workcenters and other role-based pages that bring the needed nav elements to the fore. It is also easy to do extensive personalization which enables users to create home pages with the things they want on them. There is also related content, related actions, etc.

    Our apps teams are delivering more Fluid content designed for power users too.

    You may want to check this out: http://docs.oracle.com/cd/E65859_01/fluid_ux/index.html

  • Matthew Thursday, August 4, 2016

    By the way, I don't mean to diminish your complaint. It is absolutely legitimate. In addition to the Tools mechanisms I've mentioned, our applications teams are working hard to improve the UI for power users/back office processes. You'll see a lot more out of the box in upcoming PIs that we believe will improve things for these user communities.

  • Matthew Wednesday, August 17, 2016

    Steve: Please contact me at matthew.haavisto@oracle.com. I have some information that may address the issue you raised. I don't know if there is an SR for it.

  • Tom Friday, August 26, 2016

    Like most things, these changes will have benefits and issues. The benefits are always made clear by the vendor but, for obvious reasons, they are reluctant to state the issues you might/will encounter.

    When the navigation becomes fully customizable and personalized, it becomes very problematic to produce training media that shows the navigation to novice users and makes it harder to support when issues occur for the user. I'll reserve judgment until we upgrade later this year.

  • Matthew Monday, August 29, 2016

    Our objective is to make things intuitive enough that users won't need much training. For example, if an Employee Home page is deployed to me, I should be able to easily deduce what to do from the tiles on them. If I personalize it by adding a tile that I use frequently (but that wasn't delivered), I should know what to do with that tile/component. Similarly, with WorkCenters and guided processes, everything the user needs to complete a process is right there for them. Everyone knows how to use Search, I hope.

  • guest Tuesday, August 30, 2016

    Thanks for the informative blog Matthew on disabling fluid. Any idea how to disable fluid header on the global search results page?

    We have enabled SES and disabled fluid, but the global search results always open in fluid with Navbar etc. This is inconsistent with the rest of the classic application...

  • guest Thursday, December 22, 2016

    Matthew, this (mostly) works. Thanks. However, we are noticing that on the first navigation to a classic page, we don't see any of the breadcrumbs between "main menu" and the page being navigated to. But then on the second and all subsequent navigations all of the breadcrumbs display as one would expect. This happens with both method 1 and with method 2. We are on PT 8.55.11. Does Oracle have a solution for this?

  • Matthew Monday, January 9, 2017

    Re: Guest Post on 12/22--

    Have you submitted an SR on this? It appears to be a bug. We'll need an SR to address it properly.

  • Christopher Cavett Tuesday, January 10, 2017

    Thanks, Matthew.

    An SR has been opened, SR 3-14012601171 : Incomplete Breadcrumbs on first classic navigation - PeopleTools 8.55.11.

  • Owen Thursday, February 16, 2017

    While fluid navigation does have some benefits, I think there is one shortfall that affects support staff. In classic navigation, the breadcrumbs made is very easy for support staff to identify where and how an end-user navigated to the page that they are having an issue with (by way of screenshot). With fluid navigation, there is no frame of reference as to how the end-user got to where they are in the system (without them specifically providing those details, or having to ask them).

    The style sheet "hack" given in method 2 does allow breadcrumbs to be displayed again, but it looks very clunky. Perhaps a compromise could be found where breadcrumbs could be displayed (in a more fluid style) without needing to enable the old classic drop-down menu navigation?

  • Sheri Sheeks Wednesday, August 2, 2017
    Is classic navigation be deprecated in 8.56?
  • Matthew Wednesday, August 2, 2017
    Classic is not deprecated, but all our development is for Fluid, so all new features will be Fluid. Both Classic and Fluid pages can be used within the Fluid navigation paradigm, and we advocate customers move to that. Fluid can still be disabled, but we don't recommend that. It's a dead end.
  • guest Monday, August 7, 2017
    What's the best way to enable breadcrumbs in the 9.2 environment? We experience issues with bundles and would like to circumvent this problem while providing users with the navigation when it's needed.
  • Matthew Monday, August 7, 2017
    Breadcrumbs and cascading menus are not used in Fluid navigation. No contemporary UIs use breadcrumbs any longer. We suggest taking advantage of the many UI features in Fluid that streamline navigation. In particular, look at the Navigation Standards:

    and UX Guidelines:
  • Kevin Monday, November 5, 2018
    Is this a "customization" or "configuration"? Is it possible that it would get lost with an upgrade? It looks like a configuration.
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.