0. Use of PeopleSoft Fluid User Interface and Guided Self-Service
Carrie Jo Howard
System Director
HR Operations and Technology
Dr Prasanna K Menta 
Interim Director - IT
Baylor Scott and White Health
CJ to Introduce Prasanna
Prasanna to introduce CJ then review agenda

1. Agenda Introduction of speakers
Overview of Baylor Scott & White Health (BSWH)
Integration Journey
Project ONE
BSWH Challenges
‘Fluid’ Overview
Demo – Fluid & Guided Self-Service
Lessons Learned
Q & A
Prasanna

2. Baylor Scott & White HealthCJ
Insert Integration video here

3. Baylor Scott & White Health
Insert Integration Video
Integration Video

4. Our Integration Journey
Merger of Baylor Health and Scott & White Health in 2013
Integration
Administrative and clinical systems and processes
Project O.N.E. (Our New Enterprise)
Harmonization of HR and Payroll Services
Creation of a world class HR Service Center
Centralizing all functions in-house from a legacy outsource model CJ

5. Project ONE- Details
Standardization of PeopleSoft HCM 9.2 for core HCM, Benefits Admin, Time and Labor, Absence Management and Payroll for North America
Standardization of Oracle’s HCM cloud for Recruiting, Talent, Compensation, and Learning
PeopleSoft Interaction Hub as the HUB utilizing PeopleSoft Fluid
Implementation of Service Now for Service Management CJ

6. BSWH - Challenges
Employee experiences with portals were not ideal and did not represent a “world class experience”:
Excessive content
Too many technologies causing too many links off the portal
Limited search capabilities
Sub-par appearance
Transactions are not chained together CJ

7. Portal of 9.2 in 2013 (CTX) CJ

8. HRWW Portal NTX CJ

9. Fluid User Interface
Cascading style sheets (CSS), HTML5, and JavaScript
Device-independent
Operation on certified device browsers
Maintained within PeopleSoft Application Designer
Dynamic layout (based upon device used)
Easy interaction using a conventional mouse and keyboard or using a touch interface
Enhanced UX across multiple technologies
Prasanna
Enhanced use of cascading style sheets (CSS3), HTML5, and JavaScript
Pages are device-independent & dynamic
Pages operate on any certified device browser
Maintained within PeopleSoft Application Designer
Apply conditional formatting appropriate to smartphone, tablet, or large-screen devices.
Easy interaction using a conventional mouse and keyboard or using a touch interface.
Ability to provide a singular, and elegant user experience across multiple technology types.

10. Fluid – Laptop or Tablet
Prasanna

11. Fluid – Landscape (Mobile)
Prasanna

12. Fluid – Portrait (Mobile)
Prasanna Note: Buttons contain only images but no text. The grid contains even fewer columns, and the group boxes are aligned one below the other.

13. Fluid – Components
Prasanna

14. Fluid – Components Home Page Global Search
Starting point for Fluid navigation
Multiple home pages (one default)
Role based
Global Search
Global Search (SES)
Indexed
Prasanna

15. Fluid – Components Notifications Actions List
Notifies users of any new actions or alerts
Actions List
Context Action: specific to the current component
System Action: an action that is at the system level and is not related to a component
Prasanna Context Action: specific to the current component
System Action: an action that is at the system level and is not related to a component

16. Fluid – Components Tiles Navigation Bar
Transfer the user to a component
Open Second Level Content
Navigation Bar
Provides handy navigation options such as Recent Places, My Favorites, Navigator (which expands to show the classic menu hierarchy), and Classic Home.
Prasanna

17. Fluid – Implementation & Considerations
Self-Service operations are ideal candidates for fluid deployment
Application usage and processing
Special requirements (spell check, rich text editor, find in for grids, download to excel, modal movement or re-sizing)
Home Page & Tiles
CSS, Java Script & HTML 5 (Caution)
Prasanna

18. Fluid Requirements PeopleTools 8.54 Internet Explorer 11 HCM PUM 9+
Enable fluid mode (System Administrator)
Mobile browser/OS requirements
Technical skills
Prasanna

19. BSWH – People PLACE CJ

20. Preparing the Place CJ

21. BSWH Approach - Fluid Implementation
Formed a User Experience Team
Evaluated current state (classic)
Evaluated future need (classic  Fluid)
Built required Fluid pages
Tested and verified functionality, requirements etc.
Conduct Training (In-Progress)
Implementation of Fluid (In-Progress) CJ

22. Fluid User Interface and Guided Self-Service - DEMO
Shared Demo

23. Lessons Learned Not all components are Fluid
Identify what is required to be Fluid vs. Classic vs. Mobile
Integration with Cloud (for Fluid interface)
Limitations of coexist
REST services - controlled
Recruiting Taleo – utilize existing pagelets
Integration with OBIE/OBIA
8.54 does not support iframe – OBI reports cannot be dynamically displayed in tile
Content Management
Managing content is challenging
Identifying ownership of content is critical
Home pages (limit the number)
A homepage should not have more than 9 tiles for a given user CJ

24. Contact Info
Carrie Jo Howard
System Director, HR Operations & Technology
Baylor Scott & White Healthcare
Mobile:

25. Contact Info
Dr. Prasanna K. Menta
Interim Director
Baylor Scott & White Healthcare
Mobile:

26. References Baylor Scott White & Health
Oracle (2015). Fluid Navigation Standards, retrieved from
Oracle (2015). Understanding the Characteristics of Fluid Applications, retrieved from

27. Questions?