PeopleSoft HCM 9.2 Fluid UI: Mastering Homepage Tiles & Nav Collections

Unlocking User Productivity: A Deep Dive into Oracle PeopleSoft HCM 9.2 Fluid UI Homepage Tiles and Navigation Collections

As organizations continue their journey towards digital transformation, the user experience within enterprise applications has become paramount. Oracle PeopleSoft HCM 9.2, with its responsive and intuitive Fluid User Interface (UI), stands at the forefront of this evolution, offering a personalized and engaging experience. At the heart of Fluid UI's effectiveness lie two critical components: Homepage Tiles and Navigation Collections. These elements are not just aesthetic enhancements; they are powerful tools for streamlining navigation, improving access to critical information, and significantly boosting user productivity. As a senior technology writer at TechNews Venture, I’ve witnessed firsthand how a well-designed Fluid interface can revolutionize how employees interact with their HR systems.

This article will provide a comprehensive, technical exploration of PeopleSoft HCM 9.2 Fluid UI homepage tiles and navigation collections, detailing their architecture, implementation, security considerations, and best practices. We will delve into the practical steps required to configure these elements, ensuring your PeopleSoft environment delivers an optimal user experience.

Overview: The Architecture of Fluid UI Navigation

The Oracle PeopleSoft HCM 9.2 Fluid UI: Tiles & Nav Collections Guide">PeopleSoft Fluid UI represents a fundamental shift from the classic, menu-driven interface to a modern, tile-based paradigm optimized for various devices, from desktops to smartphones. This change is more than skin deep; it impacts how users discover and interact with functionalities. Homepage Tiles and Navigation Collections are the cornerstones of this new navigation model.

Homepage Tiles: Your Gateway to Key Actions

A Fluid UI homepage is a customizable dashboard composed of tiles. Each tile is a visually distinct, clickable element that serves as a direct link to a specific PeopleSoft page, component, external URL, or even a summary of real-time data (dynamic tiles). Tiles simplify navigation by bringing frequently used applications and critical information directly to the user's fingertips, eliminating the need to traverse complex menu paths.

Tiles can be:

• Static Tiles: Simply launch a component, page, or URL. They display a fixed label and image.
• Dynamic Tiles: Display real-time data, such as counts of pending approvals, unread notifications, or employee self-service tasks. These tiles often leverage PeopleSoft Query or custom PeopleCode to fetch and present data.

Navigation Collections: Structured Access to Related Content

While tiles offer direct access, Navigation Collections provide a structured, hierarchical way to group related content. Think of them as modern, customizable menus within a tile. A Navigation Collection can be exposed as a tile on a homepage, or accessed via the NavBar (Navigator icon). When a user clicks a Navigation Collection tile, they are presented with a list of links, often organized into folders, leading to various PeopleSoft pages or external resources. This is particularly useful for roles that require access to a broad set of related functionalities, such as HR Administrators or Payroll Specialists.

The synergy between tiles and navigation collections creates a highly flexible and efficient navigation experience. Tiles serve as high-level entry points, and navigation collections provide the detailed pathways once a specific functional area is chosen.

Prerequisites for Implementation

Before embarking on the configuration of Fluid UI homepage tiles and navigation collections, ensure the following prerequisites are met:

• PeopleTools Version: PeopleSoft HCM 9.2 requires PeopleTools 8.55 or higher for full Fluid UI capabilities. Later PeopleTools versions (e.g., 8.58, 8.59, 8.60) introduce further enhancements and performance improvements.
• Application Designer Access: Developers and administrators will need access to PeopleSoft Application Designer to create and modify Content References (CREFs), which are the underlying objects for tiles and navigation items.
• PeopleSoft Security Knowledge: A solid understanding of PeopleSoft security, including Permission Lists, Roles, and User Profiles, is crucial for controlling access to homepages, tiles, and navigation collections.
• Portal Technology Understanding: Familiarity with PeopleSoft Portal concepts, such as Content References, Folders, and Homepages, is beneficial.
• Web Server and Application Server Configuration: Ensure your web and application servers are properly configured and running to support Fluid UI. This typically involves deploying the necessary web profiles and services.
• Browser Compatibility: Users should be using modern web browsers (Chrome, Firefox, Edge, Safari) that are officially supported by Oracle for PeopleSoft Fluid UI.

