Screen by screen Local-first Audit-ready

A guided tour of QueryWell

QueryWell gives you a familiar, SQL-Developer-style experience for Oracle Fusion Cloud ERP — without pretending Fusion exposes a backend database. Every query and report runs through Oracle's supported reporting surfaces, and every byte of data stays on your machine. Here's what that looks like in practice.

Three steps to your first report

  1. Add and test your pod in Connections — enter the URL, choose Basic or OAuth, set the BI Publisher data-source pool, and click Test.
  2. Run SQL or reports in Query Studio, or author your own in Report Builder. Fill any parameters and click Run.
  3. Review the grid, then export to CSV / JSON / XLSX / PDF. History and Exports keep a full audit trail automatically.

The workspace at a glance

A calm, enterprise layout: a navigation rail on the left, the active workbench in the centre, and context panels — parameters, inspector, logs — on the right. Colour-coded status badges tell you what's safe to run at a glance.

No Oracle credentials yet? A built-in Demo (Mock) connection lets you explore every feature offline.

QueryWell Dashboard showing workspace status, active connection, and recent run and export activity.
01 · Dashboard

A quick read on status & recent activity

Your landing overview: the active connection, today's run and row counts, and a recent-activity list you can use as a jump-off point to repeat or review a run. Green means the active pod is connected and ready; amber means a profile still needs testing.

The Dashboard also reminds you when a job looks too large for an interactive pull — very large extracts belong in Oracle's BICC or scheduled channels.

QueryWell Connections screen for creating and testing Oracle Fusion pod profiles with Basic or OAuth authentication.
02 · Connections

Create and test a profile for each pod

Add a profile, enter the pod URL, choose an auth type, and set the BI Publisher pool (e.g. ApplicationDB_FSCM). Click Test to verify, then select the profile to make it active.

Credentials live in the OS keychain — never in plain text, never in the app's database. Prefer OAuth 2.0; Basic auth is clearly labelled dev/fallback and only allowed over HTTPS. A failed test is a real failure — 401/403 are reported as failures, so a green test genuinely means you can run reports.

QueryWell Query Studio worksheet with a SQL editor, parameter inspector, and a fast results grid.
03 · Query Studio

One worksheet, three engines

The main worksheet runs free-form SQL, BI Publisher reports (RUN REPORT /path), and read-only Fusion REST GETs — switch simply by how you start the command. Pick a connection, type your query, fill any parameters in the right-hand inspector, and click Run.

Reporting-only is on by default: destructive operations are blocked, and the inspector always shows the current mode so there are no surprises.

QueryWell Report Builder for authoring BI Publisher data-model reports with typed parameters.
04 · Report Builder

Author your own data-model reports

Build and test your own BI Publisher data-model reports — datasets plus typed parameters — without leaving the app. Select a connection, write your dataset SQL with :NAME binds, give each parameter a type and sensible default, and run.

Read-only by design: SQL must be SELECT / WITH only; anything else is blocked before it ever reaches the pod.

QueryWell Toolkits showing curated DBA and Audit SQL alongside saved personal snippets.
05 · Toolkits

DBA, Audit & My Snippets

Curated ITGC/ITAC and DBA SQL, mapped to controls and ready to open straight into a worksheet — set your bind values and run. Save your own go-to queries, or upload existing .sql scripts into My Snippets and reuse them across connections.

Pair Toolkits with Report Explorer: keep your standard SQL here and your standard report paths there.

QueryWell Results view with a virtualized data grid, an instant chart, and column profiling.
06 · Results

Grid, charts & column profiling

Explore big result sets in a fast virtualized grid, turn any result into an instant chart, and profile a column to see distributions, ranges and outliers — so trends jump out before you export.

QueryWell History log listing every execution with timestamps and masked sensitive parameters.
07 · History

Every execution, traceable

A complete, searchable record of every run — what was executed, when, against which connection, and with which (masked) parameters. Re-open a past run to repeat or audit it.

Sensitive parameter names — token, key, IBAN, account and the like — are masked in the log automatically.

QueryWell Exports log showing CSV, JSON, XLSX and PDF files each with a SHA-256 hash for tamper-evident evidence.
08 · Exports

Tamper-evident export evidence

Send results to CSV, JSON, XLSX, or a polished PDF report. Every export is SHA-256 hashed and recorded in the export log — tamper-evident evidence you can hand straight to auditors and examiners.

QueryWell Settings screen covering security options, licence status, and local data management.
09 · Settings

Security, licence & your data

Manage your licence, review security options, and stay in control of your local data. QueryWell stores connection metadata, history, audit logs and saved queries in local SQLite on your device — with no telemetry and no cloud sync. Nothing phones home but the licence check.

Ready to put it to work?

Buy QueryWell once and own it. We'll send your download links and licence key by email, and you'll be reporting on live Fusion data — locally — in minutes.

Own it outright, no subscription Audit-ready exports out of the box Your data never leaves your machine