What's New in Oracle Field Service Release 26B

This release delivers a meaningful mix of AI capability and solid platform integration work — the kind of improvements that make day-to-day field operations smoother and give mobile workers better tools before they've even left the depot. Oracle have continued to invest in agentic AI for Field Service, and there's also a raft of foundational integration enhancements for organisations running Field Service alongside HCM, Inventory, and Procurement.

I've split the highlights into AI Related Features and Core Features to make it easy to navigate. I've also flagged an important deprecation notice you shouldn't miss. Let's get into it.

AI Related Features

Start of the Day Mobile Worker Pre-brief

This is the standout feature of the 26B release, and one I'll be recommending to clients running Field Service with Fusion Inventory. Starting with 26B, an AI-powered pre-brief is available on the My Route page to help mobile workers prepare for their day. The AI agent scans configured inventory locations, automatically reserves available parts for the day's work orders, and highlights any shortages — all before the worker has left for their first job.

When required parts for any work orders in the route are unavailable, a Missing Required Parts section appears at the top of the My Route page, showing each item, the required quantity, the associated work order, and its reservation status. The section stays visible until the route is activated, giving workers and dispatchers a clear picture of what needs to be sorted before the day kicks off. The AI agent works through a priority order — checking Technician stocking locations first, then Manned, Unmanned, and Site Dedicated locations.

The business case is compelling: fewer delays in the field, higher first-time fix rates, and a better customer experience. A few things to note for implementation:

• This feature is available in Oracle Fusion Field Service only and must be enabled via the FSM flag ORA_FFS_START_OF_DAY_BRIEF.
• Setup requires configuring AI Agent roles, permission groups, and data security policies — it's not a one-click enable, so plan this into your upgrade testing cycle.
• The AI agent currently supports responses in English only.

Core Features

Native Fusion Inventory Support

This is the headline feature for me in 26B. Field Service users can now search for and install Fusion Inventories directly from within the Oracle Field Service application — no OIC accelerator required. That's a meaningful simplification for organisations that have been managing this through middleware.

Once Stocking Locations are configured via Oracle Fusion Service Logistics, mobile workers can access inventory with positive balances from their assigned locations through the Debrief page. Search is available by item number, description, or serial number, and critically — it works offline after data has been loaded. When an item is recorded in a Service Work Order debrief, the quantity is automatically deducted, keeping inventory positions accurate without manual reconciliation. This is the kind of native, end-to-end integration that customers have been asking for, and it's great to see it land.

Update Labor Hours to Oracle Time and Labor Using Debrief

Another integration I'm genuinely excited to see — Oracle Field Service now has a native connection to Oracle Fusion Cloud HCM Time and Labor (OTL). Mobile workers can capture their labor hours as part of the standard Debrief workflow in the Field Service mobile app, and those hours are submitted directly to OTL as time card entries.

The business case for this is clear: it eliminates dual entry, removes the need for separate mobile applications just for time capture, and brings Field Service labor data into the OTL compliance and approval framework — including validation rules, approval workflows, and downstream payroll and project costing. A couple of things worth noting for implementation:

• This integration currently supports project-based activities only — activities from Fusion Service work orders or Maintenance work orders are not supported in this release.
• If a mobile device is offline, Debrief will queue the OTL submission and automatically post once connectivity is restored. There's also a built-in retry mechanism for failed posts, with a default 24-hour retry window.
• Setup is required — you'll need to configure OTL time entry layout components and set a plugin parameter for Work Type values. Worth planning this into your upgrade checklist.

After-Hours Plugin Support for 24/7 Operations

This one is a bigger deal than the release notes might suggest. Many Field Service customers use custom plugins instead of the standard Complete Activity page — particularly those running 24/7 or multi-day field operations. Previously, there were limitations around what plugin actions could be performed during the overnight period. With 26B, that gap is closed.

The enhancement supports a configurable window (defined by the Allow offline sync and update activities after overnight Business Rules setting) during which plugins can finalise in-progress activities, update activity and inventory fields, and perform standard inventory actions including create, install, deinstall, and undo operations. A new updateAllowed parameter in the Plugin API tells your plugin whether it's within the permitted window, which is a clean way to handle the logic. This enables existing plugin investments to behave consistently with the standard pages and REST API — something that's been a frustration point in complex custom implementations.

