Make Tabular Form Conditionally Read-only
If you decide to use an editable tabular form to present a number of records for viewing and/or editing, but you have some users who are only allowed to view the data but not edit it, you’d think you could set the “Readonly” condition on the region; but this condition is only applied to any extra region items you add, not to the editable items within the report itself.
Here’s my tabular form, with the records still editable:
One way to get around this is to have two separate report regions on the page – one is the editable tabular report, the other is an ordinary standard report that doesn’t have any of the edit capabilities – and use conditions to hide one or the other depending on the user’s authorisation.
Another way is to use conditions and jQuery to make all the items in the tabular form readonly:
1. Put a condition on all the buttons (e.g. “Add Row”, “Delete”, “Save”, etc) so they are not shown if the user doesn’t have edit privilege
2. Put the same condition on the Multi-Row processes so that they will not run if the user doesn’t have edit privilege.
3. Set the static ID on the region so jquery can find it:
4. Add a Dynamic Action to make all the input items within that region disabled:
Event: Page Load
Authorization Scheme: {Not Editor} (this is just an example where I have an Authorization scheme called “Editor”; alternatively you could set a Condition instead)
True Action: Execute Javascript Code
$("#linesreport input, #linesreport select").prop("disabled",true)
Now, when the page loads, if the user doesn’t have edit privilege the items are rendered readonly, e.g.:
There are other variations on this theme, e.g. we could target the jQuery expression to just the text inputs while still allowing the user to use the checkboxes (e.g. if there was some action that we wanted to allow). Of course, if I wanted to hide the checkboxes completely, I’d just put the authorization on the [row selector] column in the tabular report definition.
About Jeffrey Kemp
Application Designer & Developer at Oracle specialising in Oracle APEX (Application Express), Oracle SQL and PL/SQL. Oracle ACE Alumni ♠️. Piano player, father, husband, Christian. The views expressed on this blog are my own and do not necessarily reflect the views of Oracle.