JD Edwards Release 26 Tools Update: Smarter Automation, a Rebuilt Scheduler and AI That Works Inside JDE

JD Edwards Release 26 delivers more than incremental improvements to the tools layer – it represents a genuine shift in how organisations can interact with their JDE environment, build automation, and begin connecting the platform to artificial intelligence. For the teams responsible for running, developing, and extending JD Edwards, this is one of the most consequential tools releases in recent memory.

The enhancements span everything from how users consume data on E1 pages, to how developers debug orchestrations, to how organisations can now send JDE data to Oracle Cloud Infrastructure AI services and surface the results directly inside the application. Some of these changes are long-overdue quality-of-life improvements. Others open up capabilities that simply weren’t possible before.

Here is what JD Edwards Release 26 delivers on the tools side — and why it matters.

Generative AI via OCI allows organisations to send JDE data, spend analysis, transaction histories, operational metrics, to a large language model and receive natural language analysis in return. The LLM can be prompted to summarise findings, identify anomalies, answer specific questions about the data, or generate output in a particular format. This analysis can be surfaced directly on an E1 page through a text widget, with user-configurable inputs allowing different teams or individuals to query different data sets. The choice of LLM is configurable, allowing organisations to select the model that best suits the sensitivity and nature of the data being processed.

OCI Language Services extend this further with translation and localisation capabilities. JDE data output can be translated into any supported language on the fly, with the target language set as a persistent user preference. Oracle’s primary use case for this capability is addressing the longstanding challenge of mistranslations in localised JDE deployments, but the same mechanism can be applied wherever multilingual output is needed.

Document Understanding is the OCI AI service likely to see the earliest and widest adoption among JDE organisations. It allows documents, invoices, purchase orders, expense receipts, to be submitted to an AI model that identifies the document type and extracts structured data from it, returning that data to the Orchestrator for processing. The practical application is significant: an invoice arriving as an email attachment can be read, classified, and loaded into Accounts Payable automatically, without manual keying. For organisations managing high volumes of supplier invoices, this represents a material reduction in processing cost and error rate.

Digital Assist brings chatbot capability into the JDE environment, allowing users to interact with JDE data and processes through a conversational interface. AI Vision adds image recognition and anomaly detection, with clear applications in asset management and maintenance operations, where equipment images can be analysed to identify missing components, damage, or deviation from an expected state.

It is worth being clear about the cost model. The OCI AI services require an OCI subscription and are consumed at a cost. Oracle provides learning paths in LearnJDE covering both OCI Generative AI and OCI Language Services, which offer a practical way for teams to evaluate these capabilities and build internal knowledge before committing to a production deployment.

JD Edwards Configurable Widgets with User Inputs: Personalised Data at Every Workstation

Widgets have been a growing part of the JD Edwards user experience across recent releases, giving organisations the ability to surface orchestration-driven data visualisations directly on E1 pages. Release 26 takes this a step further with the introduction of user inputs on widgets, a change that transforms them from static displays into genuinely interactive tools.

Previously, a widget showing spend analysis by business unit would show the same data to every user who loaded that page, with no ability to filter or adjust the view without reconfiguring the widget itself.

Now, organisations can allow users to enter their own parameters directly on the E1 page, a company number, a date range, a location code, and the widget refreshes accordingly. These inputs can be presented inline, visible directly on the page, or hidden behind a settings control for a cleaner interface where the user only adjusts parameters when needed.

Critically, these settings are persistent. When a user logs out and back in, their last input is retained, meaning each person’s E1 page reflects their own context without requiring them to re-enter preferences every session. For organisations where different teams or business units work with different data sets, this makes E1 pages significantly more useful and reduces the need to build and maintain multiple versions of the same widget for different audiences.

JD Edwards E1 Page Notifications: Keeping the Right Information Visible

Release 26 adds targeted notifications to the E1 page toolkit, extending what was already possible with watchlists and widgets. Specific notifications can now be associated with individual E1 page tiles, surfacing relevant alerts in context rather than requiring users to navigate to a central work centre to find them.