Step-by-Step Implementation: Configuring Tiles and Navigation Collections

This section will walk through the practical steps to create and configure both static and dynamic tiles, custom homepages, and navigation collections.

1. Creating a Static Homepage Tile

Static tiles are the simplest to implement and are ideal for direct links to frequently used components.

1.1 Identify the Target Content Reference (CREF)

Every PeopleSoft page or component that you want to link to via a tile must have an existing Content Reference in the Portal Registry. For example, to link to the "Personal Details" page (component `HCD_PER_ORG_DATA_FL`), you would typically navigate to:

PeopleTools > Portal > Structure and Content > Fluid Structure Content > Fluid Pages > Employee Self Service > Personal Details

Note down the CREF Name (e.g., `HCD_PERSONAL_DETAILS_FL`) and its path. If a CREF doesn't exist for your target, you'll need to create one in Application Designer or via Structure and Content.

1.2 Use the Tile Wizard to Create a New Tile

The Tile Wizard simplifies the process of creating a new tile and its associated CREF.

• Navigate to: PeopleTools > Portal > Tile Wizard
• Click Add a New Value.
• Enter a Tile Name (e.g., TECHNEWS_PERSONAL_DETAILS) and Description.
• Click Add.
• Step 1: Choose Tile Type: Select Static Tile. Click Next.
• Step 2: Tile Content:
  • Application Class: Leave blank for static tiles.
  • Component: Enter the target component name (e.g., HCD_PER_ORG_DATA_FL).
  • Menu Name: Enter the menu name (e.g., HCD_EMPLOYEE_SELF_SERVICE).
  • Marketplace Name: Leave blank.
  • Portal Name: EMPLOYEE (or your custom portal).
  • Node Name: HRMS (or your custom node).
  • Page Name: (Optional) If linking to a specific page within the component.
  • Action: A (Add), U (Update/Display), C (Correction). Typically U.
  • Query Name: Leave blank.
  • External URL: Leave blank.
  Click Next.
• Step 3: Tile Display:
  • Tile Label: "My Personal Details"
  • Tile Description: "View and update your personal information"
  • Tile Icon: Choose an icon from the PeopleSoft icon library (e.g., PSE_EMPLOYEE_PROFILE).
  • Tile Image: (Optional) Upload a custom image.
  • Tile Class: (Optional) For custom styling.
  Click Next.
• Step 4: Tile Options:
  • Tile Size: Medium (default).
  • Header Label: (Optional)
  • Show Header: (Optional)
  • Cache Tile: (Recommended for static tiles).
  Click Next.
• Step 5: Tile Security:
  • Permission List: Add the permission list(s) that should have access to this tile (e.g., PTPT1000 or a custom permission list like TECHNEWS_ESS_PL).
  Click Next.
• Step 6: Review and Save: Review all settings. Click Save. The wizard will create the necessary CREF under Fluid Structure Content > Fluid Homepages > Tiles.

1.3 Verify the Tile Content Reference in Structure and Content

You can verify the created CREF by navigating to:

PeopleTools > Portal > Structure and Content > Fluid Structure Content > Fluid Homepages > Tiles > TECHNEWS_PERSONAL_DETAILS

Ensure the Folder URL, Content URL, and Security tabs are correctly configured. The Security tab should list the permission lists assigned in the wizard.

2. Creating a Dynamic Homepage Tile

Dynamic tiles provide real-time information, often relying on PeopleSoft Query or PeopleCode.

2.1 Example: Pending Approvals Tile

Let's create a tile that displays the count of pending approvals for the current user.

2.2 Create a PeopleSoft Query (Optional, but common)

If your dynamic data requires complex filtering or aggregation, a PeopleSoft Query is often the easiest approach. For pending approvals, however, PeopleCode directly querying a worklist table might be more efficient.

2.3 Create an iScript/Application Class for Dynamic Content

Dynamic tiles typically use an iScript or an Application Class to fetch data.

