Showing posts with label Oracle Fusion HCM. Show all posts
Showing posts with label Oracle Fusion HCM. Show all posts

August 31, 2026

Connecting External APIs to Oracle HCM Using VBCS Service Connections

Oracle Visual Builder Cloud Service (VBCS) is a powerful tool for extending HCM with custom UI components. One of its most useful features is the Service Connection — it lets you call any REST API and display the results directly within your HCM pages.

When to Use VBCS Service Connections

  • Displaying predictions from an ML model (e.g. attrition risk score)
  • Pulling data from a third-party HR system in real-time
  • Triggering an external workflow from within HCM
  • Showing live leave balances from a custom calculation engine

Creating a Service Connection — Steps

  1. Open VBCS → Navigate to your application → Services tab
  2. Click + Service Connection → Choose Define by Endpoint
  3. Enter your REST API URL (e.g. your Azure ML endpoint)
  4. Set Authentication: Bearer Token or Basic Auth depending on your API
  5. Define the Request schema (JSON body) and Response schema
  6. Click Test to verify the connection returns expected data
  7. Bind the response fields to your page components
// Example request payload for Azure ML attrition endpoint
{
  "input_data": {
    "columns": ["tenure_months","absence_count","perf_rating","grade"],
    "data": [[36, 8, 3, "M3"]]
  }
}
// Response
{ "result": [0.73] // 73% attrition risk }
✦ Always handle the case where the external API is unavailable. Add a fallback value or a "Data not available" message in your VBCS component — otherwise the HCM page will show a blank tile with no explanation.

Migrating to Oracle Redwood UI — A Practical Checklist from the Field

Oracle's Redwood UI is the new standard for Fusion HCM. If your organization is still on the classic UI, migration is inevitable. Here is the practical checklist I used — tested against a real implementation.

Phase 1 — Audit Your Current Configuration

  • List every custom page layout and flexfield configuration
  • Identify personalizations that will not carry over automatically
  • Document all custom BIP reports that display within HCM pages
  • Note any third-party integrations that depend on classic UI URLs

Phase 2 — Enable Redwood in Sandbox

Navigate to Setup and Maintenance → Manage Administrator Profile Values. Search for the profile option HCM_EXPERIENCE_DESIGN_MODE and set it to REDWOOD at the Site level — in Sandbox only first.

✦ Never enable Redwood in Production before completing a full regression test in Sandbox. Some workflows behave differently, especially absence and performance forms.

Phase 3 — Test High-Traffic Pages First

PageTest FocusRisk Level
My Team → AbsenceAbsence request flow end-to-endHigh
Performance → Goal SettingGoal creation and approval chainHigh
Payslip viewRendering and downloadMedium
Learning → My CoursesCourse launch and completionMedium
Directory searchSearch results and person cardLow

Phase 4 — Promote to Production

After sign-off in Sandbox: enable Redwood at Site level in Production during a low-traffic window. Prepare a rollback plan — you can revert the profile option if critical issues arise.

The Biggest Lesson

The technical switch takes minutes. The people side takes weeks. Invest in quick reference cards and short demo videos for end users — these reduce helpdesk tickets by more than any technical preparation.

Generating Multi-Sheet Excel Reports from Oracle HCM Using BI Publisher (BIP)

Standard OTBI outputs are flat tables. When stakeholders need data across multiple dimensions in separate sheets — say, one sheet per depart...