Presentation is loading. Please wait.

Presentation is loading. Please wait.

Cut Through the Fog to Create a Golden User Experience with PeopleSoft Interaction Hub Session #CON2232 October 1, 2014.

Similar presentations

Presentation on theme: "Cut Through the Fog to Create a Golden User Experience with PeopleSoft Interaction Hub Session #CON2232 October 1, 2014."— Presentation transcript:

1 Cut Through the Fog to Create a Golden User Experience with PeopleSoft Interaction Hub
Session #CON2232 October 1, 2014

2 Your Presenters Kristin McLean Senior Business Analyst
Northwestern University 10 years PeopleSoft experience

3 Agenda/Contents Business Case for Implementing Interaction Hub
Evolution of the Interface Demo of Current Interface Future Enhancements Critical Success Factors Questions

4 Northwestern University
Active Users Faculty Staff Temporaries Retirees Affiliates Initial PeopleSoft Implementation December 1996 Interaction Hub / HCM Version – 9.1 Interaction Hub v.1 implemented August 2012 Interaction Hub v.2 implemented October 2013 Interaction Hub Tools Version – 8.52* HCM Tools Version – 8.51 *Installed the latest version of Interaction Hub in preparation of a future HCM upgrade *Ensured compatibility between two different tools versions

5 Interaction Hub

6 Business Case PROVIDE Users with a rich, contemporary, intuitive user experience A summary page that puts critical information where users need it most A collaborative workspace to blend business processes across HCM pages CATALYST Need to complete or manage training and disclosure of financial interests for research: sponsored by federal agencies sponsors adopting Public Health Services regulations research involving human subjects

7 Evolution of the Interface
Guest Sign In / Authentication Page

8 Evolution of the Interface
From PeopleSoft Menu to Interaction Hub v.1

9 Evolution of the Interface
From Interaction Hub v.1 to v.2 From: “creating great UI-Alliance -2012”

10 Demo of Current Interface
Accordions Links / Hover Over Verbiage Modal Windows Direct Login Security

11 Accordions Expand / Collapse to display links for reviewing and updating Self-Service information

12 Links / Hover Over Verbiage
Clicking links allow users to open up a modal window to access a Self Service page, role or internal/external website Inserting hover over verbiage on the link name describes the navigation destination and what actions can be taken

13 Links / Hover Over Verbiage

14 Modal Windows Clicking a link within an accordion opens a modal window displaying a Self-Service page

15 Direct Login Upon authentication, displays a Self Service page or role without navigating through the Interaction Hub Required A new PIA with a unique naming convention Separate site from the Guest / Sign In page, with a different set of cache A user is on the Interaction Hub web server but is not signed in yet Once the user authenticates through LDAP, the User Profile in Interaction Hub determines the access A URL Definition Table that goes to the site name Append the menu and component to the URL

16 Direct Login Page Example

17 Direct Login Role Example

18 Security Roles Security is roles-based
All users granted Guest Login role when they land on the Sign In page (NW_PA_WEB) Allows users to see “basic” functionality, regardless of the users’ Self-Service role in HCM

19 Security *Determine which roles are tied to a JOB Role Mapping
Upon login User Profiles are created Users granted roles based on a mapping from HCM* Roles are associated with Content References vs. pages. For example Accordions / Pagelets Links News articles There can be a 1 to many relationship between Interaction Hub and HCM roles Portal roles contain a roll up all HCM roles associated with the links within the Accordion, Pagelet or Link Users must have access to at least one security role within an accordion or pagelet that is not “Public” to view it Dynamic queries tied to dynamic roles sync Interaction Hub with HCM every 30 minutes using a database link and view *Determine which roles are tied to a JOB

20 Security Role Mapping Crosswalk Example

21 Security Role Mapping Example in Interaction Hub

22 Future Enhancements Portals Applicant / Onboarding
Office of the Provost VPHR Administrator Manager Recruiter Help Desk Benefits Payroll Course Administrator

23 Critical Success Factors
Define User Requirements Identify supported browsers Determine timelines for University-wide rollouts of new versions IE7 was not compatible with the Interaction Hub design due to the number of places where external content and libraries are loaded Included an “if” statement to change the EDGE code for IE10 because not compatible with the accordion design Identify browser behavior Directing users to a new browser window or tab in the current browser when clicking links to external URLs Display / size of the modal windows Mobile device limitations Expanding / scrolling through modal windows Uploading PDFs

24 Critical Success Factors
Define User Requirements – cont’d Turn off pop up blockers Add Interaction Hub URL to trusted sites Assess firewall constraints with non standard ports* Determine impacts of shared cookies on user experience and connectivity to the Interaction Hub** *With the initial implementation, the Interaction Hub was connected to HCM from a non standard port using an existing VIP, because there were not enough virtual licenses. Departments or internet providers could potentially block the port. Users can still see data that is pre-loaded on the landing pages because the connection is going through the SNAT on the portal server. However, when the user licks a link to an HCM page, the connection is launched from the user’s desktop **Example of cookies impacts User already signed in with their Admin ID in another browser when authenticated through Interaction Hub for Self Service received “UserID and/or password is invalid” error. Considered applying javascript to invalidate the Guest token, but implementing the solution would prevent a user from toggling or opening a new window in Interaction Hub

