Oracle PeopleSoft HCM 9.2 Fluid UI: Homepage Tiles & Navigation Collections

Oracle PeopleSoft HCM 9.2 Fluid UI: Mastering Homepage Tiles and Navigation Collections for Enhanced User Experience

As a senior technology writer at TechNews Venture, I’ve witnessed the evolution of enterprise software interfaces firsthand. Oracle PeopleSoft, a cornerstone for Human Capital Management (HCM) in countless organizations, underwent a significant transformation with the introduction of its Fluid User Interface (UI). Fluid UI, initially rolled out with PeopleTools 8.54 and maturing significantly in HCM 9.2 with PeopleTools 8.55+, reshaped how users interact with the system. It moved away from the traditional, component-centric navigations to a more intuitive, responsive, and personalized experience, heavily leveraging homepage tiles and navigation collections. This article delves deep into these pivotal elements, offering a comprehensive guide to their implementation and optimization.

Overview of Fluid UI, Tiles, and Navigation Collections

The PeopleSoft Fluid UI represents a paradigm shift from the classic desktop-centric interface to a mobile-first design philosophy. Its core tenets are responsiveness, personalization, and simplicity. This means the interface automatically adjusts to various screen sizes, from desktops to tablets and smartphones, providing a consistent user experience across devices. At the heart of this responsive design are Fluid Homepages, which serve as personalized dashboards for users.

Fluid Homepage Tiles: These are the visual entry points on a Fluid Homepage. Think of them as dynamic, interactive icons that can display key information at a glance (e.g., "Pending Approvals: 3," "My Paychecks") and serve as direct links to specific pages or components. Tiles can be static, displaying a fixed label and image, or dynamic, pulling real-time data from the PeopleSoft system via PeopleSoft Queries or PeopleCode. Their primary purpose is to provide immediate access to frequently used functions and critical information, reducing navigation clicks and improving efficiency.

Navigation Collections: While tiles offer direct access, navigation collections provide a structured, hierarchical menu system within the Fluid UI. They are essentially modernized folders that group related content references (CREFs) – pages, components, or even external URLs – into a logical structure. A navigation collection can itself be published as a tile on a homepage, offering a consolidated entry point to a related set of tasks or information. For instance, an "Employee Self-Service" tile might lead to a navigation collection containing links for "View Paycheck," "Update Personal Information," "Benefits Enrollment," and "Time Off Request." This approach helps in organizing complex functionalities into manageable, intuitive groups.

Together, Fluid homepage tiles and navigation collections empower organizations to deliver a highly customized and efficient user experience in PeopleSoft HCM 9.2. They streamline access, reduce training overhead, and significantly enhance user adoption by presenting information and tasks in a contextually relevant and visually appealing manner.

Prerequisites for Implementation

Before embarking on the journey of creating and configuring Fluid UI tiles and navigation collections, ensure the following prerequisites are met:

• PeopleTools Version: PeopleSoft HCM 9.2 requires PeopleTools 8.55 or higher to fully leverage Fluid UI capabilities. While earlier versions of 8.5x introduced Fluid, 8.55+ provides the robust feature set and stability necessary for production environments.
• Application Version: Oracle PeopleSoft HCM 9.2 is the target application version. Ensure your environment is at this release level or higher.
• Understanding of PeopleSoft Security: A solid grasp of PeopleSoft security concepts, including roles, permission lists, and content reference security, is crucial. This ensures that tiles and collections are only accessible to authorized users.
• Application Designer Proficiency: Familiarity with PeopleSoft Application Designer is essential for defining content references (CREFs), components, and potentially writing PeopleCode for dynamic tile content.
• PeopleSoft Query Knowledge: For dynamic tiles that display real-time data, proficiency in creating and optimizing PeopleSoft Queries is required.
• Administrative Access: You will need administrative roles and permissions within PeopleSoft to access the necessary setup pages (e.g., Portal Administrator, PeopleTools Administrator).
• Browser Compatibility: Ensure client browsers are compatible with the PeopleSoft Fluid UI (modern browsers like Chrome, Firefox, Edge, Safari are generally supported).

Step-by-Step Implementation Guide

1. Creating a Custom Fluid Homepage Tile

