The document discusses options for using the Fluid user interface in PeopleSoft. It begins by explaining what Fluid is and its benefits for usability and intuitive navigation. It then covers decisions around using Fluid such as profiling users and devices. Several design patterns are presented for integrating Fluid and classic interfaces. Examples from organizations that have implemented Fluid are also reviewed. The document aims to help customers determine the best approach for adopting Fluid.

1. PeopleSoft UI: Fluid, Classic, or
Both? A Decision for Every
Customer - CON2848
Graham Smith

2. About Cedar
 Oracle Implementation House
 PeopleSoft, HCM Cloud and Taleo Experts
 Support, Managed Services, Hosting Centre
 Around 70 consultants with Offices in UK,
Switzerland, India and Australia
 15 Upgrades to PeopleSoft 9.2 completed

4. Who am I ? – Graham Smith
Lead Consultant at Cedar Consulting
Oracle ACE Director
Chair of the PeopleTools SIG at UK
Oracle User Group
7th year presenting at Oracle OpenWorld
http://i-like-trains.blogspot.co.uk

5. Agenda
 Fluid: What’s it all about?
 User and Device Profiling
 Decisions and Design
Patterns
 Implementation

6. Fluid: What’s it all about?

7. Fluid: What’s it all about?
 Why?
 Application usability
 More intuitive & easier to
use
“Fluid represents PeopleSoft’s
strategic direction for delivering
a robust and intuitive, yet
familiar, experience for your
application users.”
“A new paradigm and model”
“not just a new user interface”
“direction of all future PS
development”

8. Fluid Technology
 Designed for mobile devices
 Screen size aware
 Responsive
 Auto adjusts visible fields
 Supports native device controls
 Appropriate for desktop devices
 Good for simple transactions

9. Useful References & Guides
 FLUID UI: PeopleSoft
Fluid User Interface
Documentation Updates
(Doc ID 1909955.1)
 Converting Classic PIA
Components to PeopleSoft
Fluid User Interface
(Doc ID 1984833.1)
 PeopleSoft Fluid