For roles like purchase order approvers or accounts payable processors, this means that the information most likely to require their attention, orders awaiting approval, invoices on hold, exceptions requiring action, can be front and centre , shown in context, when they start their day, without any additional navigation.

Conditional Launch of an Orchestration, Notification, or Logic Extension from a Form Extension

Designers can now set conditions under which an orchestration, notification, or logic extension is launched from an event on a form extension.

Previously, any conditional logic governing when logic should execute had to be included within the logic extension or orchestration itself. This meant logic extensions and orchestrations could become cluttered with conditional checks that had nothing to do with the core function, simply to prevent them from running in the wrong context. Now, execution conditions can be defined externally at the form extension level, specifying the precise circumstances, order type, company, document type, or any combination, under which the logic extension, orchestration or notification should be invoked.

For organisations running complex JDE environments with multiple business units, order types, or company structures, this will meaningfully reduce the maintenance overhead on logic extensions and orchestrations, and make it easier to understand and audit what each logic extension or orchestration  is doing.

JD Edwards Orchestrator Improvements: Debug, Variables and Power Form Extensions

Release 26 includes several targeted improvements to the Orchestrator that will be immediately appreciated by anyone doing serious development work on the platform.

File input debugging has been a persistent friction point, until now, attempting to debug an orchestration that used a file as its input would produce an error, making it difficult to diagnose issues in file-based integrations. This limitation has been resolved in Release 26, allowing developers to step through file-driven orchestrations in debug mode just as they would any other.

A related improvement addresses the experience of debugging complex form requests. When a form request involves multiple forms and one of them fails, the system now identifies exactly which form caused the failure. For orchestrations stepping through ten or more forms, the difference between knowing a form request failed and knowing which specific form failed is the difference between minutes and hours of investigation.

Printer output options, printer selection, output format, number of copies, and debug settings, can now be passed as variables within orchestration report requests. This makes it possible to dynamically route report output based on the user, the business unit, or any other context available at runtime, without hardcoding printer settings into each orchestration.

Form extensions, including the ability to enable and disable fields conditionally, are now supported on Power Edit forms, bringing them in line with standard forms and removing a limitation that has constrained what was achievable in certain high-volume data entry contexts.

JD Edwards Web-Based Scheduler: The Most Significant Scheduler Update in Two Decades

The JD Edwards scheduler has been moved to a web application in Release 26, ending the long-standing requirement to use a fat client for scheduler management. For organisations that have been working toward fully browser-based JDE environments, this removes one of the last remaining dependencies on the thick client for routine administration tasks.

The move to the web would be noteworthy on its own, but Oracle has accompanied it with the most substantial set of scheduler enhancements in an estimated ten to twenty years. Scheduled jobs can now be configured to run on a specific business day of the month, the third business day, the last business day, rather than only on a fixed calendar date. Run windows can be defined to restrict when a job is permitted to execute, and where multiple virtual batch servers exist, jobs can be directed to a specific server.

Perhaps the most practically significant addition is control over catch-up behaviour. In the standard JDE scheduler, when the scheduler goes offline and then restarts, every job that was due to run during the downtime queues up and executes in rapid succession on restart. For jobs that run frequently, every fifteen or thirty minutes, this produces a burst of redundant processing that consumes server resources without delivering any useful outcome. Release 26 gives administrators the choice: catch up on missed runs or simply resume from the point the scheduler comes back online. For high-frequency scheduled jobs, this change alone can have a meaningful impact on system stability during and after scheduler recovery events.

Getting the Most from JD Edwards Release 26 Tools

The tools enhancements in Release 26 reward organisations that approach them strategically. Configurable widgets and the Enterprise Automation Dashboard are most valuable when E1 pages are deliberately designed around the data each role actually needs. he OCI AI integrations require upfront thinking about which use cases align with business priorities and which AI services are appropriate for the data involved.

Ndevr’s consultants work with organisations across Australia and New Zealand to design, build, and optimise exactly these kinds of implementations, from E1 page design and widget configuration through to production Orchestrator automations and OCI AI integrations. If you are assessing what Release 26 tools could mean for your organisation or looking for help translating these capabilities into tangible outcomes, we are ready to have that conversation.