Example PeopleCode (Application Class Method):

class TECHNEWS_TILE_APPR:TILES:PendingApprovalsTile extends PT_PORTAL_FLUID:HOME:Tile;
   method GetTileContent(&Tile);
   method GetTileCount(&Tile);
end-class;

method GetTileContent(&Tile)
   /* This method returns the HTML content for the tile. */
   Local number &pendingCount;
   &pendingCount = %This.GetTileCount(&Tile);
   &Tile.SetProperty(&Tile.Property_TileValue, String(&pendingCount));
   &Tile.SetProperty(&Tile.Property_TileValueLabel, "Pending Approvals");
   &Tile.SetProperty(&Tile.Property_TileValueCSSClass, "psc_tile-value-accent");
end-method;

method GetTileCount(&Tile)
   /* This method fetches the actual count from the database. */
   Local SQL &sql;
   Local number &count;

   &sql = CreateSQL("SELECT COUNT(*) FROM PS_EOAW_WL WHERE OPRID = :1 AND EOAWSTATUS = 'P'", %CurrentUserId);
   &sql.Fetch(&count);
   Return &count;
end-method;

Save this PeopleCode in an Application Package (e.g., TECHNEWS_TILE_APPR) and Class (TILES:PendingApprovalsTile).

2.4 Use the Tile Wizard to Create a Dynamic Tile

• Navigate to: PeopleTools > Portal > Tile Wizard.
• Click Add a New Value. Enter a Tile Name (e.g., TECHNEWS_PENDING_APPR) and Description.
• Step 1: Choose Tile Type: Select Dynamic Tile. Click Next.
• Step 2: Tile Content:
  • Application Class: TECHNEWS_TILE_APPR:TILES:PendingApprovalsTile
  • Application Class Method: GetTileContent
  • Component/Menu/Page/Action: (Specify the target component for when the user clicks the tile, e.g., EOAW_APPROVAL_MON for Approval Monitor).
  Click Next.
• Step 3: Tile Display:
  • Tile Label: "My Approvals"
  • Tile Description: "View and act on pending approvals"
  • Tile Icon: Choose an appropriate icon (e.g., PSE_NOTIFICATION_BELL).
  Click Next.
• Complete Steps 4, 5, and 6 similar to the static tile, ensuring security is correctly applied.

3. Creating a Custom Homepage

Users can personalize their homepages, but administrators can also define default homepages and assign them to roles.

• Navigate to: PeopleTools > Portal > WorkCenter > Manage WorkCenters / Dashboards > Manage Pages.
• Click Add a New Value.
• Enter Page Name (e.g., TECHNEWS_ESS_HOMEPAGE) and Description.
• Select a Page Layout (e.g., Single Column, Two Column).
• Click Save.
• You can then add default tiles to this homepage by clicking Add Tile and selecting from the available tiles.

4. Assigning Homepages and Tiles to Users

4.1 Assigning Tiles to Homepages (User Personalization)

Users can add tiles to their personal homepages:

• From any Fluid homepage, click the Personalize Homepage icon (pencil icon).
• Click Add Tile.
• Browse or search for the desired tile (e.g., "My Personal Details", "My Approvals").
• Click Add next to the tile.
• Click Save.

4.2 Assigning a Default Homepage to a Permission List

To make a custom homepage the default for a group of users:

• Navigate to: PeopleTools > Security > Permissions & Roles > Permission Lists.
• Open the relevant permission list (e.g., PTPT1000 or TECHNEWS_ESS_PL).
• Go to the Fluid Homepages tab.
• Add your custom homepage (e.g., TECHNEWS_ESS_HOMEPAGE).
• Check the Default Homepage checkbox if this should be the primary homepage.
• Ensure the permission list is assigned to the appropriate roles and users.

5. Creating a Navigation Collection

Navigation Collections provide structured access to a group of related links.