Navigation Standards
White Paper (Doc ID

10. PeopleSoft Spotlight Series

11. Need access to PeopleSoft Fluid?
 PeopleSoft Image Hosting from Cedar
 http://www.cedarconsulting.co.uk
 Your own HCM, FSCM, ELM, CRM or IH PeopleSoft
Image
 Use it for exploring Fluid
 Experimental / Prototype Development
 Selective Adoption Packing of Updates to 9.2
from
$420
per month

12. What do you get with Fluid UI ?
1.PeopleTools Fluid UI development tools
2.Fluid Helper Tools
3.Fluid Components (or Apps)

13. Fluid Page Layouts (Templates)

14. Application Start Pages

15. Homepages and Tiles
 Recommend no more
than 9 tiles per
Homepage
 No more than 5
Homepages
 Bring key
information onto
the Tile itself
 Easy to think of
these as replacing
Pagelets but they

16. What do you get – Some Fluid Helper
Tools
 Fluid Landing Page
 Homepages
 Tiles
 Fluid Search Results
 Notifications (Actually MAP not Fluid)
 replaces Worklist and is now cross system
 Pivot Grids
 Activity Guides (coming in 8.55)
 Navigation Collections (coming in 8.55)
 Unified header branding (coming in 8.55)

17. User and Device Profiling

18. User and Device Profiling
1.People and their Roles
 Self service
 Executive
 Power
2.Devices they may use
 Phone
 Tablet
 Desktop/Laptop

19. Profile Users by Device
Tablets
PCs
Smart
Phones
Desktop Browsers:
• Google Chrome
• Internet Explorer
• Mozilla FireFox
• Apple Safari
• *Dolphin
• *Opera
• *Microsoft Edge
*Not certified
Mobile Browsers:
• Google Chrome
• Apple Safari
• *23+ others
*Not certified

20. Profile Users by Application Type
Tablet
Users
Desk
Based
Users
Smart
Phone
Users
Executive
Power
Self
Service

21. Decisions and Design
Patterns

22. What are the decisions to be made
Use Fluid
(Y / N) ?
Fluid
Homepage
& Portal ?
Fluid or
Classic Apps
“direction of all future PS
development”

23. Classic Interface
Source: Wiktionary.org
Classic Portal Classic Component

24. Use Fluid (Y/N) ?
 Do you need PeopleSoft on mobile device ?
 Either now or in the future?
 Do you want a Cleaner, Simpler user interface
for Self Service and Executive users?
 Do you want to take advantage of new
features?
Use Fluid
(Y / N) ?

25. Landing Page or PeopleSoft Portal?
 Fluid Homepages designed for mobile devices
 Works well on desktops too
Fluid Homepage
• Tiles limited v Pagelets
• No Wizard
• Simple UI
• Great on mobile
Classic Portal
• Pagelets Rich content
• Pagelet Wizard
• Can look cluttered
• Limited on mobile
Fluid
Homepage
& Portal ?

26. Windows and Fluid

27. Header Branding - Fluid and Classic

28. Header Branding - Fluid and Classic

29. Changing the Header
 PeopleTools > Portal > Branding > Define
Headers and Footers

30. The User Experience

43. Classic comp

46. Design Patterns

47. Design Pattern #1– Classic Portal
 Classic design
using available
technology prior to
PeopleTools 8.54
 Good for desktop
users
 Bad for mobile
users
 Functionally rich,
familiar Clasic
portal framework
Login
Classic
Portal
Classic
Component
Classic
WorkCentre

48. Design Pattern #2– Classic Portal
with Fluid Apps
 Good for both
desktop & mobile
users
 Avoid Portal for
mobile users using
bookmark direct to
Fluid components
 Great introduction
to Fluid
 No Fluid Homepage to
maintain
Login
Classic
Portal
Classic
Component
Classic
WorkCentre
Fluid
Component
Mobile
Bookmark

49. Design Pattern #3 – Only Fluid
 Good for all devices –
mobile & desktop
 Limited breadth of
Fluid apps
 Included for
completeness
Login
Fluid
Homepage
Fluid
Component

50. Design Pattern #4 Fluid Home - Classic
& Fluid Apps
 No classic portal
 Tidy clean and
simple
 All users get same
login and
navigation
experience
 Less functionality
compare to Portal
 But can replace with
WorkCentres
Login
Classic
Component
Classic
WorkCentre
Fluid
Component
Fluid
Homepage

51. Design Pattern #5– Classic Only or
Fluid Only
Login
Fluid
Component
Fluid
Homepage
Classic
Portal
 Single point of
login
 Drive UI on who
you are, what
you’re doing or
what device
 Could be
confusing
 Clear divide
between mobile
and desktop
Classic
Component
Classic
WorkCentre
?

52. Design Pattern #6– Both Homepage and
Portal
 Some Classic
acceptable
on Mobile
device
 Complex to
administer
 Best of all
worlds
Mobile
Login
Classic
Component
Classic
WorkCentre
Fluid
Component
Classic
Portal
Desktop
Login
Fluid
Homepage
Classic
WorkCentre

53. Real World Examples

54. Fluid Example from Oxfam GB
 Great example of Design Pattern #4
 Built by the amazing PeopleSoft Team at Oxfam
 (Not built by Cedar Consulting)
 Introduced as part of a HR 9.0 to 9.2 Upgrade
Project

55. Fluid UI @
 Exclusively Fluid Homepage
 Regardless of user device
 Even if users don’t use Fluid Apps
 Use Fluid apps where delivered
 Convert custom self service into
Fluid

56. Homepage for most users

57. Homepage for Power Users

58. Spire Healthcare PeopleSoft Fluid
Recruitment
 UK’s 2nd
largest
provider of
private
healthcare
 Job site
built around
Classic
Candidate
Gateway
 Cedar built

59. Design Pattern #2 – Classic Portal
with Fluid Apps
Guest Login

60. Desktop BrowserCell Phone

61. Desktop BrowserCell Phone

62. Rotate Cell PhoneCell Phone

64. One strategy for converting to Fluid
• Record
• Record
• Record
• Record
• Record
• Record
C 1 C 2 C 3 F 4 F 5 F 6
1) Create new Fluid pages
C 4 C 5 C 6
2) Rename original pages
F 1 F 2 F 3 3) Rename Fluid to original names
Component

65. In Conclusion
 Understand what you have with Fluid
 Profile your users and devices – look to the
future
 Decide Classic or Fluid ?
 Classic Portal and/or Fluid Landing page
 Classic Apps and/or Fluid Apps
 Choose a design that suits your profile and
infrastructure
 Pilot some Fluid Apps in low risk area

66. New PeopleTools Book!
 Fluid UI
 MAP
 REST and
Documents
 jQuery Mobile
 AngularJS
 Cordova
 Android
 Oracle Mobile
Application
Jim & Sarah Marion

67. Who is Jeffrey?

68. Any Questions or Observations?
http://i-like-trains.blogspot.co.uk
graham.smith@cedarconsulting.c
o.uk