Skip to main content

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 will hold the current page's title.

2️⃣ Create a Dynamic Action on Page 0

    Event: Page Load

This dynamic action will have two True Actions.

🔹 True Action 1: Fetch Page Title (Server-side)

Action: Execute Server-side Code

Language: PL/SQL

Items to Return: P0_PAGE_TITLE

BEGIN

  SELECT page_title

    INTO :P0_PAGE_TITLE

    FROM apex_application_pages

   WHERE application_id = :APP_ID

     AND page_id = :APP_PAGE_ID;

EXCEPTION

  WHEN OTHERS THEN

    :P0_PAGE_TITLE := null;

END;

✔️ This dynamically fetches the page title

✔️ Works for all pages

✔️ Safe fallback using exception handling

🔹 True Action 2: Inject Title Near Logo (JavaScript)

Action: Execute JavaScript Code

var a = $v("P0_PAGE_TITLE");

$(".t-Header-logo").each(function () {

  $(this).append(

    '<span class="extra-text" style="font-size:20px; font-weight:bold; margin-top:15px;">'

    + a +

    '</span>'

  );

});

🧩 What This Does

Reads the page title from P0_PAGE_TITLE

Appends it right after the APEX logo

Makes it visually clear and elegant

🎨 UI Result

No extra space consumed in the page body

Page title is always visible

Cleaner and more professional header

Works automatically for every page

✅ Why This Tip Is Useful

✔️ Zero page-level configuration

✔️ Centralized logic (Global Page)

✔️ Improves UX without redesign

✔️ Easy to customize with CSS later

This is one of those small changes that make your app feel premium.

Comments

Post a Comment

Popular posts from this blog

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_...
Post a Comment
Read more

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 ...
Post a Comment
Read more

Conditional Cell Editing in Oracle APEX IG

While browsing the Oracle APEX forum, I noticed a question from a user asking how to disable all other cells in an Interactive Grid row until the first cell has a value. In this blog, we will explore how to disable all other cells in an Interactive Grid row until the first cell contains a value. This approach helps enforce proper data flow, avoids incomplete or invalid records, and improves overall data integrity.  By implementing a simple client-side logic using JavaScript and Dynamic Actions, we can gain fine-grained control over row-level editing behavior in Oracle APEX. Step1: Create IG with static ID of EMP. Step2: Paste the following code in function global declaration. function setCellsToReadOnly()  { var grid = apex.region("EMP").widget().interactiveGrid("getViews", "grid"); if (!grid || !grid.model) { return; } var model = grid.model; model.forEach(function (record, index, id) { var meta = model.getRecordMetadata(id); var fields ...
Post a Comment
Read more