Optimize PeopleSoft HCM 9.2 Fluid UI Tiles & Navigation Collections

Overview: Navigating the Modern PeopleSoft HCM Experience with Fluid UI

In the evolving landscape of enterprise resource planning, user experience (UX) has emerged as a paramount differentiator. Oracle PeopleSoft, a stalwart in the Human Capital Management (HCM) domain, embraced this paradigm shift with its Fluid User Interface (UI). Introduced in PeopleTools 8.54 and significantly matured in HCM 9.2, Fluid UI transforms the traditional, often form-based PeopleSoft interface into a responsive, intuitive, and highly personalized experience akin to modern web and mobile applications. At the heart of this transformation lie two fundamental constructs: Fluid UI homepage tiles and navigation collections.

Fluid UI homepage tiles serve as visual entry points, providing users with immediate access to specific applications, reports, dashboards, or even real-time data summaries. These tiles are dynamic, interactive elements that can display crucial information at a glance – for instance, a "Pending Approvals" tile showing the number of outstanding items, or a "My Team" tile providing quick access to employee profiles. Their primary purpose is to simplify navigation, reduce clicks, and present relevant information contextually, empowering users to perform their most frequent tasks efficiently.

Navigation collections, on the other hand, are organized groupings of links, designed to consolidate related functionalities into a logical, easily consumable structure. While tiles act as front doors, navigation collections are like well-organized hallways, guiding users through a set of interconnected processes or reports. They are particularly effective when integrated into WorkCenters or as part of a tile that leads to a curated list of tasks. Together, tiles and navigation collections form the backbone of the Fluid UI, enabling organizations to deliver a highly customized, role-based, and mobile-friendly experience to their diverse user base, from employees and managers to HR administrators.

Prerequisites for Implementation

Before embarking on the journey of configuring PeopleSoft HCM 9.2 Fluid UI homepage tiles and navigation collections, several prerequisites must be in place to ensure a smooth and successful implementation:

• PeopleSoft HCM 9.2 Application: A fully installed and functional PeopleSoft HCM 9.2 application environment.
• PeopleTools Version: PeopleTools 8.55 or higher is essential, with 8.58 or 8.59 being recommended for access to the latest Fluid enhancements and features.
• Application Designer Access: Administrator-level access to PeopleSoft Application Designer is required for creating and modifying underlying objects like components, pages, and potentially PeopleCode.
• PeopleSoft Pure Internet Architecture (PIA) Access: Administrator access to the PeopleSoft web interface (PIA) with roles such as PeopleSoft Administrator or Portal Administrator is necessary for configuring portal content, security, and Fluid homepages.
• Understanding of PeopleSoft Security: A solid grasp of PeopleSoft security concepts, including permission lists, roles, and content reference security, is crucial for controlling access to tiles and navigation collections.
• Basic SQL Knowledge: Familiarity with SQL will be beneficial for troubleshooting, verifying backend configurations, and especially for creating dynamic tiles based on PeopleSoft queries.
• Web Server and Application Server Access: Occasional access to the PeopleSoft web server and application server command-line interfaces may be needed for cache clearing and service restarts during development and testing.

Step-by-step Implementation: Crafting Your Fluid Experience

The implementation of Fluid UI homepage tiles and navigation collections involves several interconnected steps, from creating the underlying content to defining the visual presentation and securing access. We will walk through the process of creating a custom homepage, designing a dynamic tile, and configuring a navigation collection.

Creating a Custom Fluid Homepage

A custom homepage provides a personalized landing page for specific user groups or roles. This allows for a tailored user experience right from the login.

1. Navigate to Structure and Content:

   In PeopleSoft PIA, navigate to: PeopleTools > Portal > Structure and Content.

2. Create a New Folder (Optional but Recommended):

   To keep your custom content organized, create a new folder under a relevant parent, e.g., under "Fluid Pages".

   • Click "Add Folder".
   • Provide a Folder Label (e.g., "TechNews Custom Homepages").
   • Provide a Folder Name (e.g., "TECHNEWS_CUSTOM_HP").
   • Save the folder.
