Skip to main content

Oracle Apex: Custom Region Headers Step-by-Step Guide

 

Introduction

When building data-driven dashboards and reports in Oracle APEX, displaying descriptive region headings improves the user interface. By default, Oracle APEX renders the region title as a plain header. However, developers often need more control over how that title looks, especially when working with Interactive Grid or Classic Report regions embedded in complex page layouts. Without this control, headings can appear duplicated or unstyled, which looks unprofessional.

This article provides a step-by-step approach to displaying a custom styled heading such as "Service Request Master" above a report region in Oracle APEX.

Prerequisite

·         An Oracle APEX page containing:

 One Interactive Grid region named Service Request Master

 One Detail region named Service Request Detail

·         Basic familiarity with APEX Page Designer

Objective

When you want to show a styled heading like "Service Request Master" above a report region, a common mistake is to add both a Static Content HTML region and set the region's built-in Title field simultaneously. This results in a duplicate heading one from the HTML and one from the region title  which looks unprofessional.

Solution

Step 1: Set the Report Region Title

In Page Designer, click your report region (e.g., Service Request Master). Under Identification, set the Title field to match your region name:

 Service Request Master

 Step 2: Add a Static Content Region for the Heading

Add a styled heading above your report region:

1        Right-click your page in the Page Designer tree → Create Region Below


2        In Page Designer, click your report region. Under Identification, set the Title field to: Service Request Master

Note: The Title field is mandatory in APEX and cannot be left blank.

3        Set Type to Static Content

 4        Under Source → HTML Content, paste the following:

<div style="

  background: #2596be;

  padding: 15px 25px;

  border-radius: 10px;

  text-align: center;

  box-shadow: 0 4px 10px rgba(0,0,0,0.2);

">

  <h2 style="

    color: white;

    font-weight: bold;

    margin: 0;

    letter-spacing: 1px;

  ">

    Service Request Master

  </h2>

</div>

5        Set the region sequence so it appears just above your report region

Step 3: Hide the Built-in Title Using Template Options

To prevent the duplicate heading, hide the report region's built-in title:

1.      Click your report region in Page Designer

2.      Go to Appearance → Template Options → Click the button

3.      Find the Header setting and select Hidden but accessible

4.      Click OK and Save the page

 Step 4: Remove the Gap Between Heading and Report

A spacing gap often appears between the Static Content heading region and the report region below it. To fix this:

  1. Run the page in Oracle APEX
  2. Hover over the Static Content heading region  a pencil () icon will appear in the top-right corner of the region
  3. Click the pencil icon to open Quick Edit
  4. In the Quick Edit panel, click Template Options
  5. Set Top Margin to None
  6. Set Bottom Margin to None

  1. Click OK
  2. Save the page and refresh to confirm the gap is removed

Applying the Same Steps to the Detail Region

Repeat Steps 1 through 4 above for the Service Request Detail region. In the HTML Content, replace the heading text with:   Service Request Detail

<div style="
  background: #2596be;
  padding: 15px 25px;
  border-radius: 10px;
  text-align: center;
  box-shadow: 0 4px 10px rgba(0,0,0,0.2);
">
  <h2 style="
    color: white;
    font-weight: bold;
    margin: 0;
    letter-spacing: 1px;
  ">
    Service Request Detail
  </h2>
</div>

 Save and Run

Save the page and run it to verify that both the Master and Detail headings display correctly with no duplication and no spacing gaps.


Conclusion

Displaying a clean, styled region heading in Oracle APEX requires a combination of using the built-in region Title (to satisfy APEX validation), hiding it via Template Options, and adding a separate Static Content region with custom HTML. This approach gives full control over the visual style while maintaining compatibility with the Universal Theme.

 






Comments

Popular posts from this blog

Oracle EBS R12 General Ledger (GL) Module – Practical SQL Queries

Introduction Oracle E-Business Suite (EBS) R12 General Ledger (GL) is the core Financial module in Oracle EBS R12. It is used to manage journal entries, accounting periods, balances, and financial reporting. The GL module integrates with Payables (AP), Receivables (AR), Fixed Assets (FA), Purchasing (PO), and Inventory (INV). The main purpose of a general ledger system is to record financial activity of a company and to produce financial and management reports to help the organization make decisions. Below are real-world SQL queries commonly used.   1) View configured Ledgers      Purpose: Fetch Ledger Configuration Details SELECT       ledger_id,      name  AS   ledger_name ,    short_name ,   currency_code FROM     gl_ledgers ORDER BY     ledger_id ;   2) Ledger Information Query Purpose: Fetch Ledger Configuration Details SELECT     gl.name   ...

Exploring AI in Oracle APEX 26.1

Artificial Intelligence (AI) is transforming the way organizations and developers work. Businesses and professionals are increasingly adopting AI tools to improve productivity, automate processes, and build smarter applications. Oracle APEX introduces a significant evolution in application development by integrating governed Generative AI capabilities directly into the low-code platform. This enables developers to build intelligent, conversational applications while maintaining enterprise-grade security and control. In this article we explore AI capabilities in Oracle APEX 26.1 What is AI Agents AI Agents can be created to reason over user requests and take actions through approved AI Tools. Each tool exposes a specific application capability the agent is allowed to invoke, such as retrieving data, running server-side PL/SQL, or executing client-side JavaScript. APEX manages the execution flow by preparing context, dispatching tool calls, executing tools, handling results, and...

Oracle R12 Inventory Configuration: Key points to Avoid Mistakes

Most Oracle ERP R12 inventory problems are not system failures they are process and configuration failures. The same categories of mistakes surface repeatedly across implementations: Focusing on master data control, disciplined transactions, proper OU setup, and strong internal controls prevents operational and financial discrepancies.   This article walks through the four most critical areas where Oracle R12 inventory implementations go wrong, explains why each mistake is costly, and provides recommendations to prevent them. Each section includes the relevant navigation path and configuration screenshots for hands-on reference   1.       Improper Item Master Configuration in Oracle R12   Oracle E‑Business Suite R12 , the Item Master Configuration serves as the foundation of the Inventory module. Two critical components under this configuration umbrella are: Define Master Item Setup Define Item Status Both setups control how items ...