APEX Diff — A Snapshot Summary

APEX Diff gives us a clean, intelligent way to understand how Oracle APEX evolves across versions making it effortless to pinpoint what’s new, what’s changed, and what may impact our applications.

APEX Diff gives you a quick glance at what has changed between APEX releases.

By default, the application shows the latest six APEX releases on the right side of the page.

we can use the filter to select any 2 to 6 versions and compare what changed between them.

If we want an overview of the metadata differences between any two selected releases, we can click on either the APEX Views Diff or PL/SQL APIs Diff. Selecting the APEX Views Diff option, for example, will display the differences in columns across APEX Views between the two selected releases. For Public PL/SQL APIs, the focus is on functions and procedures.

Column level differences do not apply here. The app highlights additions, removals or updated definitions in the API signatures.

As developers, we can easily identify deprecated components using this tool.

It allows us to quickly compare two different APEX versions and spot changes.

We can also easily detect if any metadata views were renamed or newly added.

From my point of view, this becomes especially useful when upgrading an APEX application and refer apex versions.

To learn more, refer to the link below.

Click_to_view

Comments

APEX - Tip: Fix Floating Label Issue

Oracle APEX's Universal Theme provides a modern and clean user experience through features like floating (above) labels for page items. These floating labels work seamlessly when users manually enter data, automatically moving the label above the field on focus or input. However, a common UI issue appears when page item values are set Dynamically the label and the value overlap, resulting in a broken and confusing user interface. once the user focuses the affected item even once, the label immediately corrects itself and displays properly. When an issue is reported, several values are populated based on a single user input, causing the UI to appear misaligned and confusing for the end user. Here, I'll share a few tips to fix this issue. For example, employee details are populated based on the Employee name. In this case, the first True Action is used to set the values, and in the second True Action, paste the following code setTimeout(function () { $("#P29_EMAIL,#P29_...

Oracle APEX UI Tip: Display Page Title Next to the APEX Logo

In most Oracle APEX applications, every page has a Page Title displayed at the top. While useful, this title occupies vertical space, especially in apps where screen real estate matters (dashboards, reports, dense forms). So the goal is simple: Show the page title near the APEX logo instead of consuming page content space. This keeps the UI clean, professional, and consistent across all pages. Instead of placing the page title inside the page body: ✅ Fetch the current page title dynamically ✅ Display it right after the APEX logo ✅ Do it globally, so it works for every page All of this is achieved using: ✅ Global Page (Page 0) ✅ One Dynamic Action ✅ PL/SQL + JavaScript Simple, effective, and reusable. 1️⃣ Create a Global Page Item On Page 0 (Global Page), create a hidden item: P0_PAGE_TITLE This item wi...

Building a Custom Debug Package for Oracle APEX Using PL/SQL

While developing Oracle APEX applications, debugging page processes and backend PL/SQL logic can be challenging—especially when values are lost between processes or execution flow is unclear. Although DBMS_OUTPUT is useful, it doesn’t work well inside APEX runtime. To solve this, I built a custom PL/SQL debug Package that logs execution flow and variable values into a database table. This approach helps trace exactly where the code reached, what values were passed, and whether a block executed or not - even inside page-level processes and packaged procedures Why a Custom Debug Package? Works seamlessly inside Oracle APEX page processes Persists debug information even after session ends Helps trace execution flow Captures runtime values Can be turned ON/OFF dynamically Does not interrupt business logic The Package consists of:- Debug Table - Stores debug messages Sequence ...

Think APEX

Search This Blog