3. Add a New Homepage Content Reference:

   Within your newly created or chosen folder, click "Add Content Reference".

   • Content Ref Label: A user-friendly label (e.g., "My Custom HR Homepage").
   • Content Ref Name: A unique, internal name (e.g., "TECHNEWS_HR_HOMEPAGE").
   • Usage Type: Select "Homepage".
   • URL Type: Select "PeopleSoft Generic URL".
   • URL: Enter c/NUI_FRAMEWORK.PT_AGSTARTPAGE_NUI.GBL. This is the standard URL for Fluid homepages.
   • Description: A brief description.
   • Effective Date/Status: Set as appropriate.
   • Security: On the "Security" tab, assign the permission lists that should have access to this homepage (e.g., "PTPT1000" for all users, or a custom permission list like "TECHNEWS_HR_ADMIN").
   • Save the Content Reference.

Designing Custom Tiles

Tiles are the visual building blocks of Fluid homepages. We'll focus on creating a dynamic tile, which can display real-time data.

Example: Creating a Dynamic Tile for "Pending Approvals"

This tile will show the count of pending approvals for the currently logged-in user.

1. Create a PeopleSoft Query:

   A dynamic tile often relies on a PeopleSoft Query to retrieve the data it displays. Navigate to: Reporting Tools > Query > Query Manager.

   • Click "Create New Query".
   • Add the record PS_APPR_TRANS_VW (Approval Transaction View).
   • Select the field OPRID and APPROVAL_STATUS as criteria.
   • Add criteria:
     • OPRID = %CurrentUserId (for the current user)
     • APPROVAL_STATUS = 'P' (for pending approvals)
   • Select COUNT(*) as the aggregate field to display the total count.
   • Save the query with a meaningful name, e.g., TECHNEWS_PENDING_APPROVALS.
   • Test the query to ensure it returns the expected count.
2. Create a Content Reference for the Tile:

   Navigate to: PeopleTools > Portal > Structure and Content.

   • Choose an appropriate folder (e.g., "Fluid Pages > Employee Self Service").
   • Click "Add Content Reference".
   • Content Ref Label: "My Pending Approvals".
   • Content Ref Name: "TECHNEWS_PENDING_APPR_TILE".
   • Usage Type: Select "Tile".
   • URL Type: "PeopleSoft Generic URL".
   • URL: This URL will point to the component that the tile navigates to when clicked. For an approvals tile, this might be c/ROLE_EMPLOYEE.PT_AWE_APPR_INBOX.GBL (the delivered Approval Inbox).
   • Description: "Shows count of pending approvals."
3. Configure Fluid Attributes for the Tile:

   While still on the Content Reference definition page, navigate to the "Fluid Attributes" tab.

   • Tile Name: "TECHNEWS_PENDING_APPR_TILE" (should match Content Ref Name).
   • Tile Type: Select "Dynamic". This enables the tile to display real-time data.
   • Tile Image: Choose a suitable image from the image library (e.g., "PT_WF_APPROVAL_FL_GBL").
   • Tile Class: This controls the visual styling (e.g., "ps_tile_primary" for a standard tile).
   • Tile Content: This is where you link your query. Select "PeopleSoft Query".
     • Query Name: Enter TECHNEWS_PENDING_APPROVALS.
     • Query Field Name: Enter the field name that contains the count (e.g., "COUNT").
   • Refresh Interval: Set a refresh interval (e.g., "300" seconds for 5 minutes) if you want the tile to automatically update its count.
   • Security: On the "Security" tab, assign permission lists that grant access to this tile (e.g., "HCDPALL" or a custom permission list).
   • Save the Content Reference.

Configuring Navigation Collections

Navigation collections group related links, often used within WorkCenters or as a menu structure behind a tile.

Example: Creating an "HR Admin Quick Links" Navigation Collection

