Fluid UI features like tiles, homepages, dashboards etc. make navigating the application intuitive and easy to use. Fluid navigation combined with pivot grid based analytic could help you achieve greater processing efficiency.I have taken a common use case in HR business area and have provided a simple comparison of its execution between classic navigation and analytic driven fluid navigation.
HR administrator to update a job attribute (e.g. contract end date) for a list of employees identified by,
– Specific job title
– In specific department
– Working in specific list of locations
Process in Classic UI
A typical approach to perform this activity would involve,
- Getting the list of employees using PS query or other reporting tool
- Navigate to the target component
- For each employee in the list,
– Find the employee in the component search
– Perform data updates
– Exit the component and find next employee
Analytic driven Fluid Navigation
Fluid framework allow components to be accessed via pivot grid based analytic.This provide users with enhanced capabilities to slice and dice data to suit a variety of business requirements and is a better alternative to reports that address specific requirements.
A pivot grid built on a common data set like employee’s organization attributes – department, location, company etc. can be reused across multiple components. Analytic shown below with a list of filtering options allows the user to narrow down the result set based on variety of attributes. Once the required data is listed, use the result table on the right hand side to access the component.
Shown below is an example of a fluid component that uses pivot grid search with master/detail feature enabled.
‘Master/Detail’ is a feature that allows the search results to be persistent in the left hand side of the component that acts as a master and the detailed component pages on the right hand side. This feature allows for easier navigation thru the search result set without losing it’s context.
It’s a no-brainer that the later option is intuitive and easy to use. Leaving that aside if we objectively compare the statistics of these two options, ratio of clicks required to perform a single transaction using these options stand at 4:1. In essence analytic driven fluid navigation is 75% more efficient than the classical navigation.
As seen in this example, fluid framework provides amazing capabilities to access application functionality. If you are contemplating fluid UI for PeopleSoft then “navigation” must be your highest priority. It is a low hanging fruit and getting it right would reap immediate quantifiable reward.
One of my earlier post this year on Staying classsic in PT 8.55 (for now) is by far the most searched and visited post of mine.
This picture below best describes my frustration that many users upgrading to PT 8.55 are still looking to stay in classic UI.
With PeopleTools 8.55 PeopleSoft customers have incredible potential to improve user experience and processing efficiency, unleash it!