Let's walk through creating a dynamic tile that displays the count of pending approvals for the current user. This is a common requirement in HCM systems.

a. Define the Content Reference (CREF) for the Target Page

First, ensure the target page or component that the tile will link to has a defined content reference. If you're linking to an existing component, this is usually already done. If it's a new custom page, you'll need to define it in Application Designer and then register it in Structure and Content.

-- Example of creating/verifying a Content Reference in PeopleTools > Portal > Structure and Content
-- Path: PeopleTools > Portal > Structure and Content > [Root Folder e.g., HCM] > [Folder e.g., Employee Self Service]
-- Ensure the component/page you want to link to is registered here.
-- Node Name: HRMS
-- Content Ref Name: EOAW_APPROVAL_MONITOR_FL (Example for Approval Monitor Fluid page)
-- URL Type: PeopleSoft Component
-- Menu Name: HCSC_FL
-- Component: EOAW_APPROVAL_MON_FL
-- Page: EOAW_APPROVAL_MON_FL
-- Action: A

b. Create a PeopleSoft Query for Dynamic Tile Content

For a dynamic tile, we need a query that fetches the data to be displayed. Let's create a query to count pending approvals.

-- Navigate to: Reporting Tools > PS Query > Query Manager
-- Create a new query, e.g., HCSC_PENDING_APPROVALS_COUNT
-- Add Record: EOAW_TXN (Approval Transaction)
-- Add Fields: COUNT(A.EOAWDEFN_ID)
-- Add Criteria:
-- A.EOAWPRCS_ID = 'HR_APPROVALS' (Replace with your actual approval process ID)
-- A.EOAW_STEPSTATUS = 'P' (Pending status)
-- A.OPRID = %CurrentUserId (To show approvals for the logged-in user)
-- Save the query. Note the Query Name, as it will be used in the Tile Wizard.

The SQL generated by PeopleSoft Query would look something like this:

SELECT COUNT(A.EOAWDEFN_ID)
FROM PS_EOAW_TXN A
WHERE A.EOAWPRCS_ID = 'HR_APPROVALS'
  AND A.EOAW_STEPSTATUS = 'P'
  AND A.OPRID = %CurrentUserId;

c. Create the Fluid Tile Using the Tile Wizard

The Tile Wizard simplifies the process of creating Fluid tiles.

1. Navigate to: PeopleTools > Portal > Fluid Homepages > Fluid Homepage Content > Create Fluid Tile.
2. Click Add a New Value. Enter a Tile Name (e.g., HCSC_PENDING_APPROVALS_TILE) and a Description. Click Add.
3. Tile Definition:
   • Tile Type: Select Dynamic Tile.
   • Tile Label: Enter a user-friendly label (e.g., "Pending Approvals").
   • Tile Name: (Populated from previous step).
   • Tile Id: (Auto-generated).
   • Parent Folder: Choose a logical folder (e.g., ROOT or a custom folder for your tiles).
   • Image Class: Select an appropriate icon from the delivered PeopleSoft Image Catalog (e.g., psicon-time-sheet or search for 'pending'). You can also upload custom SVG images.
   • Drilldown Content Ref: Click the lookup and select the CREF for the target page (e.g., PT_APPROVE_TRANSACTIONS_FL or your custom approval monitor).
4. Dynamic Tile Properties:
   • Data Type: Select PeopleSoft Query.
   • Query Name: Enter the name of the PS Query you created (e.g., HCSC_PENDING_APPROVALS_COUNT).
   • Query Column Name: Enter the alias or name of the column containing the count (e.g., COUNT_EOAWDEFN_ID or EXPR1 if no alias was given).
   • Query Parameters: If your query requires parameters, define them here. For %CurrentUserId, PeopleSoft automatically handles it.
   • Tile Text: This is the text displayed on the tile. You can use %1 as a placeholder for the query result. Example: Pending: %1.
   • Refresh Rate: Set how often the tile should refresh its dynamic data (e.g., 15 minutes).
5. Publish Tile: Click the Publish Tile button. This registers the tile as a CREF in the portal registry.

After publishing, the tile is now available to be added to homepages. You can inspect the generated CREF under PeopleTools > Portal > Structure and Content > Fluid Homepages > Fluid Pages > [Your Tile].

