Skip to main content

Oracle APEX: Open Specific Tab on Page Load Using Dynamic Parameter

While browsing the Oracle APEX discussion forum, I came across a useful workaround shared by a user named blue. 

His requirement was to activate a specific tab automatically when navigating from 

different pages — based on the redirect source, button click, or custom navigation logic.

In this blog, we will walk through how to achieve this behavior. I hope it helps you in similar APEX use cases.

Step 1: Create the Tab Container
Create a tab container region and assign it a Static ID
Static ID: TAB_MAIN

Template: Tabs
Tab Style: Pill

Step 2: Create Sub Tabs
Inside the main tab container, create three tabs and assign Static IDs:

Tab Label           Static ID
Emp              EMP
Dept           DEPT
Location           LOCATIONS

Step 3: Create a Hidden Page Item

Create a hidden page item named: P16_ACTIVE_TAB
This item will receive a value (e.g., EMP, DEPT, or LOCT) when navigating from another page. 
Based on this value, the corresponding tab will activate automatically on page load.

Pass_Value                Tab_Activated

Emp                                Emp Tab
Dept                                Dept Tab
Loct                                Location Tab

Step 4: Add the JavaScript

Paste the following code into Function and Global Variable Declaration 

setTimeout(function () {
    var activeTab = ($v("P16_ACTIVE_TAB") || "").toUpperCase();  

    if (activeTab === 'EMP') {
        apex.region("TAB_MAIN").widget().aTabs("getTabs")["#SR_EMP"].makeActive();  
    } else if (activeTab === 'DEPT') {
        apex.region("TAB_MAIN").widget().aTabs("getTabs")["#SR_DEPT"].makeActive();
    } else if (activeTab === 'LOCT') {
        apex.region("TAB_MAIN").widget().aTabs("getTabs")["#SR_LOCATIONS"].makeActive();
    }
}, 500);


P16_ACTIVE_TAB  - Hidden item used to pass the tab identifier
TAB_MAIN  - Static ID of main tab container 
SR_EMP, SR_DEPT, SR_LOCATIONS - Tab Static IDs with "SR_" prefix as required by APEX tab structure

With this setup, the correct tab will automatically activate based on the value passed into P16_ACTIVE_TAB, making navigation smoother and more intuitive for users.






Comments

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_...

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 ...

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 ...