A department head needs one number. Not a dashboard, not a project, just a number: how many enterprise customers in the Nordics renewed last quarter, broken out by industry. She cannot pull it herself, so she does what everyone in her position does. She files a request, and the request joins a queue behind everyone else’s requests, and the queue is measured in weeks.
This is one of the most common and least examined costs in a large organization. The data exists. The people who need it cannot reach it without help, and the people who can reach it are a shared, overloaded resource. Oracle APEX 26.1, the May 2026 release of Oracle’s low-code platform, is built to change that specific dynamic, and it does it in a way that finally addresses the reason self-service reporting has disappointed so many organizations before.
Follow that request through a typical enterprise. It starts as a message to IT or to a central analytics team. It becomes a ticket. The ticket is triaged, prioritized against everything else in flight, and assigned to someone who can write the query. That person may need to clarify what the requester actually meant, because “enterprise customers” and “renewed” can mean three different things depending on who is asking. Eventually the report is built, checked, and delivered.
By the time it arrives, two things have often happened. The business moved on, and the answer is now needed in a slightly different form, which starts the cycle again. And the requester, having learned how long this takes, has begun hoarding requests or building fragile workarounds in spreadsheets, which creates a second problem the organization will pay for later. Multiply this by every manager in every department, and the cost is not a delay. It is a permanent tax on how quickly the business can think.
The obvious fix is to let business users serve themselves, and most large organizations have tried. The attempts usually fail for a reason worth understanding, because Oracle APEX 26.1 is built around it.
Early self-service tools handed business users broad access to data and the freedom to slice it however they liked. That produced two failures at once. It produced wrong answers, because users without a precise understanding of the data drew confident conclusions from numbers that did not mean what they thought. And it produced risk, because broad self-service access is difficult to reconcile with the rule that people should see only the data they are entitled to see. Faced with conflicting numbers in board meetings and uncomfortable questions from security, IT did the rational thing and clamped back down. The backlog returned, because the lesson organizations took was that self-service and control were opposites. The real problem was never self-service. It was self-service without governance.
Oracle APEX 26.1 introduces two capabilities that, together, let business users get their own answers without reopening the old problems.
The first is AI Interactive Reports. Interactive reports are the familiar, sortable, filterable tables of business data that sit inside most APEX applications. In Oracle APEX 26.1, a user can adjust one by asking in plain language. The department head from the opening can type a request to see Nordic enterprise customers grouped by industry, and the report applies the matching filters, groupings, and charts. She gets her number in seconds, from a report she already had access to, without writing a query or filing a ticket.
The second is Data Reporter, a self-service reporting tool for people who do not write code. It lets business users build and publish their own reports, but only against datasets that an administrator has prepared and approved in advance. The freedom to explore is real, and it is bounded by a curated, trustworthy foundation rather than turned loose on the raw database.
The same report request, run through both the old process and the new one, looks like this.
| Stage of getting a report | The old way | With self-service in Oracle APEX 26.1 |
| Who produces it | A developer or central analyst | The business user who needs it |
| How the request is made | A ticket, often with clarifying rounds | A plain-language question in an existing report |
| How long it takes | Days to weeks | Seconds to minutes |
| When the question changes | The cycle starts again | The user simply asks again |
| Who controls data access | Enforced, but the bottleneck is the cost | Enforced automatically, with no bottleneck |
The reason this is not a repeat of the failed self-service era is that Oracle APEX 26.1 keeps the user inside the organization’s existing controls.
When a user adjusts a report in plain language, APEX does not let an AI model write and run arbitrary queries against the database. It interprets the request and applies standard, visible report settings within the data-access rules that already govern that report. The settings it applies are inspectable, so a user can see exactly what was filtered and grouped, and adjust or remove it. Data Reporter works the same way by construction, because users build on datasets an administrator has already vetted, not on unrestricted access. In practice, a trusted dataset is something an administrator curates deliberately, for example a vetted sales-performance dataset with the correct joins, definitions, and filters already built in, so that someone exploring it cannot accidentally double-count revenue or wander into data that was never meant for general use. Where the database enforces row-level security, those rules continue to apply, so a user’s natural-language question can never return rows that user was not entitled to see. That combination, visible settings on the front end and enforced rules in the database, is what lets an organization widen access to reporting without widening its risk surface.
The natural-language features connect to an AI model through a configuration the organization controls, and for sensitive environments that model can be a private one running inside the organization’s own infrastructure rather than a commercial service, a point we cover in a separate article [AI on Your Data, Not in OpenAI’s Cloud: How Oracle APEX 26.1 Enables Private AI for Regulated Businesses]. Governed self-service and data privacy are not in tension here.
“Every organization that tried self-service reporting a decade ago got burned the same way: the moment you gave people freedom, you lost control of the numbers and the access. What changes now is that the freedom and the control come from the same place. The user asks in plain language, and the answer stays inside the rules that were always there.” Matt Mulvaney, Oracle ACE Director at Pretius
The clearest proof that APEX can carry serious analytical work comes from a real deployment. Pretius rebuilt the SMAART insurance analytics system for Munich Re HealthTech on Oracle APEX, and analytical tasks that previously took days now complete in minutes. The rebuild also retired a separate, costly analytics product the organization had been running alongside it. The relevant lesson for self-service is that this was not a lightweight reporting tool bolted onto simple data. It was demanding, regulated insurance analysis delivered on APEX at a speed the old stack could not match. Oracle APEX 26.1 now adds plain-language self-service on top of that kind of foundation.
The day-to-day pattern shows up across every team that currently waits on a reporting queue. The examples below are illustrative rather than named clients, but each one describes a request that used to become a ticket and now does not.
A sales director preparing for a Monday pipeline review wants the quarter’s deals broken out by region and stage. Instead of requesting it the previous Thursday and hoping it lands in time, the director asks for it directly, notices that one region looks thin, and reshapes the same report to compare it against the prior quarter, all before the meeting opens.
An operations lead handling a live customer escalation needs to see service requests for that customer’s country, filtered to the ones that have breached their target response time. In the old model that is a next-day answer. With self-service it is a question asked and answered while the customer is still on the call.
A finance team assembling a board pack wants results pivoted by product line and period, then the same view again with one segment excluded. Rather than queuing each variation behind month-end close, they produce them in minutes and keep their time for the commentary that actually requires judgment.
A risk or compliance officer preparing for a review wants exposure summarized by counterparty, drawn only from the records they are cleared to see. Because the underlying access rules still apply, they get the view they need without anyone building a one-off report or loosening a permission to produce it.
The first effect is the obvious one. Answers that took weeks take minutes, and the business can ask follow-up questions at the speed it actually thinks, rather than rationing them to fit a queue.
The second effect is less obvious and often larger. The technical teams who spent their days producing routine reports get that time back for work that genuinely requires them. The reporting backlog was never a sign that those people were slow. It was a sign that they were doing work that did not need their expertise. Routine reporting is often the least valuable use of the most expensive people in an organization, and ending it returns capacity to the work that does need them, which is worth far more than the reports themselves.
The third effect is cultural. When everyone draws from the same governed reports and approved datasets, the meetings that used to dissolve into arguments about whose number is right become meetings about what to do, because the numbers agree. There is a cost dimension here too, since capabilities that organizations often buy a separate reporting tool for are included in the Oracle Database license they already hold, which we examine in a separate article [Still Paying for a Separate BI Tool? Oracle APEX 26.1 Might Make It Redundant]. For the wider picture of what the release changes, see the overview [Oracle APEX 26.1: What It Means for Your Business — and Why It Is Not Just Another Update].
What is Data Reporter in Oracle APEX 26.1? Data Reporter is a self-service reporting tool introduced in Oracle APEX 26.1 for people who do not write code. It lets business users build and publish their own reports against datasets that an administrator has prepared and approved in advance, which gives them freedom to explore within a trusted, governed boundary rather than unrestricted access to the database.
Can business users build reports in Oracle APEX without coding? Yes. With AI Interactive Reports, users adjust existing reports by asking in plain language, and with Data Reporter, they can build and publish new reports against approved datasets. Neither requires writing queries or code, and both keep users inside the organization’s existing data-access rules.
What are AI Interactive Reports? AI Interactive Reports are standard APEX interactive reports that users can adjust using natural language in Oracle APEX 26.1. A user describes the view they want, and APEX applies the matching filters, groupings, sorting, and charts as standard, visible report settings, without running arbitrary AI-generated queries against the database.
Is natural-language reporting in Oracle APEX 26.1 secure? It is designed to be. APEX applies report settings within the data-access rules that already govern a report, rather than giving an AI model open access to data, and where the database enforces row-level security those rules continue to apply. Users see only the data they were already entitled to see.
Does self-service reporting in Oracle APEX 26.1 replace a dedicated analyst? No, and it is not meant to. It removes the routine reporting that should never have required an analyst, which frees specialist teams for the complex analysis that genuinely does. The goal is to match the work to the right people, not to eliminate the role.
Self-service reporting in Oracle APEX 26.1 can take the routine reporting load off your technical teams while keeping every answer inside the controls you already enforce, and the value depends on setting up the right datasets, permissions, and AI configuration for your organization. Pretius is an Oracle Partner with 7 Oracle ACEs and ISO 27001 certification, and has delivered Oracle APEX applications and analytics for financial institutions, insurers, and enterprises across Europe. If you want to see what governed self-service reporting would look like on your data, get in touch with our team for a conversation.