Note on PeopleCode for Dynamic Tiles: For more complex dynamic tile logic that cannot be achieved with a simple PS Query, you can use PeopleCode. In the Tile Wizard, for "Data Type," you would select "PeopleCode." You would then specify an Application Class that implements the PT_PAGES.TILE_UTIL.IBaseTile interface and returns the dynamic data. This is an advanced topic but offers maximum flexibility.

/* Example PeopleCode for a dynamic tile (simplified) */
/* This code would typically be part of an Application Class */
/* that implements PT_PAGES.TILE_UTIL.IBaseTile */

class HCSC_MY_TILE_CLASS implements PT_PAGES.TILE_UTIL.IBaseTile
   method getTileCount() Returns string;
   method getTileURL() Returns string;
   method getTileText() Returns string;
end-class;

method getTileCount
   Local SQL &sqlCount;
   Local number &nCount;
   &sqlCount = CreateSQL("SELECT COUNT(A.EOAWDEFN_ID) FROM PS_EOAW_TXN A WHERE A.EOAWPRCS_ID = 'HR_APPROVALS' AND A.EOAW_STEPSTATUS = 'P' AND A.OPRID = :1", %CurrentUserId);
   &sqlCount.Fetch(&nCount);
   Return String(&nCount);
end-method;

method getTileURL
   /* Generate a URL to the approval page */
   Local string &sURL;
   &sURL = GenerateFluidRelativeURL(Page.PT_APPROVE_TRANSACTIONS_FL);
   Return &sURL;
end-method;

method getTileText
   /* This method could construct more complex text if needed */
   Return "Pending: " | %This.getTileCount();
end-method;

2. Creating a Navigation Collection

Navigation collections group related links, providing a structured menu system. Let's create an "Employee Self-Service" collection.

1. Navigate to: PeopleTools > Portal > Portal Utilities > Navigation Collections.
2. Click Add a New Value. Enter a Collection Name (e.g., HCSC_EMP_SELF_SERVICE_NAV) and a Description. Click Add.
3. Collection Properties:
   • Collection Name: (Populated).
   • Collection Type: Select Fluid.
   • Label: Enter a user-friendly label (e.g., "Employee Self-Service").
   • Image Class: Select an icon (e.g., psicon-employee-self-service).
4. Collection Content:
   • Click Add Link to add individual content references.
     • Link Type: Content Reference.
     • Content Reference: Use the lookup to select the CREF for "View Paycheck" (e.g., HP_PAYSLIP_FL). Enter a Label (e.g., "View Paycheck").
   • Repeat for other self-service items:
     • "Update Personal Info" (e.g., W3EB_PERSON_INFO_FL)
     • "Benefits Enrollment" (e.g., W3EB_BENEFITS_FL)
     • "Time Off Request" (e.g., TL_ESS_REQ_TIME_FL)
   • You can also add Folder elements to create sub-groups within the collection. For example, a "Benefits" folder containing various benefit-related links.
   • Use the up/down arrows to reorder links and folders.
5. Publish Collection: Click Publish Collection. This creates a CREF for the navigation collection, making it available to be added to homepages.

The published collection will appear as a CREF under PeopleTools > Portal > Structure and Content > Fluid Homepages > Fluid Pages > [Your Collection].

3. Assigning Tiles and Collections to Fluid Homepages

Once tiles and navigation collections are created and published, they need to be assigned to one or more Fluid Homepages. Users are then granted access to these homepages.

a. Create or Modify a Fluid Homepage

1. Navigate to: PeopleTools > Portal > Fluid Homepages > Fluid Homepage Content > Fluid Homepages.
2. Select an existing homepage (e.g., EMPLOYEE) or click Add a New Value to create a new one (e.g., HCSC_EMPLOYEE_HOMEPAGE).
3. Homepage Properties:
   • Homepage Label: Enter a user-friendly label (e.g., "HCSC Employee Homepage").
   • Homepage Name: (Populated).
   • Image Class: Select an icon for the homepage itself (e.g., psicon-home).
