What's New in Oracle Field Service Release 26C

OVERVIEW

There's also a meaningful step forward for Fusion Service integration, a first look at AI agents inside Collaboration, and the Travel Area transition that started in 26B finally reaches its conclusion.

This document groups what follows into AI-related features and core platform features, and flags the one item every Oracle Field Service customer needs to check off before this release lands in their environment.

Important: Travel Areas are now fully removed from Oracle Field Service.

26B phased out manual Travel Area configuration and started showing deprecation warnings. In 26C, Oracle has finished the job: the Travel Area configuration screens, the Travel Areas button under Work Zones, and the Region Name and Region Label columns in Travel Statistics reports are gone entirely. Work Zones no longer need a Travel Area association, REST API Travel Area and Region parameters are now optional, and existing integrations keep working through backward compatibility — but you shouldn't rely on those values to control behaviour any more. If you haven't already, this is the moment to check your reports, runbooks and integrations for anything that still references Travel Areas. Note this applies to Oracle Field Service environments, not Oracle Fusion Field Service.

AI RELATED FEATURES

Field Assist AI Agent Support in Oracle Fusion Field Service

This is the headline AI feature in 26C, and it's a genuine step change for Collaboration. Fusion Field Service customers can connect an AI agent built in Agent Studio directly into Field Assist (the feature formerly known as Helpdesk), so it handles incoming requests automatically and only escalates to a live operator when it needs to.

• Fusion Field Service only — Oracle Digital Assistant integration for Collaboration is no longer supported here, though it's still available for Oracle Field Service.
• Setup is straightforward once the agent exists — administrators just enter an Agent Team Code and Agent Team Version against the Field Assist configuration.
• Text only, for now — no rich responses, attachments, or sharing of location, inventory or resource details, and the send icon locks while the agent is responding, so agents need to reply within about 30 seconds.

I'll be recommending clients design their agent prompts and escalation logic carefully before they switch this on — the JSON-based handoff to a live operator is simple to build, but easy to forget.

CORE FEATURES

Extending Cloud Maintenance Work into Field Service Scheduling

If you're running Oracle Maintenance Cloud alongside Field Service, this is the feature to pay attention to. 26C lets Maintenance Work Order and Work Order Operation fields — Work Order Type, Standard Operation Code, Work Center Code, Organisation Code and more — feed directly into Field Service routing filters, work skill conditions, work zone keys, activity duration keys and travel keys.

Bulk routing can now create, schedule and assign Field Service activities straight from eligible Maintenance Work Order Operations, populating the activity address from the asset location and the SLA window from the work order's planned dates. Maintenance fields can also be surfaced — read-only, alongside read-write work order and operation DFFs — in configurable forms for dispatchers and technicians.

• Only bulk routing plans support auto-creation — not continuous, immediate or urgent plans.
• Work orders must be single-asset and released, with operations that pass a set of internal eligibility checks.
• If you've already built OIC-based or custom integrations to create activities from Maintenance operations, check for duplicate creation before turning this on.

This one has been a long time coming for asset-heavy operations, and it's the clearest sign yet of where Oracle is taking the EAM and Field Service convergence story.

Confirm Prerequisites for Configuring the Fusion Service Application

A smaller change with an outsized practical benefit. From 26C, adding, retrying, reconfiguring or modifying an Oracle Fusion Service and Service Logistics application in Field Service triggers a Confirm Prerequisites dialogue box, listing the Fusion Service setup tasks — exposing the work order setup and creating the SOA Operator job role — that need to be done first, with direct links to the relevant documentation.

It doesn't complete those prerequisite tasks for you, but it heads off the classic failure mode of starting the integration before Fusion Service is actually ready for it. No setup required on your part — it's automatic.

Fusion Service Work Order Fields and Formatted Addresses, Everywhere

Two related enhancements land together here. Administrators can bring useful Fusion Service work order address detail — building, floor number, phonetic address lines, postal code extensions — onto activity pages as read-only fields, alongside a new single formatted_address field that renders the complete address as one clean, country-aware string instead of a stack of separate fields.

The formatted address field follows Fusion's country-specific address formats where they exist, falling back to the standard street, city, state, postal code and country order everywhere else. It's a small thing, but in mobile-heavy field operations, one clean address line beats five cluttered fields every time.

Project and Task Fields Now Available in Forms

Building on the native Fusion Project Management integration introduced in 25D, 26C lets administrators add Project and Project Task fields — Project Name, Task Number, Task Name, Task Description, Task Start and Finish dates — directly into Field Service forms, plus read-write Project Task DFFs. Most fields are read-only, but Task Name and Task Description can be updated from the field.

For anyone running project-based service work, this closes a genuine gap: less duplicated data entry, and a field team that can see project context without a custom property doing the heavy lifting.

Crew Labour Hours Flow Straight to Oracle Time and Labour