1. Navigate to Navigation Collections:

   In PeopleSoft PIA, navigate to: PeopleTools > Portal > Navigation Collections.

2. Create a New Navigation Collection:
   • Click "Add Navigation Collection".
   • Collection Name: "TECHNEWS_HR_ADMIN_LINKS".
   • Collection Label: "HR Admin Quick Links".
   • Description: "Quick links for HR Administrators."
   • Effective Date/Status: Set as appropriate.
   • Save the collection.
3. Add Content to the Collection:

   After saving, you'll be on the "Content" tab.

   • Click "Add Link".
   • Use the "Search" icon to find existing content references. For example:
     • Search for "Add a Person" (Component: HR_ADD_PERSON)
     • Search for "Manage Job" (Component: JOB_DATA_FL)
     • Search for "View Paycheck" (Component: PY_SSP_VIEW_PAYCH_FL)
   • Select the desired content references and add them to the collection.
   • You can also add folders within the collection to further categorize links. Click "Add Folder" and then add links within that folder.
   • Security: The security for each link within the navigation collection is inherited from its underlying content reference. Ensure the permission lists assigned to the navigation collection itself (on the "Security" tab) and to the individual links grant appropriate access.
   • Save the collection.

Assigning Tiles to Homepages and Granting Access

1. Assign Tiles to Your Custom Homepage:

   Navigate to: PeopleTools > Portal > Fluid Homepages > Homepage Content.

   • Select your custom homepage (e.g., "My Custom HR Homepage" / TECHNEWS_HR_HOMEPAGE).
   • Click "Add Tile".
   • Search for your newly created tile (e.g., "My Pending Approvals" / TECHNEWS_PENDING_APPR_TILE).
   • Add the tile to the homepage.
   • You can drag and drop tiles to reorder them.
   • Save the changes.
2. Grant Access to the Custom Homepage:

   To make your custom homepage available to users, you must grant access to its underlying content reference via permission lists.

   • Navigate to: PeopleTools > Security > Permissions & Roles > Permission Lists.
   • Open the relevant permission list (e.g., "HCDPALL" or your custom "TECHNEWS_HR_ADMIN").
   • Go to the "Fluid" tab.
   • Click "Fluid Homepages".
   • Add your custom homepage (e.g., "My Custom HR Homepage").
   • Save the permission list.
3. Set Default Homepage (Optional):

   To make your custom homepage the default for specific roles, navigate to: PeopleTools > Portal > Fluid Homepages > Assign Homepages.

   • Add a new row.
   • Specify the Role Name (e.g., "HR Administrator").
   • Select your Homepage Name (e.g., "My Custom HR Homepage").
   • Set it as the Default Homepage.
   • Save the configuration.

Deployment and Testing

After making configuration changes, it's crucial to clear cache and thoroughly test the new setup.

1. Clear Web Server Cache:

   Access your PeopleSoft web server command line and clear the cache. This ensures the web server picks up the latest portal definitions.

   
   cd <PS_CFG_HOME>/webserv/<your_domain_name>/applications/peoplesoft/cache
   rm -rf *
   

2. Clear Application Server Cache:

   Access your PeopleSoft application server command line and clear the cache using psadmin.

   
   psadmin -c clear_cache -d <your_domain_name>
   

3. Test as Different Users:

   Log in as an administrator to verify all configurations. Then, log in as a regular user (e.g., an employee, a manager, and an HR administrator) to ensure that tiles and navigation collections are displayed correctly and that security is enforced as expected.

Security Considerations

Security is paramount in PeopleSoft, and Fluid UI components are no exception. A robust security model ensures that users only see and access the information and functions relevant to their roles.

