Changelog

26.1.0 (October 2026)

Requires Oracle APEX 24.2 or later. Supports APEX 26.1 and 26.2.

Fixed

Job list on APEX 26.1 and later. Each job in the list lost its own settings (style, colour, check interval, Remove on Complete) and used the settings of the action that opened the list. From APEX 26.1 the dynamic action attributes are stored in a JSON column; UC_PROGRESSBAR_PKG now reads them from there and keeps working on older APEX versions.
Event runs stayed in state "running". Event-type progress bars completed on screen, but their rows in UC_PROGRESSBAR stayed in state R. They are now set to D (done) or E (error).
Bar removed with "Process/Job ... do not exist or it was never executed." while the process was starting. When the first status check came before the process or job called UC_PROGRESSBAR_PKG.start_process (for example on a busy database), the bar was removed with this error and the process then ran unseen. The bar now waits up to 30 seconds for the process to start before it reports the error.
Accessibility. The bar reported 40% (aria-valuenow="40") to screen readers until the first status update. It now reports its real value from the first render.
Empty container. A completed or removed bar left an empty div.apex-uc-progress in the page. The container is now removed with the bar.
Job list dialog on Universal Theme 21.1 and later. The buttons sat directly under the list and left the rest of the dialog empty. The dialog now uses the same layout as APEX's own inline dialogs, so the buttons stay at the bottom.
Texts too large on Universal Theme 21.2 and later. Bar and job list texts rendered 60% larger than intended (for example 21.6px instead of 13.5px), because the CSS was written for the old 10px root font size. All sizes are now fixed in pixels and look the same on every theme version.

Changed

On start the plug-in reads the current state of the process, so the first render already uses the right max value.
The wait for a process or job to start can be changed in JavaScript, for example in the page's Execute when Page Loads:
```
uc.progressbar.opt.startTimeout = 60; // seconds, default 30
```

Sample application

The sample application is now exported as application 281 (it was 187), with the application alias PROGRESS_BAR. To replace an installed copy, choose ID 187 when you import it; otherwise it installs as a second application.
The History page lists every run, including the latest run of each process or job. The column Process Archived marks the current run with N.
Page 500 shows the right complete text (message UCPROCESS.COMPLETE).
Page 400: the error demo buttons are named after what they do (Run PROCESS Error and Run JOB Error).

Upgrade

New minimum: Oracle APEX 24.2 (was 19.2), and with it Oracle Database 19c.

Import the new plug-in dynamic_action_plugin_unitedcodes_progress_bar_pro.sql (or the new sample application) over the existing one.
Install the new package UC_PROGRESSBAR_PKG: run the package specification and package body from ddl_uc_pbp_manual_install.sql (the last two statements of the script). Tables and license objects stay as they are, but the fixes need the new package body.
Your license must cover version 26.1. UC_PROGRESSBAR_PKG presents its version to the license check, and that version moved from 23.1 to 26.1 in this release. Licenses have to be re-activated on every major release: obtain a new API key through the Plug-ins Pro portal and activate it as described in Installation.

23.1 (July 2023)

Release for APEX 23.1, new documentation site.

22.3 (March 2023)

JSON output of UC_PROGRESSBAR_PKG uses APEX_JSON.INITIALIZE_OUTPUT.
On start the plug-in reads the state (max value) of the process with an AJAX call.

22.1 (December 2022)

Release 22.1.