Oracle PeopleSoft HCM 9.2 Fluid UI: Tiles & Nav Collections Guide

Overview: Modernizing User Experience with PeopleSoft HCM 9.2 Fluid UI

In the ever-evolving landscape of enterprise software, user experience (UX) has emerged as a critical differentiator. Oracle PeopleSoft, a robust and comprehensive suite for Human Capital Management (HCM), embraced this paradigm shift with the introduction of its Fluid User Interface (UI). PeopleSoft HCM 9.2, powered by PeopleTools 8.54 and later, marked a pivotal moment, transforming the traditional, menu-driven interface into a responsive, intuitive, and visually appealing experience designed for today's multi-device world.

At the heart of the Fluid UI experience are two fundamental architectural components: **Homepage Tiles** and **Navigation Collections**. These elements not only enhance the aesthetic appeal but fundamentally redefine how users interact with the system, providing quick access to critical information and streamlining navigation. Homepage tiles act as actionable shortcuts, often displaying real-time data or counts, allowing users to glean insights at a glance and dive directly into relevant tasks. Navigation collections, on the other hand, provide a structured, hierarchical menu system that is both flexible and easily digestible, replacing the classic menu structure with a more modern, tree-like presentation.

The transition to Fluid UI is more than just a cosmetic upgrade; it's a strategic move towards empowering users with a personalized, efficient, and mobile-friendly interface. For HCM specifically, this translates into improved employee and manager self-service adoption, reduced training overhead, and ultimately, a more productive workforce. As a senior technology writer at TechNews Venture, I've observed firsthand how organizations leveraging Fluid UI effectively have seen significant returns on their PeopleSoft investments. This article will delve into the technical intricacies of configuring and managing Fluid UI homepage tiles and navigation collections, providing a detailed guide for PeopleSoft administrators and developers.

Prerequisites for Fluid UI Configuration

Before embarking on the journey of configuring Fluid UI homepage tiles and navigation collections, it's crucial to ensure that the foundational elements are in place and that you possess the necessary technical understanding and access. These prerequisites ensure a smooth and successful implementation:

• PeopleTools Version: Your PeopleSoft environment must be running PeopleTools 8.54 or higher. While 8.54 introduced Fluid, later versions (e.g., 8.56, 8.58, 8.60) offer significant enhancements, additional features, and improved performance for Fluid UI. It's always recommended to be on a recent PeopleTools release.
• Understanding of PeopleSoft Security: A solid grasp of PeopleSoft's security model is non-negotiable. This includes knowledge of Permission Lists, Roles, and Content References (CREFs), as security for Fluid objects is managed through these components.
• Access to Application Designer: For advanced configurations, troubleshooting, or understanding the underlying object structure, access to PeopleSoft Application Designer is essential.
• PeopleSoft Pure Internet Architecture (PIA) Access: You will need administrative access to the PeopleSoft PIA with appropriate roles, such as 'PeopleTools Administrator' or 'Portal Administrator', to access the Fluid configuration pages.
• Basic SQL Knowledge: While most configurations are done through the PIA, the ability to query PeopleTools tables using SQL can be invaluable for verification, auditing, and troubleshooting.
• Browser Compatibility: Ensure you are using a modern web browser that fully supports HTML5 and CSS3 for optimal Fluid UI rendering.

Step-by-Step Implementation: Configuring Fluid UI Homepage Tiles and Navigation Collections

This section provides a detailed, step-by-step guide to creating and securing Fluid UI homepage tiles and navigation collections. We'll walk through realistic examples to illustrate each configuration point.

Part 1: Creating a Fluid Homepage Tile

Homepage tiles are the cornerstone of the Fluid UI experience, offering users immediate access to frequently used applications or key information. They can be static (a simple link) or dynamic (displaying real-time data). We'll focus on creating a dynamic tile for a manager's "My Team" functionality.

1.1. Creating the Tile Definition using the Tile Wizard

The Tile Wizard simplifies the process of creating tile definitions. This definition specifies what the tile looks like, what it does, and how it behaves.

Navigation: PeopleTools > Portal > Tile Wizard

Here's how to configure our "My Team" dynamic tile:

• On the Tile Wizard page, select "Create a new Tile".
• Click "Next".
• Step 1: Tile Properties
  • Tile Name: MY_TEAM_TILE (This is the unique internal ID for your tile.)
  • Description: Managers' My Team Access
  • Tile Type: Dynamic (This allows the tile to display a badge count.)
  • Target Type: Component (This tile will navigate to a PeopleSoft component.)
  • Menu Name: HC_MANAGER_SELF_SERVICE (The menu where the target component resides.)
  • Component Name: HR_MSS_MYTEAM_GBL (The component to navigate to when the tile is clicked.)
  • Marketplace Tab: MANAGER_SELF_SERVICE (This helps categorize the tile in the Add Tile experience.)
  • Tile Image: PT_ARROW_ICON (You can choose from delivered images or upload custom ones.)
  • Badge Type: Count (To display a numerical badge.)
  • Badge PeopleCode: MY_TEAM_PC.GET_TEAM_COUNT (This is a hypothetical PeopleCode function. In a real scenario, you would create an Application Class PeopleCode method or a FieldFormula PeopleCode on a derived/work record that returns the count. For instance, it might count pending approvals for the manager.)
  • Click "Next".
• Step 2: Tile Layout
  • You can define the layout for different devices (Small, Medium, Large). For simplicity, we'll accept the defaults for now.
  • Click "Next".
• Step 3: Review and Save
  • Review all the details.
  • Click "Save".

The system will confirm the tile creation. This process creates an entry in the PS_HMTILEDEFN table and related records.

1.2. Creating a Content Reference for the Tile

A Content Reference (CREF) is how PeopleSoft makes any object (component, URL, tile, etc.) accessible within the portal structure and, by extension, securable. For a Fluid tile, we need a specific CREF type.

Navigation: PeopleTools > Portal > Structure and Content

Follow these steps to create the tile CREF:

• Navigate to Fluid Structure and Content > Fluid Pages. (This is a common location for Fluid tile CREFs, though you can organize them as per your portal structure.)
• Click the "Add Content Reference" link.
• Content Reference Attributes:
  • Node Name: PORTAL_ROOT_NODE (Typically, this is the default.)
  • Content Ref Name: MY_TEAM_TILE_CREF (This is the unique identifier for this CREF.)
  • Label: My Team (This is the display name for the tile.)
  • Sequence Number: 10 (For ordering within a folder, if applicable.)
  • Usage Type: Select Fluid Homepage Tile from the dropdown. This is crucial for identifying it as a tile.
• Target Content Reference:
  • Click the "Search" icon next to the "Content Reference" field.
  • In the search window, search for the "Tile ID" that matches your tile definition (MY_TEAM_TILE).
  • Select your tile definition. The field should now display Tile ID:MY_TEAM_TILE.
• Folder Properties: (Optional, but useful for organization)
  • If you want to categorize this tile within the Add Tile experience, assign it to a folder. For example, you might create a folder named "Manager Self Service Tiles".
• Click "Save".

This CREF (MY_TEAM_TILE_CREF) is now the securable object that represents your tile.

1.3. Adding the Tile to a Fluid Homepage Definition

Homepages are logical groupings of tiles. Users can have access to multiple homepages and switch between them. We'll add our new tile to the delivered "Manager Self Service" homepage.

Navigation: PeopleTools > Portal > Fluid Homepages > Homepage Definitions

Steps to add the tile to a homepage:

• Search for and select the homepage definition you want to modify, e.g., MANAGER_SELF_SERVICE.
• Go to the "Tiles" tab.
• In the "Tiles for this Homepage" grid, click the "Add" button (plus sign).
• In the new row:
  • Tile Name: Click the lookup icon and search for your tile's Content Reference name (MY_TEAM_TILE_CREF). Select it.
  • Tile Sequence: Assign a numerical sequence (e.g., 10, 20, 30) to control its position on the homepage relative to other tiles.
• Click "Save".

Now, any user with access to the MANAGER_SELF_SERVICE homepage and the MY_TEAM_TILE_CREF will see this tile.

1.4. Securing the Fluid Homepage Tile

Security is paramount. Users must have access to both the tile's CREF and the underlying component it points to.

Navigation: PeopleTools > Security > Permissions & Roles > Permission Lists

Steps to grant access:

• Open a relevant Permission List, e.g., HCDPMA1000 (a delivered permission list often associated with Manager Self Service).
• Go to the "Fluid Homepage Tiles" tab.
• Click the "Add" button.
• In the new row, click the lookup and search for your tile's Content Reference name (MY_TEAM_TILE_CREF). Select it.
• Ensure the "Authorized" checkbox is checked.
• Click "Save".