• Content Reference Security: The fundamental layer of security for any PeopleSoft object, including tiles and navigation collection links, is controlled at the Content Reference level. Each content reference must have one or more permission lists assigned to it on the "Security" tab. If a user does not have access to the underlying content reference, they will not see the tile or link, regardless of other settings.
• Permission Lists and Roles: Access to Fluid homepages, tiles, and navigation collections is ultimately granted through permission lists, which are then assigned to roles, and roles to users.
  • Homepage Security: The custom homepage itself is secured via its content reference. Users must have a role that contains a permission list granting access to the homepage content reference.
  • Tile Security: Each tile's content reference must be secured. Additionally, if a tile navigates to a component, the user must also have access to that underlying component via a permission list.
  • Navigation Collection Security: Access to the navigation collection as a whole is granted via its definition. However, the security of individual links within the collection is determined by the security of their respective content references. If a user doesn't have access to a specific link, it simply won't appear in their navigation collection.
• Data Security (for Dynamic Tiles): For dynamic tiles displaying data (e.g., "Pending Approvals"), ensure that the underlying PeopleSoft Query or PeopleCode adheres to row-level security. The query should use bind variables like %CurrentUserId or incorporate security views to prevent users from seeing data they are not authorized to view.
• Least Privilege Principle: Always adhere to the principle of least privilege. Grant users only the minimum access required to perform their job functions. Overly broad permission lists can expose sensitive data or functionality.
• Auditing and Review: Regularly audit security configurations for custom Fluid components. Changes to permission lists, roles, and content references should be tracked and reviewed to maintain a secure environment.

Example SQL to check which permission lists grant access to a specific menu item (useful for troubleshooting component security behind a tile):

SELECT DISTINCT A.CLASSID, A.CLASSDEFN
FROM PSCLASSDEFN A, PSPNLGROUP B
WHERE A.MENUNAME = B.MENUNAME
  AND A.BARNAME = B.BARNAME
  AND A.ITEMNAME = B.ITEMNAME
  AND B.PNLITEMNAME = 'PT_AWE_APPR_INBOX_FL'; -- Example: Approval Inbox Fluid component

Best Practices for Fluid UI Homepages and Navigation Collections

To maximize the value of PeopleSoft Fluid UI, consider these best practices during design, implementation, and ongoing maintenance:

• User-Centric Design: Always start with the end-user in mind. What tasks do they perform most frequently? What information do they need at a glance? Design homepages and tiles to streamline these key activities.
• Keep Homepages Clean and Focused: Avoid cluttering homepages with too many tiles. Aim for a manageable number (e.g., 6-12) of essential tiles per role. Use navigation collections or WorkCenters for deeper dives into related functions.
• Intuitive Naming and Iconography: Use clear, concise labels for tiles and navigation collection items. Select meaningful and consistent icons to visually represent their function, aiding quick recognition. Leverage the delivered PeopleSoft icon library where possible.
• Performance Optimization: For dynamic tiles, ensure that the underlying PeopleSoft Queries or PeopleCode are highly optimized. Poorly performing queries can significantly degrade homepage load times, leading to a frustrating user experience. Regularly review and tune these queries.
• Standardization and Consistency: Establish naming conventions for custom tiles, homepages, and navigation collections. Maintain a consistent look and feel across different homepages to reduce cognitive load for users.
• Leverage Delivered Content: Before creating custom components, explore the rich set of delivered Fluid tiles, WorkCenters, and navigation collections. Often, delivered content can be configured or extended to meet requirements, reducing development effort and improving maintainability.
• Responsive Design Testing: Test your Fluid homepages and tiles across various devices (desktops, tablets, smartphones) and browsers to ensure a consistent and responsive user experience. PeopleSoft Fluid is designed to be responsive, but custom layouts or embedded content might require specific adjustments.
• Accessibility: Ensure that your Fluid UI designs adhere to accessibility standards. PeopleSoft Fluid UI provides a good foundation, but custom content should also be designed with accessibility in mind (e.g., proper alt text for images, keyboard navigation).
• Documentation: Document all custom Fluid UI configurations, including tile definitions, query names, permission list assignments, and the business rationale behind specific design choices. This is invaluable for future maintenance and troubleshooting.
• Iterative Development and Feedback: Implement Fluid UI in an iterative manner. Gather feedback from end-users early and often, and incorporate their suggestions into subsequent design iterations. This fosters user adoption and ensures the solution truly meets their needs.