Message Management in Collaboration

The Collaboration feature gets a meaningful quality-of-life upgrade in 26B. Users can now edit or delete messages they've sent — within a 15-minute window — and reply directly to specific messages in a conversation thread. These capabilities are available on both desktop and mobile.

It might sound minor, but in fast-paced field operations where dispatchers and technicians are communicating constantly, the ability to correct a message or provide context against a specific earlier message makes a real difference to communication accuracy. The reply-to functionality is particularly useful in active group chats where multiple threads of discussion can run simultaneously. No setup required — this one just lands with the upgrade.

Streamlined API Access — No Additional Configuration Required

A welcome simplification for anyone managing Fusion Field Service integrations. Fusion Field Service now supports OAuth authentication via the Client Credentials grant type from Fusion IAM — the same identity platform used across all other Fusion Applications. As part of this change, the separate "Field Service API" configuration option has been removed from the REST/SOAP API Application Configuration page for Fusion Field Service environments.

In practice, this means all API access configuration is now managed centrally in Fusion IAM, consistent with the broader Fusion platform. It reduces administrative overhead, eliminates duplicate setup, and lowers the risk of configuration errors. No action is required to enable this — it's in place with the 26B upgrade.

Role-Based Access to Collaboration and Rescheduling APIs

For organisations with custom integrations touching Collaboration or rescheduling-related APIs, this is an important governance enhancement. 26B introduces Permission Groups for these APIs, enabling administrators to assign highly targeted access to specific job or duty roles through the Security Console.

Rather than over-provisioning broad API access, you can now grant roles exactly the API operations they require — whether that's reading the address book, creating chats, moving activities, or cancelling activities. External applications authenticating via OAuth 2.0 will need to have the relevant permission groups assigned before calling these endpoints, so this is worth reviewing as part of your post-upgrade validation. There are also some permission group renames from earlier releases to be aware of if you're upgrading from prior configurations.

New Routing Configuration and Reporting APIs

For teams managing routing programmatically — or looking to integrate Field Service routing with Oracle Fusion AI Studio — this release adds a comprehensive set of new public Routing API endpoints. Key additions include the ability to retrieve routing profiles and their associated buckets, pull routing run summaries and detailed assignment metrics, and import/export routing plans in an AI-friendly JSON format.

The import/export endpoints are particularly interesting for organisations using AI Studio to manage routing plan changes — plans can be exported without the signature lock of the previous V1 endpoint, modified programmatically, and re-imported cleanly. The reporting endpoints provide granular visibility into routing run outcomes, including which activities were assigned, reassigned, reordered, or left unassigned — and why. Setup is minimal; standard platform authentication is all that's required.

Capacity Categories Configuration Moved to Quota-Capacity Workflow

A smaller administrative improvement, but worth noting: capacity categories configuration has been moved to the Quota-Capacity workflow in 26B. This consolidates related configuration in a more logical location and is part of Oracle's broader effort to streamline the Field Service administration experience. No setup required.

Links to Release Documentation

I've covered the features I think matter most in 26B, but there's plenty more detail in Oracle's official readiness documentation. I'd strongly encourage you to review the full release notes — particularly the configuration guidance for the OTL integration and the new Routing APIs if those are relevant to your environment.

• Oracle Fusion Field Service 26B Feature Summary
• Fusion Inventory Support
• Update Labor Hours to Oracle Time and Labor Using Debrief
• Plugin API After-Hours Support
• Routing Configuration and Reporting APIs

Why Kyte?

At Kyte, we're Oracle specialists — and we've been delivering Field Service implementations for clients across Australia for years. Our team runs on AI, which means every phase of your Oracle engagement moves faster: requirements gathered more efficiently, documentation generated automatically, testing accelerated, and change management sharper. You get senior Oracle experts from day one — not junior staff after the contract is signed.

We're 100% Australian owned and operated, headquartered in Melbourne with offices in Sydney, Canberra, Perth, and Adelaide. Every client we've ever worked with will take your call — that's not a promise, it's our track record. If you'd like to talk through what Oracle Field Service 26B means for your environment, start a conversation with our team.

Author: Alf Martin — Capability Lead (Field Services and Asset Management)