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

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

Baylor Scott & White Health CJ Insert Integration video here

Baylor Scott & White Health Insert Integration Video Integration Video

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

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

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

Portal of 9.2 in 2013 (CTX) CJ

HRWW Portal NTX CJ

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.

Fluid – Laptop or Tablet Prasanna

Fluid – Landscape (Mobile) Prasanna

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.

Fluid – Components Prasanna

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

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

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

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

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

BSWH – People PLACE CJ

Preparing the Place https://vimeo.com/138798264 CJ

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

Fluid User Interface and Guided Self-Service - DEMO Shared Demo https://epdev.swt.mycmsc.com/psp/swtepts2/?cmd=login&languageCd=ENG&

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

Contact Info Carrie Jo Howard System Director, HR Operations & Technology Baylor Scott & White Healthcare Mobile: 254-534-0096 E-mail: cjhoward@sw.org https://www.linkedin.com/in/carriejohoward

Contact Info Dr. Prasanna K. Menta Interim Director Baylor Scott & White Healthcare Mobile: 240-441-6656 E-mail: pmenta@sw.org https://www.linkedin.com/pub/dr-prasanna-k-menta-dm-pmp/4/b57/472

References Baylor Scott White & Health Oracle (2015). Fluid Navigation Standards, retrieved from https://docs.oracle.com Oracle (2015). Understanding the Characteristics of Fluid Applications, retrieved from https://docs.oracle.com

Questions?