4. Homepage Content:
   • Click Add Tile.
   • In the search window, find your custom tile (e.g., HCSC_PENDING_APPROVALS_TILE) and your navigation collection (e.g., HCSC_EMP_SELF_SERVICE_NAV). Select them and click Add.
   • You can also add delivered tiles (e.g., "My Team," "Company Directory").
   • Rearrange the tiles as desired using the drag-and-drop functionality on the page.
5. Save the homepage.

b. Assign Homepage Security

To make the homepage accessible to users, you must assign it to relevant permission lists or roles.

1. On the Fluid Homepages page, with your homepage selected, go to the Security tab.
2. Add the permission lists or roles that should have access to this homepage. For example, add the HCSC_EMPLOYEE role.
3. Ensure the permission lists associated with these roles also grant access to the underlying components and pages linked by your tiles and navigation collection items.

c. Set Default Homepage for Users/Roles (Optional)

You can configure a default homepage for users or roles.

1. Navigate to: PeopleTools > Portal > Configure Homepage.
2. You can set a system-wide default, or override it for specific roles or users.
3. For example, select a role (e.g., HCSC_EMPLOYEE) and set its Default Homepage to HCSC_EMPLOYEE_HOMEPAGE.

Users can also personalize their homepages by adding, removing, and rearranging tiles, provided they have the necessary permissions (controlled via PeopleTools > Portal > Fluid Homepages > Fluid Homepage Content > Fluid Homepages > Personalization Options).

Security Considerations

Implementing Fluid UI tiles and navigation collections requires careful attention to security to prevent unauthorized access to sensitive HCM data and functions.

• Content Reference Security: Every tile and every link within a navigation collection is ultimately a Content Reference (CREF). Access to these CREFs is controlled by permission lists. Ensure that the permission lists assigned to roles only grant access to the CREFs that are appropriate for that role.

  
  -- To check/modify CREF security:
  -- Navigate to PeopleTools > Portal > Structure and Content
  -- Find the CREF (e.g., your tile or a link within a navigation collection)
  -- Go to the "Security" tab and ensure only authorized permission lists are listed.
          

• Component and Page Security: Beyond CREF security, the underlying PeopleSoft components and pages linked by tiles must also have appropriate security defined at the permission list level (PeopleTools > Security > Permissions & Roles > Permission Lists > Pages tab). If a user has access to a tile but not the underlying component, they will receive an authorization error upon clicking the tile.
• Data Security (Row-Level Security): For dynamic tiles displaying data from PS Queries, ensure that row-level security is correctly applied. If the PS Query itself is not secured by the Query Access Group or if the underlying records lack row-level security, users might see data they are not authorized for, even if the tile's CREF is secured. Use %CurrentUserId and other bind variables in queries to restrict data to the logged-in user.
• Homepage Security: Access to the Fluid Homepages themselves is also controlled by permission lists/roles, as demonstrated in step 3b. A user must have access to the homepage to see the tiles on it.
• Audit and Review: Regularly audit security configurations for tiles, navigation collections, and underlying components. As business requirements change, access needs may evolve, and configurations should be reviewed to maintain a secure posture.

“In the realm of enterprise systems, security isn't just about preventing breaches; it's about building trust. A well-designed Fluid UI, coupled with robust security, ensures that users interact with the system confidently, knowing their data and privacy are protected.” — Someshwar Thakur

Best Practices for Fluid UI Tiles and Navigation Collections

To maximize the benefits of Fluid UI and ensure a positive user experience, adhere to these best practices:

• Keep Homepages Clean and Focused: Avoid clutter. Each homepage should serve a specific purpose (e.g., "Employee Self-Service," "Manager Dashboard," "Benefits Admin"). Limit the number of tiles on a single homepage to prevent cognitive overload.
• Meaningful Icons and Labels: Use descriptive labels and intuitive icons that clearly convey the tile's function. Leverage the extensive PeopleSoft Image Catalog or design custom SVG icons for brand consistency.
• Optimize Dynamic Queries: For dynamic tiles, ensure that the underlying PeopleSoft Queries are highly optimized for performance. Slow queries can degrade the entire homepage load time. Avoid complex joins or unindexed fields. Test query performance thoroughly.

  
  -- Example of checking query execution plan in SQL Developer/Toad for a PeopleSoft query
  -- (Run against the underlying database after identifying the SQL generated by PS Query)
  EXPLAIN PLAN FOR
  SELECT COUNT(A.EOAWDEFN_ID)
  FROM PS_EOAW_TXN A
  WHERE A.EOAWPRCS_ID = 'HR_APPROVALS'
    AND A.EOAW_STEPSTATUS = 'P'
    AND A.OPRID = 'PSADMIN'; -- Use a test OPRID for plan generation
  SELECT * FROM TABLE(DBMS_XPLAN.DISPLAY);
          

