Skip to main content

Dynamically Setting APEX Logo Based on Logged-In User

 In Oracle APEX applications, enhancing user experience through personally is a key aspect of modern UI design. One effective way to achieve this is by dynamically setting the application logo based on the currently logged-in user. This approach allows us to display different logos for example, company-specific branding, department icons, or user-type indicators tailored to each user.

Step1: Store the logo image in the user details table.

Step2: Create a Module from Restful service

Step3: Add a Template

Step4: Add a Handler

Step5: Paste the following PLSQL code

DECLARE

v_blob BLOB;

v_mime_type VARCHAR2(50);

v_length NUMBER;

v_user_id NUMBER;

BEGIN

v_user_id := TO_NUMBER(:USER_ID);

SELECT USER_LOGO, MIME_TYPE

INTO v_blob, v_mime_type

FROM USER_TABLE

WHERE USER_ID = v_user_id;

v_length := DBMS_LOB.GETLENGTH(v_blob);

IF v_length > 0 THEN

OWA_UTIL.MIME_HEADER(NVL(v_mime_type, 'image/png'), FALSE);

HTP.PRN('');

WPG_DOCLOAD.DOWNLOAD_FILE(v_blob);

ELSE

OWA_UTIL.STATUS_LINE(404, 'Not Found');

END IF;

END;

Step6: Now copy the Full URL from Resource Handler.

Step7: Create One Application Page Item with the name of P_USER_ID

Step8: Create One Application Process Process_Point - After Authentication (paste the following code)

BEGIN

SELECT USER_ID

INTO :P_USER_ID

FROM USER_TABLE

WHERE UPPER(USER_NAME) = UPPER(:APP_USER);

EXCEPTION

WHEN NO_DATA_FOUND THEN

:P_USER_ID := NULL; 

WHEN TOO_MANY_ROWS THEN

:P_USER_ID := NULL; 

WHEN OTHERS THEN

:P_USER_ID := NULL; 

END;

Step9: Now go-to UI Interface under shared component and select logo

Logo

Image

Image URL

Paste Full URL and add application item

Sample_URL

https://yourdomain/ords/dms/get/user_logo/&P_USER_ID.

Step10: Save and run the application.

User1:-

User2:-







 

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