Skip to main content

Highlight Row in Interactive Report

Recently I encountered a question on the OTN Forum about "How to Highlight a Current Row in an Interactive Report". For a regular report that kind of highlighting is a built-in functionality in the template, but an IR doesn't have a (editable) template (could be a nice enhancement for a future version though!). But you can override the styles used by an IR, by adding some STYLE tags in the Page HTML Header. First take a look at the on-line demo. You can click the [Edit] button to see the highlighting in action.

So how do we achieve that:
First we need to add a function call to the [Edit] link/button in the IR: Add "onclick=highLight(this);" to the Link Attributes property of the Link Column. This click calls a "highLight" function, defined in the Page HTML Header:

function highLight( pThis ){
$('td').removeClass('current');
$(pThis).parent().parent().children().addClass('current') ;
var empno = $(pThis).parent().next().html();
$s('P36_CUR_EMP', empno);
refreshReport( empno, 'P36_CUR_EMP' );
}
The "refreshReport" is a wrapper for some (standard) APEX functions to execute a Partial Page Refresh of the detail region on the right side of the page. The rest of the code is some jQuery stuff, first do a clean up to remove all "current" classes from the TD-tags - to "un-highlight" a previous selection - and subsequently add that class to all TD's in the current TR.

Next define a "current" style to your own taste. In this example I used:

.current
{
background : transparent url(#WORKSPACE_IMAGES#row-over.gif) repeat-x scroll 0 0 !important;
border-bottom : 1px solid red !important;
border-top : 1px solid red !important;
}
I also tweaked the standard "apexir_WORKSHEET_DATA" styles a bit to get a hover effect:

.apexir_WORKSHEET_DATA tr:hover {
background:#EFEFEF url(#WORKSPACE_IMAGES#row-over.gif) repeat-x scroll left top;
}
- and did some other restyling on the look-and-feel as well - but that's about it!
9 comments

Popular posts from this blog

Showing a success message after closing a modal dialog

APEX 5 comes with Modal Dialogs out of the box. Very neat. Especially for adding and changing data. And to minimise the number of time a user has to click, it could be useful to add a "Close Dialog" process after the actual data processing. When the data processing fails, the Dialog stays on top showing the error. When data processing runs fine, the Dialog is closed ... without any confirmation. And this might be scary for a shaky user.

So how can we provide the user some feedback? On Page 4 of the Sample Dialog Application you can see one solution: up on a Dialog Closed Event on the parent page it does a redirect to refresh the parent page appending the success message of the "Close Dialog" process. This has two drawbacks. First, it probably refreshes more than necessary. And second, if you're using multiple layers of dialogs (dialogs that open other dialogs) the message appears in the "parent dialog".
As an alternative you could follow these steps: 1…

A review of APEX World 2017 - Day 1

Last week the SS Rotterdam was the beautiful location of the largest gathering of APEX Developers worldwide. With around 380 (!) attendees a new high was set. And they came from all over the world : I spotted people from The Netherlands, Belgium, Switzerland, Austria, Croatia, Germany, Denmark, Norway, UK, Ireland and the USA. And I even might have missed one or two ….

The event started with a presentation by the “father of APEX”, Mike Hichwa, talking about "Oracle APEX Past, Present and Future”. Of course everyone is curious what the APEX future might bring: Friendly URL’s, automated testing, more JSON, concurrent APEX versions, third party Oauth 2 authentication (think Facebook, Google), APEX app diff and more, a lot more, REST capabilities. And now we have to wait for APEX 5.2 … and that might take a while! 
After this keynote, the conference split up in three tracks. After the coffee break I returned to to big theatre where Geertjan Wielenga talked about "Finally Javas…

Push changed rows to an Interactive Grid

For pushing changes from the database to the end user, the regular solution is using websockets. A change in a record is detected - using a trigger or using the CQN (Change Query Notification) feature - and a notification is send to a websocket server. That websocket server broadcasts the notification over a channel to all browsers that are tuned in to that websocket channel. Then the browser reacts to that notification, usually showing an alert or refreshing a report. This trick is described on multiple sites, just Google for "oracle apex websockets" or similar.

So back in the old days, we used that notification in the browser to refresh the (interactive) report. But along comes the Interactive Grid (IG). While he full-refresh mechanism still works for IG, an IG has also the option to refresh just one row.  So wouldn't it be awesome that just the changed row(s) get refreshed upon a change in the database, instead of the whole report? Can we do it ... yes we can!
First i…