25 Critical Success Factors
Design Requirements To ensure images display appropriately: Store images in the application vs. the web server* Ensure images have the same file name and extension between the HCM definition and the actual image Determine user experience navigating from unsecure to secure URLs within Interaction Hub** Ensure system generated URLs direct the user to the appropriate system to complete workflow tasks Engage a web designer with javascript and jquery experience *Otherwise, jquery files will need to be on each web server for each database and pointed to the appropriate web server for each database. All servers will need to be in the SNAT (Secure Network Address Translation) to ensure the same cookie is being used in the call from Interaction Hub to HRMS and back **User may receive security warnings depending on the browser security levels

26 Critical Success Factors
Design Requirements – cont’d Consider ADA requirements Partner with the Office of Web Communications and EEO Leverage “Web Accessibility in Mind” website: Leverage screen reader / low vision tools Leverage Accessibility Inspector Extension for Firebug* Participate in courses / seminars through Job Accommodation Network and the Illinois Center for Information Technology and Web Accessibility *Helps verify the use of the iCITA HTML Accessibility Best Practices techniques to implement the requirements of the Section 508 and W3C Web Content Accessibility Guidelines. This development is led by Dr. Jon Gunderson, Coordinator of Assistive Communication and Information Technology Accessibility in the Division of Disability Resources and Education Services (DRES) at the University of Illinois in Champaign/Urbana, Illinois

27 Critical Success Factors
Security Considerations Configuration Configure the timeout warning and timeout to be 1 minute later than in HCM Ensure the Node Name for any HCM pages that open within the Interaction Hub are set to “HRMS” in the Content Reference instead of “LOCAL_NODE” to prevent authorization errors Configure the NAVSTACK=Clear parameter on HCM pages to prevent users from navigating to previously accessed pages within Interaction Hub and remain in Interaction Hub wrapper* Ensure security is added to CREFs in both HCM and Interaction Hub *Ensure user stays within Interaction Hub

28 Critical Success Factors
Security Considerations At go-live Implemented a one-time process to create User Profiles in HCM for active users who had never signed into Self- Service before Developed a process to create User Profiles and grant appropriate Self-Service roles proactively as LDAP communicates NetID for new hires and rehires vs. at login

29 Critical Success Factors
Security Considerations - cont’d Maintenance Perform regular clean-up effort to ensure active users maintain a User Profile in both HCM and Interaction Hub associated with an EmplID If a page is hidden in HCM, security must also be removed on the Interaction Hub– otherwise, the link to the page will still be active but the user will receive authorization errors when the link is clicked Interaction Hub roles are not synced with HCM roles. If a role needs to be issued, it must be entered in both HCM and Interaction Hub manually or manually in HCM and through the dynamic query process in Interaction Hub If a role is issued dynamically in HCM while the user is in Interaction Hub, users will need to wait for the dynamic query process to run to be issued the appropriate access in Interaction Hub if the access is tied to a new accordion/pagelet/link

30 Critical Success Factors
Security Considerations – Cont’d Lock Out Users for Testing Tax Update / Minor System Maintenance Change the Web Library Permission to “No Access” to remove the Login pagelet from the Sign In Page Post message regarding Current System Status NOTE: Users with access to a “Direct Login” link can still access Self Service by navigating to the Home page Testing team can use the “Direct Login” URL

31 Critical Success Factors
Security Considerations – Cont’d Lock Out Users for Testing Major Upgrade / System Maintenance Cancel the dynamic role process Delete all the dynamic role assignments to remove non-public accordions / pagelets, preventing users from accessing Self-Service functionality from a “Direct Login” link Remove Roles from non-public accordions Grant PS_ADMIIN role to testing team

32 Critical Success Factors
Security Considerations – cont’d Testing Major Upgrade / System Maintenance Create a Production Testing link to most closely match the end user experience; mimic firewall rules Create an Admin Login link to aid in general testing to see if there is an issue with the cache and to test any processes that use the “Direct Link” During testing, if an issue is uncovered in Interaction Hub, verify if the issue also exists in HCM or in a different browser

33 Critical Success Factors
Load Testing Schedule early to avoid competing priorities Determine hardware / software installation impacts Ensure load machines upgraded to minimum Windows and browser requirements Ensure test environment mirrors PROD in web / app server allocation Request public IP addresses in advance Perform pre-test Execute test scripts for 10 employees to confirm connectivity, passwords, security, firewalls, functionality *Degradation included refusal connection user errors 15 second lag to log in pages loading in 2 minutes

34 Critical Success Factors
Load Testing – cont’d Determine success criteria Ramped up to 200 users, maintained for an hour Ramped up to 400 users, maintained for an hour Saw degradation at 530 users**

35 Critical Success Factors
Project Management Complete several test moves, scaling back on the level of consultant support Ensure pagelets are pointing to the correct database Complete security pre-tests if functionality needs to be hidden at go-live Include Subject Matter Experts in testing Schedule several standing touchbase calls throughout load testing and go-live weekend Use Google Tracker to identify references to current Self Service links* *Considered redirecting users from the Self Service login page to the Interaction Hub login page, but the URL is the link to the Interaction Hub. Discussed removing security on the web libraries or changing the pages to point to the Interaction Hub and disabling the User ID and password boxes

36 Questions? For additional information on Self-Service functionality and navigation, see: employees/using-self-service-portal/index.html

37 Contacts Kristin McLean Senior Business Analyst
Office of Human Resources, Faculty & Staff Information Systems Northwestern University Eduard Khutornyy; Swee Phua Senior Systems Analyst IT Management Systems

Download ppt "Cut Through the Fog to Create a Golden User Experience with PeopleSoft Interaction Hub Session #CON2232 October 1, 2014."

Similar presentations

Ads by Google