Tag: PeopleSoft Fluid User Interface

Quest had the opportunity to talk with McMaster University about their Selective Adoption strategy. When exploring new features for Selective Adoption, teams review the dependencies/pre-requisites to apply the new features. They then determine if Selective Adoption is the most viable and resource efficient way to implement the new feature.

Quest had the opportunity to talk with McMaster University about their Fluid User Interface deployment. The university is currently on HCM Image 23 PeopleTools 8.55.05, FSCM Image 25 PeopleTools 8.55.05, Interaction Hub Image 2 PeopleTools 8.55.12, Campus Solutions 9.0 PeopleTools 8.55.12, EPM (DW) 9.1 PeopleTools 8.55.03, Custom PeopleTools Dev. (Bolt On) PeopleTools 8.55.05 and Hyperion 11.1.2.3.700.

Presented by CDW

We are in the process of upgrading to 9.2 Image 23 and Tools 8.55.17 with go live date of Nov 11th. Also working on taking advantage of the GSS features to automate our current manual process. Instead of creating bolt-on capabilities, we determined it was best to use GSS as a prep for future usability via mobile. But as with all clients, there is always additional features that requirement some customization. There are 3 new transactions we have to create: Request Tax Location Change, Request Shift Differential Change and Coworker Jon and/or Salary Change. With this it requirements cloning, configurations, AWE and coding due to usage of some custom values used in the Job data component.

Are you looking to use Fluid User Interface or want to hear what others are doing? If so, join us to hear directly from a panel around their experience with Fluid User Interface. Learn what they are doing with it and more important, how they made it happen.

The demonstration will include developing a fluid page, and applying advanced object features including CSS code to the custom group boxes. Next we will set the fluid properties for the Component, add a fluid folder, issue the proper security and finally add a new tile to deploy our new fluid application.

John Robinson and Tammy Boyles from Oracle spoke at RECONNECT 18 about Fluid Simplified Analytics for Human Capital Management (HCM). Their presentation provided customers with key information about the new features and provided a roadmap update.

Intermountain Healthcare recently shared its Fluid implementation success story at RECONNECT 18. The company implemented PeopleSoft 9.2 with Fluid UI in June 2017 with PUM 19. In March 2018, they moved to PeopleTools 8.56 and PeopleSoft PUM 25 with Selective Adoption.

The Fluid user interface is an evolutionary UI experience that adjusts an application’s resolution depending on the user’s device making it PC as well as mobile-friendly. Fluid makes use of standard web development standards like CSS3, JavaScript and HTML 5.0 to develop applications.

We share how Intermountain implemented and optimized Fluid to create a great end-user experience and improve productivity.

Introduction of Fluid technology reflects the growing mobility of the workforce, and the corresponding demand for ease-of-use to promote immediacy, accuracy and accountability.
While the demand for mobility has increased dramatically, use cases require significant analysis and technical competence that can be easily underestimated. To effectively introduce a mobile framework requires several key factors.