• Standardize Tile Design: Maintain consistency in tile size, color, and layout where possible. This creates a cohesive look and feel across the application.
• Leverage Delivered Content: Before creating custom tiles or collections, explore the rich set of delivered Fluid content. Oracle provides many out-of-the-box tiles and navigation collections for common HCM functions. Customize these where appropriate, rather than reinventing the wheel.
• Role-Based Personalization: While administrators can define default homepages and tiles, empower users with the ability to personalize their homepages within defined boundaries. This fosters a sense of ownership and improves usability.
• User Testing and Feedback: Involve end-users early and often in the design and testing phases. Their feedback is invaluable for refining tile placement, labels, and overall navigation flow.
• Plan for Future Enhancements: Design your tile and collection structure with scalability in mind. Anticipate future modules or features and ensure your navigation framework can accommodate them gracefully.
• Document Everything: Maintain thorough documentation of all custom tiles, queries, navigation collections, and their security configurations. This is critical for maintenance, troubleshooting, and future upgrades.

Frequently Asked Questions (FAQ)

Q1: How can I restrict a specific tile to be visible only to certain users or roles?

A1: Tile visibility is controlled at the Content Reference (CREF) level. After creating a tile using the Tile Wizard, it is published as a CREF in the portal registry. You can navigate to PeopleTools > Portal > Structure and Content, locate your tile's CREF, and then go to the Security tab. Here, you can add or remove permission lists to control which users (based on their assigned roles and permission lists) can see and access that specific tile. If a user does not have access to the tile's CREF, it will not appear on their homepage, even if the homepage itself is accessible.

Q2: Can I have dynamic content on a tile that isn't just a count, like displaying a message or a status?

A2: Yes, you can. While PeopleSoft Query is excellent for displaying counts or single values, for more complex dynamic content, you can use PeopleCode. When creating a dynamic tile in the Tile Wizard, select "PeopleCode" as the Data Type. You will then specify an Application Class that implements the PT_PAGES.TILE_UTIL.IBaseTile interface. This Application Class can contain methods to return not only a count but also specific text, colors, or even complex HTML to be displayed on the tile, offering maximum flexibility in how dynamic information is presented.

Q3: What's the key difference between a Fluid Homepage Tile and a Navigation Collection? When should I use one over the other?

A3: A Fluid Homepage Tile is primarily a single, interactive entry point to a specific function or piece of information. It can be static or dynamic, displaying real-time data or a direct link. It's best used for frequently accessed functions, key metrics, or direct access to a single page (e.g., "View Paycheck," "Pending Approvals").

A Navigation Collection, on the other hand, is a structured grouping of multiple related links (CREFs). It acts as a mini-menu or a folder system. A navigation collection itself can be published as a tile. You should use a navigation collection when you have several related items that users need to access, and grouping them logically improves navigation (e.g., an "Employee Self-Service" collection containing links to "View Paycheck," "Update Personal Info," "Time Off Request"). The tile acts as the door, and the navigation collection is the lobby with multiple doors inside.

Conclusion

The Oracle PeopleSoft HCM 9.2 Fluid UI, with its intelligent application of homepage tiles and navigation collections, marks a significant leap forward in delivering an intuitive, personalized, and mobile-responsive user experience. By meticulously planning, implementing, and securing these elements, organizations can transform how their employees interact with vital HR functions, reducing training costs, improving efficiency, and boosting overall user satisfaction.

Mastering Fluid UI is not merely about adopting new technology; it's about embracing a design philosophy that prioritizes the user. As a domain expert, I emphasize that the true power lies not just in creating tiles and collections, but in crafting a thoughtful, user-centric architecture that aligns with your organization's specific needs and workflows. The future of PeopleSoft HCM is fluid, and a strategic approach to its interface elements is paramount for sustained success.