Important: You must also ensure that the same permission list (or another one assigned to the user) grants access to the *target component* (HR_MSS_MYTEAM_GBL in our example). This is done via the "Pages" tab within the Permission List, under the appropriate menu structure.

Part 2: Creating a Navigation Collection

Navigation Collections provide a structured, hierarchical way to group related links, replacing or augmenting the classic menu system in Fluid UI. They are essential for organizing a large number of components.

2.1. Defining the Navigation Collection

Navigation: PeopleTools > Portal > Nav Collections > Navigation Collections

Let's create a "HR Admin Tools" navigation collection:

• Click "Add a New Value".
• Name: HR_ADMIN_TOOLS_NAV (Unique internal identifier.)
• Description: Human Resources Administration Tools
• Click "Add".
• Now, you'll define the structure using groups and links.
• Add a Top-Level Group:
  • Click the "Add Group" button.
  • Group Label: Employee Management
  • Click "OK".
• Add Links under "Employee Management":
  • Select the "Employee Management" group you just created.
  • Click the "Add Link" button.
  • Link Type: Content Reference
  • Content Reference: Click the lookup and search for the CREF of the "Workforce Administration" component (e.g., HCMD_HR_WORKFORCE_ADMIN).
  • Label: Workforce Administration
  • Click "OK".
  • Repeat for another link:
    • Link Type: Content Reference
    • Content Reference: Search for "Job Data" component's CREF (e.g., HCMD_HR_JOB_DATA).
    • Label: Job Data
    • Click "OK".
• Add another Top-Level Group:
  • Click the "Add Group" button (at the root level).
  • Group Label: Compensation Management
  • Click "OK".
• Add Links under "Compensation Management":
  • Select the "Compensation Management" group.
  • Click the "Add Link" button.
  • Link Type: Content Reference
  • Content Reference: Search for "Compensation Data" component's CREF (e.g., HCMD_HR_COMPENSATION).
  • Label: Compensation Data
  • Click "OK".
• Click "Save".

This creates the hierarchical structure for your navigation collection, storing data in tables like PS_PTNCSGROUP and PS_PTNCSITEM.

2.2. Creating a Content Reference for the Navigation Collection

Similar to tiles, navigation collections need a CREF to be accessible and securable within the portal structure.

Navigation: PeopleTools > Portal > Structure and Content

Steps to create the navigation collection CREF:

• Navigate to where you want this collection to appear in the Navigator, e.g., Fluid Structure and Content > Navigator > HR Admin (you might need to create the 'HR Admin' folder if it doesn't exist).
• Click the "Add Content Reference" link.
• Content Reference Attributes:
  • Node Name: PORTAL_ROOT_NODE
  • Content Ref Name: HR_ADMIN_TOOLS_NAV_CREF
  • Label: HR Admin Tools
  • Usage Type: Select Fluid Navigation Collection.
• Target Content Reference:
  • Click the "Search" icon next to the "Content Reference" field.
  • In the search window, search for the "Navigation Collection Name" that matches your collection definition (HR_ADMIN_TOOLS_NAV).
  • Select your navigation collection definition. The field should now display Nav Collection:HR_ADMIN_TOOLS_NAV.
• Click "Save".

2.3. Securing the Navigation Collection

Users need security access to the navigation collection CREF to see it in their Navigator menu.

Navigation: PeopleTools > Security > Permissions & Roles > Permission Lists

Steps to grant access:

• Open a relevant Permission List, e.g., HCDPHR1000 (a delivered permission list for HR Administrators).
• Go to the "Portal Fluid" tab.
• Click the "Add" button.
• In the new row, click the lookup and search for your navigation collection's Content Reference name (HR_ADMIN_TOOLS_NAV_CREF). Select it.
• Ensure the "Authorized" checkbox is checked.
• Click "Save".

Crucial Note: Granting access to the navigation collection CREF only allows users to *see* the collection and its links. It does NOT grant access to the underlying components linked within the collection. Each component (e.g., Workforce Administration, Job Data) must be secured separately via its own CREF on the "Pages" tab of the permission list.

2.4. Verification using SQL (Optional but Recommended)

To verify the configurations at the database level, you can use SQL queries against PeopleTools tables. This is especially useful for troubleshooting or auditing.

Verifying Tile Definition:

SELECT HMTILEID, HMTILEDESCR, HMTILETYPE, PTPORTALNAME, PORTAL_OBJNAME, URL_TYPE
FROM PS_HMTILEDEFN
WHERE HMTILEID = 'MY_TEAM_TILE';

Verifying Homepage Definition and its Tiles:

SELECT HMPGNAME, HMTILEID, HMTILESEQ
FROM PS_HMPGTILE
WHERE HMPGNAME = 'MANAGER_SELF_SERVICE'
ORDER BY HMTILESEQ;

-- To get more details about the tile from its CREF
SELECT A.PORTAL_OBJNAME, A.PORTAL_LABEL, A.PORTAL_URI_TEXT, B.HMTILEID
FROM PSPRSMCURL A, PS_HMTILEDEFN B
WHERE A.PORTAL_OBJNAME = 'MY_TEAM_TILE_CREF'
AND A.PORTAL_URI_TEXT = 'Tile ID:' || B.HMTILEID;

Verifying Navigation Collection Definition:

SELECT PTNCGROUPNAME, PTNCGROUPDESCR
FROM PS_PTNCSGROUP
WHERE PTNCGROUPNAME = 'HR_ADMIN_TOOLS_NAV';

Verifying Navigation Collection Items (Links):

SELECT PTNCGROUPNAME, PTNCITEMID, PTNCITEMDESCR, PTNCPARNTITEMID, PTNCITEMTYPE, PTPORTALNAME, PORTAL_OBJNAME
FROM PS_PTNCSITEM
WHERE PTNCGROUPNAME = 'HR_ADMIN_TOOLS_NAV'
ORDER BY PTNCPARNTITEMID, PTNCITEMID;

Security Considerations

Security is paramount in any enterprise application, and PeopleSoft Fluid UI is no exception. A robust understanding and meticulous configuration of security are essential to prevent unauthorized access and maintain data integrity.

1. Content Reference (CREF) Security is the Gateway: Every Fluid UI object (tile, navigation collection, or even a classic component accessed via Fluid) must have a Content Reference (CREF). Security is applied at the CREF level through Permission Lists and Roles. If a user does not have access to the CREF, they will not see the corresponding tile or navigation collection entry, regardless of whether they have access to the underlying component.
2. Dual Security for Tiles/Collections and Components: Granting access to a Fluid Homepage Tile CREF or a Navigation Collection CREF only allows the user to *see* and *click* the tile/link. It does NOT automatically grant access to the underlying component or page that the tile/link points to. You must ensure that the permission list also grants access to the target component/pages via the "Pages" tab. Failure to do so will result in "Authorization Error -- Contact your Security Administrator" messages when users click the tile or link.
3. Homepage Security: Access to Fluid homepages themselves is also controlled by permission lists. On the "Fluid Homepages" tab within a permission list, you define which homepages a user can access and if they can personalize them (e.g., hide/show tiles, reorder).
4. Delivered vs. Custom Security: While PeopleSoft delivers many permission lists and roles, it's a best practice to create custom permission lists and roles for your specific organizational requirements. Use delivered ones as templates, but avoid modifying them directly, especially in production environments, to simplify upgrades and maintenance.
5. Dynamic Tile PeopleCode Security: If a dynamic tile uses PeopleCode to generate its badge count or content, ensure that the PeopleCode itself is secure and runs efficiently. Any data retrieved by this PeopleCode should adhere to the user's security context. Consider using Application Class PeopleCode for better organization and reusability.
6. Auditing and Review: Regularly audit and review your Fluid UI security configurations. Changes to roles, permission lists, or even the underlying content references can have ripple effects. Tools like the Security Administrator Workbench can assist in identifying potential security gaps or over-privileging.
7. Data Masking/Redaction: For sensitive HCM data displayed on dynamic tiles, consider implementing data masking or redaction techniques within the PeopleCode or underlying views to protect confidential information from unauthorized viewing, even if the tile is technically accessible.

"In the realm of PeopleSoft Fluid UI, security is not a feature; it's the foundational layer upon which the entire user experience rests. A beautifully designed Fluid interface without meticulously configured security is an open door to risk." - Someshwar Thakur

Best Practices for Fluid UI Homepage Tiles and Navigation Collections

Implementing Fluid UI is an ongoing journey. Adhering to best practices ensures optimal performance