• Navigate to: PeopleTools > Portal > Navigation Collections.
• Click Add a New Value.
• Enter Collection Name (e.g., TECHNEWS_HR_ADMIN_NC) and Description.
• Click Add.
• Collection Structure:
  • Click Add Folder to create logical groupings (e.g., "Employee Management", "Payroll Processing").
  • Select a folder, then click Add Link.
  • In the Add Link dialog, browse for the target Content Reference (CREF) for the PeopleSoft page/component you want to add (e.g., HCD_PER_ORG_DATA_FL for Personal Details, or a custom component).
  • Repeat for all desired links and folders.
• Collection Options:
  • Active: Ensure it's checked.
  • Display Type: Folder View (default, hierarchical) or List View.
  • Display in NavBar: Check this if you want it to appear directly in the NavBar (under Navigator).
• Security:
  • Go to the Security tab.
  • Add the permission list(s) that should have access to this Navigation Collection (e.g., TECHNEWS_HRADMIN_PL).
• Click Save.

6. Exposing a Navigation Collection as a Tile

To make a Navigation Collection easily discoverable, you can create a tile that links to it.

• Navigate to: PeopleTools > Portal > Tile Wizard.
• Click Add a New Value. Enter a Tile Name (e.g., TECHNEWS_HR_ADMIN_TILE) and Description.
• Step 1: Choose Tile Type: Select Static Tile. Click Next.
• Step 2: Tile Content:
  • Application Class: Leave blank.
  • Component: PT_NAVCOLL_FL (This is the generic component for displaying Navigation Collections).
  • Menu Name: PTPN_MENU
  • Action: U
  • Page Name: PT_NAVCOLL_SCF_FL
  • Content Reference Parameters: NAVCOL_NAME=TECHNEWS_HR_ADMIN_NC (Replace with your collection name).
  Click Next.
• Complete the remaining steps (Tile Display, Options, Security, Review) as you would for any static tile. Ensure the security for this tile aligns with the security of the underlying Navigation Collection.

Security Considerations

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

• Content Reference Security: Every tile and every link within a Navigation Collection ultimately points to a Content Reference (CREF). The security for these underlying CREFs (defined via Permission Lists in Application Designer or Structure and Content) is paramount. If a user does not have security to the underlying CREF, clicking the tile or link will result in an authorization error, even if they can see the tile/link.
• Tile Security: Each tile itself has security defined at its CREF level (as configured in the Tile Wizard or Structure and Content). Users must have access to the tile's CREF to even see the tile on their homepage.
• Homepage Security: Custom homepages must be assigned to permission lists. Users without access to a specific homepage cannot set it as their default or personalize it.
• Navigation Collection Security: The Navigation Collection itself has security defined on its main CREF. If a user lacks this security, they cannot view the collection, even if they have access to individual links within it.
• Role-Based Access: Always assign permission lists to roles, and roles to users. Avoid assigning permission lists directly to users. This promotes a cleaner, more manageable security model.
• Row-Level Security: Remember that Fluid UI navigation only controls *access* to pages/components. Once a user is on a page, row-level security (e.g., Department Security Tree, Data Permissions) still applies to control *what data* they can see or modify.
• Regular Audits: Periodically review tile and navigation collection assignments and their underlying CREF security to ensure they align with current business requirements and security policies.

Expert Tip: When troubleshooting missing tiles or navigation items, always start with security. Verify that the user has access to the tile's CREF, the homepage's CREF (if applicable), and all CREFs within a navigation collection. Clear application server and web server cache after any security or portal registry changes.

Best Practices

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

• User-Centric Design: Involve end-users in the design process. Understand their workflows and frequently used tasks to create relevant homepages and tiles. Group related functionalities logically.
• Consistent Naming Conventions: Establish clear and consistent naming conventions for tiles, homepages, and navigation collections (e.g., TECHNEWS_TILE_APPROVE, TECHNEWS_HP_ESS, TECHNEWS_NAV_HRADMIN). This aids in maintenance and understanding.
• Optimize for Performance:
  • Dynamic Tiles: Design dynamic tiles efficiently. Avoid complex or long-running queries/PeopleCode that could impact page load times. Cache results where appropriate.
  • Number of Tiles: Keep the number of tiles on a single homepage manageable. Too many tiles can overwhelm users and slow down initial page loads. Leverage navigation collections for deeper content.
  • Images/Icons: Optimize tile images for web use (appropriate size and resolution).
