Infolets in Oracle Fusion HCM: Complete Practical Guide for Consultants
Introduction
Infolets in Oracle Fusion HCM are one of the most powerful yet often underutilized UI components that enhance user experience by presenting key HR data in a visual, actionable format. In modern Oracle Fusion Cloud (Release 26A), Infolets play a critical role in enabling HR managers, employees, and executives to make faster decisions by surfacing real-time insights directly on the homepage.
In real implementations, Infolets are not just “nice dashboards”—they are actively used for headcount monitoring, absenteeism tracking, pending approvals, and workforce analytics. As a consultant, understanding how to configure and optimize Infolets can significantly improve user adoption.
What are Infolets in Oracle Fusion HCM?
Infolets are interactive, role-based dashboard cards that display summarized information on the Fusion homepage. Each Infolet typically shows:
- Key metrics (e.g., total employees, absences)
- Graphs or counts
- Drill-down capability to detailed transactions
They are tightly integrated with:
- OTBI (Oracle Transactional Business Intelligence)
- Workforce Structures
- Security roles
- Responsive UI framework
Think of Infolets as mini dashboards embedded directly into the user experience, reducing dependency on separate reports.
Key Features of Infolets
1. Role-Based Personalization
Infolets are displayed based on:
- User role (HR Specialist, Line Manager, Employee)
- Data security profiles
👉 Example: A Line Manager sees team absences, while HR sees organization-wide data.
2. Real-Time Data Visualization
- Displays live data from OTBI
- Supports charts, counts, and KPIs
3. Drill-Down Capability
Users can click an Infolet to:
- Open detailed reports
- Navigate to transaction pages
4. Responsive UI (Mobile + Desktop)
- Works seamlessly across devices
- Critical for executives accessing dashboards on mobile
5. Configurable and Extendable
- Can be customized using Page Composer
- Supports personalization at:
- Site level
- Role level
- User level
Real-World Business Use Cases
Use Case 1: HR Head Monitoring Workforce Trends
A global HR head wants to track:
- Total headcount
- New hires this month
- Attrition rate
👉 Infolets provide a quick snapshot without running reports.
Use Case 2: Line Manager Tracking Team Absences
Managers need visibility into:
- Pending leave requests
- Team availability
👉 Infolets show:
- Absences by type
- Pending approvals
Use Case 3: Recruitment Dashboard for HR Teams
Recruitment teams use Infolets to track:
- Open requisitions
- Candidates in pipeline
- Offer acceptance rate
Use Case 4: Payroll Monitoring
Payroll teams monitor:
- Pending payroll actions
- Errors or exceptions
Configuration Overview
Before configuring Infolets, ensure the following prerequisites are in place:
| Configuration Area | Details |
|---|---|
| OTBI Reports | Required for data source |
| Security Roles | Determines visibility |
| Workforce Structures | Departments, Business Units |
| Data Security | Ensures correct data visibility |
| Page Composer Access | Required for customization |
Step-by-Step Configuration of Infolets
Step 1 – Navigate to Infolets Page
Navigation Path:
Navigator → Home → Me → Personalization → Page Composer
Step 2 – Enable Sandbox (Recommended)
Before making changes:
Navigator → Configuration → Sandboxes
Create a Sandbox → Activate
👉 Always configure Infolets in sandbox to avoid production issues.
Step 3 – Access Infolets Page Layout
- Open homepage
- Click Edit Page in Page Composer
You will see:
- Infolets container
- Individual Infolet cards
Step 4 – Add or Modify Infolet
Options available:
- Add new Infolet
- Modify existing Infolet
- Hide unnecessary Infolets
Step 5 – Link Infolet to OTBI Report
Each Infolet is powered by an OTBI analysis.
Example:
- Create OTBI Report:
- Subject Area: Workforce Management – Worker Assignment Real Time
- Metrics: Employee Count by Department
- Link this report to Infolet
Step 6 – Configure Infolet Properties
Key fields to configure:
| Field | Description |
|---|---|
| Title | Name of Infolet |
| Data Source | OTBI report |
| Visualization | Count / Graph |
| Drill Down URL | Target page |
| Refresh Frequency | Real-time / scheduled |
Step 7 – Save and Publish
- Save changes
- Exit Page Composer
- Publish sandbox
Testing the Infolet Setup
Test Scenario
Objective: Validate headcount Infolet
Steps:
- Login as HR Manager
- Navigate to homepage
- Verify:
- Headcount number
- Graph accuracy
Expected Results
- Infolet shows correct employee count
- Drill-down opens detailed report
- Data matches OTBI output
Validation Checks
- Compare with OTBI report manually
- Check role-based visibility
- Validate performance (load time)
Architecture / Technical Flow
Understanding backend flow helps in troubleshooting.
Flow:
- User logs into Fusion
- Homepage loads Infolets container
- Infolet calls OTBI report
- OTBI fetches data from HCM tables
- Data is rendered as visualization
Common Implementation Challenges
1. Data Mismatch with OTBI
Cause:
- Incorrect filters in OTBI
Solution:
- Validate report filters and subject area
2. Infolet Not Visible
Cause:
- Role or data security issue
Solution:
- Check role mapping and security profiles
3. Performance Issues
Cause:
- Heavy OTBI queries
Solution:
- Optimize report
- Avoid complex joins
4. Drill-Down Not Working
Cause:
- Incorrect navigation URL
Solution:
- Validate target page URL
5. Sandbox Changes Not Reflecting
Cause:
- Sandbox not published
Solution:
- Publish sandbox and re-login
Best Practices from Real Implementations
1. Keep Infolets Minimal
Avoid cluttering homepage with too many Infolets.
👉 Ideal: 6–8 Infolets per role
2. Use Optimized OTBI Reports
- Avoid unnecessary columns
- Use indexed fields
3. Design Role-Based Dashboards
Different roles should have different Infolets.
Example:
- HR: Workforce analytics
- Manager: Team metrics
- Employee: Personal data
4. Use Clear Naming Conventions
Example:
- “Team Absence Summary”
- “Monthly Hiring Overview”
5. Enable Drill-Down Navigation
Always provide actionable insights.
6. Test Across Roles
Always validate:
- HR role
- Manager role
- Employee role
7. Use Sandbox for All Changes
Never modify Infolets directly in production.
Real Implementation Scenario (Consultant Perspective)
In one enterprise project:
- Client: 25,000 employees
- Requirement: Executive dashboard
We implemented:
| Infolet | Purpose |
|---|---|
| Headcount | Total employees |
| Attrition | Monthly attrition |
| Hiring | New hires |
| Absence | Leave trends |
Outcome:
- Reduced dependency on reports
- Improved decision-making speed
- Increased user adoption
Frequently Asked Questions (FAQ)
1. Can Infolets be customized for different roles?
Yes. Infolets are role-based and can be personalized using Page Composer and security roles.
2. What is the data source for Infolets?
Infolets primarily use OTBI reports as their data source.
3. Can we create custom Infolets?
Yes. You can create custom Infolets by:
- Designing OTBI reports
- Linking them via Page Composer
Summary
Infolets in Oracle Fusion HCM are a critical UI and analytics component that enhances decision-making and user experience. From real-world implementations, it’s clear that well-designed Infolets:
- Reduce reporting dependency
- Improve productivity
- Provide real-time insights
As a consultant, your focus should be on:
- Designing role-based dashboards
- Optimizing OTBI reports
- Ensuring performance and usability
For deeper technical reference, always refer to Oracle’s official documentation:
https://docs.oracle.com/en/cloud/saas/index.html