Skip to main content

Enhancing UX with Recently Visited Pages Navigation in APEX

 

In this solution, I leverage Oracle APEX data dictionary views particularly the workspace activity log to capture detailed navigation audit information for each user within a given application. 

This audit data includes which pages users visit, how frequently they access them, and their overall navigation patterns.

Using this information, I create a Dynamic List in Shared Components, which automatically generates entries based on the most recently accessed pages for the logged-in user. 

This list is then displayed on the Home page as a personalized dashboard.

The result is a dynamic, user-specific "Recently Used Pages" dashboard that updates in real time. 

Each user sees a tailored set of pages they frequently or recently visited, allowing them to quickly navigate back to their most relevant screens. 

This is especially valuable for APEX applications where users routinely work across many pages and need faster access without searching through lengthy menus.

Overall, this approach improves usability, reduces navigation time, and enhances productivity—making it particularly helpful for users who interact with multiple pages within a single APEX application.

Step 1: Create a new Dynamic List from Shared Components.

             Navigate to: Shared Components > Lists > Create > Dynamic.

Step 2: Choose SQL Query as the source option.

Step 3: Paste the following query:

SELECT 

null              AS c1_level,

PAGE_TITLE        AS c2_name_for_label,

'f?p=' || :APP_ID || ':' || PAGE_ID || ':' || :APP_SESSION AS c3_target_url,

null              AS c4_is_current,

CASE 

WHEN PAGE_ID = 10 THEN 'fa fa-id-card'

ELSE 'fa fa-check' -- if you want add more icons

END               AS c5_icon_name,

VIEW_CNT          AS c6_badge

FROM (

SELECT 

p.PAGE_TITLE,

p.PAGE_ID,

COUNT(*) AS VIEW_CNT

FROM APEX_WORKSPACE_ACTIVITY_LOG l

JOIN APEX_APPLICATION_PAGES p

ON p.APPLICATION_ID = l.APPLICATION_ID

   AND p.PAGE_ID        = l.PAGE_ID

WHERE l.APPLICATION_ID = :APP_ID

  AND l.VIEW_DATE      >= SYSDATE - 3

  AND l.APEX_USER      = UPPER(:APP_USER)

  AND p.PAGE_ID NOT IN (9999, 1, 39)

  AND p.PAGE_MODE = 'Normal'

GROUP BY p.PAGE_TITLE, p.PAGE_ID

ORDER BY VIEW_CNT DESC

)

WHERE ROWNUM < 15; -- Adjust the limit as needed for convenience

Step 4: Go to the Home Page and create a List Region (choose from the Region Type options) using the Content Block template. If you want a smaller region tile, use the template options—three sizes are available: Small, Medium, Large.

Step 5: Under the Source property of the region, select the Dynamic List you created.

Step 6: In the List Region Attributes section, APEX provides several appearance options such as Badge List, Cards, Tabs, etc.

Choose Cards and configure the following settings under Card Appearance:

General             – Use Template Defaults & Apply Theme Colors

Style                 – Featured

Icons                 – Display Icons

Layout              – 3 Columns (or any layout you prefer)

Body Text         – Hidden (we don't need additional content)

Icon Shape        – Circle

Animation         – Color Fill (Raise Card is also available)

Step 7: Run the application, navigate through a few pages, and return to the Home Page.

Your Recently Viewed Pages dashboard will now display automatically based on your activity.


Screenshot:-

Demo_Link

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