Frequently Asked Questions (FAQ)

Q1: How do I make a custom homepage the default for a specific role?

A: You can assign a custom homepage as the default for a specific role via the "Assign Homepages" component. Navigate to: PeopleTools > Portal > Fluid Homepages > Assign Homepages. Here, you can add a new row, specify the 'Role Name' (e.g., 'HR Administrator'), select your 'Homepage Name' (e.g., 'My Custom HR Homepage'), and check the 'Default Homepage' checkbox. This ensures that users assigned to that role will see your custom homepage as their primary landing page upon login. Remember that a user can be assigned multiple roles, and the system will determine the default based on an internal hierarchy or the first default homepage encountered in their role list.

Q2: My dynamic tile isn't refreshing its count. What should I check?

A: Several factors can prevent a dynamic tile from refreshing:

1. Refresh Interval: First, check the 'Refresh Interval' on the 'Fluid Attributes' tab of the tile's Content Reference definition (PeopleTools > Portal > Structure and Content). Ensure it's set to a value greater than zero (e.g., 300 seconds for 5 minutes).
2. PeopleSoft Query: Verify that the underlying PeopleSoft Query (specified in 'Tile Content') is working correctly and returning data. Run the query directly in Query Manager to confirm. Ensure the 'Query Field Name' on the tile definition correctly points to the field containing the count or data you wish to display.
3. Caching: Clear the web server cache and application server cache as outlined in the "Deployment and Testing" section. Browser cache might also be a factor; try clearing your browser's cache or testing in an incognito window.
4. Security: Ensure the user has access to the underlying query and any records/views used by the query.
5. Browser Issues: Sometimes, browser-specific issues or extensions can interfere with JavaScript-driven tile refreshes. Test in a different browser.

Q3: Can I hide or show tiles based on user attributes beyond simple permission lists, like department or location?

A: Yes, this is possible, though it requires more advanced configuration, often involving PeopleCode.

1. Component-based Tile with PeopleCode: Instead of a simple content reference, create a custom component (with a page) that acts as the tile's target. On the 'Page Activate' or 'Component PostBuild' event of this component, you can write PeopleCode to evaluate user attributes (e.g., from `USER_PROFILE`, `PS_JOB` record, or custom tables) and then dynamically control the visibility of elements on the page or even redirect if the user is not authorized. The tile itself would still be secured by permission list, but the component behind it would enforce finer-grained control.
2. Custom Tile Content Pagelet: For highly dynamic scenarios, you can develop a custom Fluid pagelet (using Application Designer) that encapsulates the logic for displaying the tile content. This pagelet would contain PeopleCode to perform the necessary checks against user profiles or other data. The tile's definition would then point to this custom pagelet.
3. Delivered Personalization (Limited): While not attribute-based, users can personalize their homepages by hiding tiles they don't use. However, this is user-driven, not system-enforced based on attributes.

For attribute-based visibility, PeopleCode is generally the most flexible and robust solution, allowing you to implement complex business rules.

Conclusion

The Oracle PeopleSoft HCM 9.2 Fluid UI represents a significant leap forward in delivering a modern, intuitive, and highly personalized user experience. At its core, the intelligent design and strategic deployment of homepage tiles and navigation collections are pivotal to unlocking this potential. By transforming the way users interact with the system, organizations can dramatically improve user adoption, increase productivity, and enhance employee engagement across the entire HR ecosystem.

The journey from traditional PeopleSoft navigation to a fully fluid environment is not merely a cosmetic upgrade; it's a strategic move towards a more agile and user-centric enterprise application. Through careful planning, meticulous implementation, and adherence to best practices, organizations can empower their workforce with a PeopleSoft experience that is not just functional but also delightful. As PeopleSoft continues to evolve with its Selective Adoption and Continuous Delivery model, mastering Fluid UI components will remain a key competency for maximizing the return on investment in one of the most robust HCM platforms available today.