Debrief can now capture and manage crew labour hours for project-based activities, prefilled from activity duration and pushed automatically to Oracle Time and Labour as time entries on submission. Crew leads and members can review, correct, delete or add labour records before any of it reaches payroll or project costing.

• Supported for project-based activities only — Fusion Service work orders and Maintenance work orders aren't in scope here.
• Offline-friendly — Debrief queues pending entries and posts them automatically once the device is back online, with a 24-hour retry window that can be extended via a plugin parameter.
• Needs the laborItemNumberForRegLabor plugin parameter configured — skip it, and workers land on a manual Add Labour page instead of a prefilled one.

This is the kind of feature that quietly improves project costing accuracy without anyone in the field noticing the extra admin — which is exactly how it should work.

Multi-Image Watermarking and Inventory Photo Attachments

Two photo-related features that work well together. Multi-Image Watermark stamps every field photo with location, timestamp and accuracy information — captured in the background so it doesn't slow down the person taking the photo — and the watermark stays visible through preview, crop and edit. Alongside it, Inventory Photo Attachments lets field resources capture and attach multiple photos directly to inventory and asset records, syncing automatically to OCI Object Storage once connectivity returns.

Between the two, you get defensible proof-of-service photography and properly documented assets, which matters a lot in the utilities, construction and asset-heavy scenarios I see most often. Enabling the watermark does make geolocation permission mandatory for anyone capturing a photo on that screen, so plan your rollout communication accordingly.

Microsoft Teams Meetings, Started From Collaboration

If your organisation already runs Microsoft Teams, field resources and back-office staff can now start a Teams meeting from inside Collaboration and share it as a meeting card in the chat — no separate app-switching required. It only works in one-to-one chats and conferences, not broadcasts, and each user needs the "Allow initiation of Microsoft Teams meetings" permission plus a valid Teams licence.

It's a genuinely useful one for remote guidance and escalating tricky jobs to an expert, and it's the kind of feature that reduces repeat truck rolls more than any dashboard ever will.

A More Modern Look for Scheduling and Dispatch Configuration

Activity Types, Time Slots, Resource Types, Work Skills, Work Zones, and Shifts and Schedules all get a Redwood-based refresh in 26C, accessible through Fusion Setup and Maintenance rather than the legacy Field Service Configuration menu. Expect tabbed detail pages, drawer-based editing, manage-columns options and filter chips — a genuinely nicer experience for administrators, even if a few old parameters have quietly been deprecated in the process.

Bulk import and export of work zones isn't available in the new interface yet, so if you rely on that heavily, keep the legacy pages enabled in parallel for now.

Field Resources Page Joins the Redwood Move

In the same spirit, the Field Resource page — where you manage schedulable resources, working and on-call schedules, and non-working time — has also moved to Fusion Setup and Maintenance for Maintenance Cloud and Fusion Service customers. Both the old and new pages stay available side by side, so there's no forced cutover.

A Few Smaller Wins Worth Knowing About

Not everything in 26C needs its own section, but these are worth a mention:

• Filtering for Inventory REST API operations — a new filter query parameter on the customer, installed, deinstalled and resource inventory endpoints, applied before pagination, so integrations stop pulling every record just to find the one they need.
• Object Storage Attachments API — new endpoints for linking files already sitting in OCI Object Storage to activities and inventory records, without Field Service needing to store the files itself.
• Navigation to MyRoute from plugins — the Plugin API's close method now supports a MyRoute value for backScreen, so mobile workers land straight back on their route after finishing a plugin-based activity.
• DKIM-compliant reply addresses — Field Service now validates the Reply address domain on email steps in message scenarios, flagging any scenario that isn't using an approved or DKIM-enabled domain so your emails actually land in inboxes.

LINKS TO ORACLE FIELD SERVICE 26C RELEASE DOCUMENTATION

The detail behind everything above sits in Oracle's official readiness documentation — worth bookmarking if you're planning your 26C acceptance testing.

• Oracle Fusion Field Service 26C full feature summary
• Extend Cloud Maintenance Work into Field Service Scheduling and Enablement
• Field Assist AI Agent Support in Oracle Fusion Field Service
• Auto-Configuration of Travel Areas for Oracle Field Service
• Configuration UX for Activity and Resource Management

WHY KYTE?

Releases like 26C are exactly why we built Kyte the way we did. Oracle expertise means nothing if it can't keep pace with what Oracle ships every quarter, and that's where AI-first delivery earns its keep. We use AI to run requirements workshops, draft health checks and readiness assessments, and keep documentation current as fast as Oracle changes the platform underneath it — so our consultants spend their time on your decisions, not on paperwork.

We're 100% Australian owned, built by ex-Oracle Consulting leaders, and 100% referenceable — every client, every time. If Maintenance Cloud and Field Service convergence is on your roadmap, or you just want a second opinion on what 26C means for your environment, start a conversation with our team.

Author: Alf Martin, Capability Lead – Field Services and Asset Management

Deliver faster. With Kyte AI.