• Clear Labels and Descriptions: Use concise, descriptive labels for tiles and navigation items. The tile description should quickly convey its purpose.
• Leverage Personalization: While providing default homepages and tiles, empower users to personalize their experience by adding, removing, and rearranging tiles.
• Mobile Responsiveness: Test your Fluid UI configuration on various devices (desktop, tablet, mobile) to ensure a consistent and usable experience across all platforms.
• Branding and Styling: Utilize PeopleSoft's branding capabilities to align the Fluid UI with your organization's look and feel. Custom CSS can be applied for specific tile styles or themes.
• Documentation: Maintain thorough documentation of your Fluid UI configuration, including CREF paths, security assignments, and any custom PeopleCode.
• Regular Review and Maintenance: Periodically review your Fluid UI setup. Remove outdated tiles or navigation collections, update links, and incorporate user feedback.

Frequently Asked Questions (FAQ)

Q1: How can I troubleshoot why a user cannot see a specific tile on their homepage?

A1: This is almost always a security issue or a caching problem. Follow these steps:

1. Clear Cache: Ask the user to clear their browser cache. As an administrator, clear the web server and application server cache (PeopleTools > Portal > Portal Utilities > Clear Cache).
2. Verify Tile CREF Security:
   • Go to PeopleTools > Portal > Structure and Content > Fluid Structure Content > Fluid Homepages > Tiles and locate the tile's CREF.
   • Click on the Security tab. Ensure the user's permission list(s) (via their role) are listed and have Public Access or Authorized checked.
3. Verify Homepage CREF Security (if a custom homepage):
   • Go to PeopleTools > Portal > WorkCenter > Manage WorkCenters / Dashboards > Manage Pages and locate the homepage.
   • Ensure the user's permission list is assigned to this homepage and has Access checked.
4. Verify Underlying Component/Page CREF Security: If the tile links to a PeopleSoft component, ensure the user has security to that component's CREF in the Portal Registry.
5. Check User's Personalization: Has the user accidentally hidden the tile or removed it from their personalized homepage?

Q2: Can I create a tile that launches an external website or application?

A2: Yes, absolutely. When using the Tile Wizard or manually creating a Content Reference for a tile:

• In Step 2: Tile Content of the Tile Wizard (or in the Content Ref Administration page of Structure and Content):
• Select External URL as the Type.
• Enter the full URL (e.g., https://www.technewsventure.com) in the External URL field.
• Ensure the URL Type is set to External.

This allows you to seamlessly integrate external resources into the Fluid UI experience.

Q3: How do I ensure my dynamic tile updates automatically without manual refresh?

A3: Dynamic tiles in Fluid UI are designed to refresh periodically. The refresh interval is controlled by the Cache Tile and Refresh Interval settings on the Tile CREF (or in the Tile Wizard, Step 4: Tile Options).

• Cache Tile: For dynamic tiles, it's often set to 'No' if real-time data is critical, or to 'Yes' with a short refresh interval if some caching is acceptable.
• Refresh Interval: This specifies how often the tile's content should be refreshed, in minutes. For example, setting it to 5 will refresh the tile every 5 minutes.

For critical, near real-time updates (e.g., workflow approvals), ensure the refresh interval is set appropriately. If the tile still doesn't update, verify your PeopleCode or PeopleSoft Query logic for fetching the dynamic content is correct and efficient.

Conclusion

Oracle PeopleSoft HCM 9.2 Fluid UI homepage tiles and navigation collections are more than just cosmetic upgrades; they are fundamental components that redefine how users interact with their HR systems. By providing intuitive, personalized, and role-based access to critical functions and information, they significantly enhance user productivity and satisfaction. A well-executed Fluid UI strategy, built upon a solid understanding of these components, their configuration, and the underlying security framework, transforms the PeopleSoft experience from a transactional system into an engaging and indispensable daily tool. As organizations continue to seek efficiency and user empowerment, mastering these Fluid UI elements will be key to unlocking the full potential of their PeopleSoft HCM investment.