Read Only condition on RadioGroup item

I have a RadioGroup item on my page that is conditionally set to read only (using a function in the read-only condition type). I have a process that is updating the table with the value of the radio item
ie. update table
set column_name = :P1_RADIO
It seems that when the item gets set to read-only (from the condition), the page value of that item is blank, which in turn sets my DB column value to blank. Why is that? It only seems to work that way on Radiogroups that are readonly.

Anybody know why setting a radiogroup item to read-only (thru read-only condition in properties) makes the value blank?

Similar Messages

Making Read Only A select List Item

Hi,
I am using Application Express 3.1.1.00.09 version.
If the date field is future date then the Select List field should become Read only.
I tried to make "read only".
When I made it "read only" '>[] is displayed???
Does some one have a solution?
Thanks,
Priyanka.

Hi Leckraj,
I assume that
the select list is not displayed at all.means that your page item is not rendered as a select list input control, but it's rendered as text only, right? That's the nature of the read only condition, it will render almost all controls as text only.
About the dynamic action solution. That can be simplified and doesn't require a hidden item or JavaScript.
1) Create a dynamic action which fires for the "Page Load" event
2) As (Server Side) Condition Type set "exists (SQL quer returns...)" and specify your SQL statement
3) Use a "Disable" action to disable your select list page item
The above dynamic action will only be included and executed on the page, if the SQL statement returns a value.
Note: Please keep in mind that dynamic actions are browser based operations, for a skilled user it's no problem to enable the select list and modify the value. To secure it you should add a server side validation to verify if the user is really allowed to modify the value. That's the difference to the "Read Only Condition", because in that case the APEX engine guarantee that the value can't be modified.
Regards
Patrick
Member of the APEX development team
My Blog: http://www.inside-oracle-apex.com
APEX Plug-Ins: http://apex.oracle.com/plugins
Twitter: http://www.twitter.com/patrickwolf

Read Only Conditions - Master Detail

I have a page with a master detail
i created an read only condition and the master passed to read only but the detail not...
Why? Is not possible to put the detail component "read onyl" ?

Hi,
When i understand correctly you want that the form is editable when the user is an admin user
and read only when the user is a normal user.
You can solve this by the use of dynamic actions
to enable and disable items of that region(s)
do this conditional (standard user = disable and admin = enable)
Other solution
When making master/ detail with the wizard choose edit detail on different page
On the edit link you can put a condition (only visible when user is ADMIN)
Regards,
Frank

Textarea with Read Only Condition Type

A have a textarea (database field with Varchar2(4000) with the Read Only Condition Type set to Request != Expression 1. Works fine, except that data presented as a long 1 line text (like a Displayed text) when condition meet (no vertical scrollbar).
Am i missing some additional settings.

the easiest way to get the read-only version of your textarea item to appear more like your read/write version is to add some style specifications into the "Read Only Element Table Cell(s) Attributes" field that's right below where you specified your read-only conditions ("Expression 1" and "Expresssion 2"). as the name suggests, values entered into that field end up in the table data tag for the cell in which your read-only content is placed. added style specifications for height and width would help you control how the text is spread across your page. you can/should also consider using background and color style attributes to color the table cell the way we're used to seeing read-only data ("grayed out"). so though my colors are way off, a string like this...
style="width:16px;height:30px;background:#C5D5C5;color:666666;font-weight:bold;font-size:12pt"
...in that "Read Only Element Table Cell(s) Attributes" field would format your read-only data closer to what you're going for. at the least, it'd give you an idea for the type of control you have.
for extremists, there's also another approach: if you want absolute and total control over the way your textarea item's data is displayed, you could display your item's data in an HTML region instead of as the item directly. for instance, you mentioned you liked that scroll bar. you could achieve the scroll bar by defining your table, the scroll bar class, and table cell in an HTML region. say we saved your textarea item's data to a hidden item called P1_MY_TEXTAREAS_DATA. i'm pretty sure this html would let you show that data in that scrollable non-updatable format you're shootin' for...
<style type="text/css">
.scrollarea{
font-size: 10pt;height:250px;width:100%;text-align:left;
background-color:#ffffff;color:black;padding:0px 0px 0px 0px;margin:0px;overflow: auto;
float:left;}
</style>
<div class="scrollarea">
<table summary="" width="100%"><tr>
<td style="width:16px;height:300px;border:4px;margin-left:4px;margin-right:9px">
&P1_MY_TEXTAREAS_DATA
</td></tr></table><div>
...see? by defining your own table, you get the easy opportunity to wrap it in those div tags that call the scrollarea class. also note that i just referenced the content of your textarea item with that ampersand syntax (&P1_MY_TEXTAREAS_DATA). you could, of course, keep things cleaner by defining your scrollarea class in a css, but that's your call.
hope this helps,
raj

Strange behavior when Popup LOVs has read-only condition and Bug Report

Hi,
I observed an inconsistent behavior of Popup LOVs when the read-only condition is true. In that case the defined lov query is used to map the internal value of the page item to the display value defined in the lov query.
What is the reason for this behavior? Because if the Popup LOV is in "edit mode" the page item value is just displayed without looking up the display value. The display value is just used for the popup lov. Mapping the value is normally a behavior of the popup key lov.
-> The result is that different values are displayed if the page item is in edit or read-only mode. That's not really the behavior someone would expect.
BTW, there seems to be a bug with "Display Extra Values" set to "Yes" in the case read-only is true. If the lookup doesn't return a value it just displays [ ], but because the property is set to yes it should display the value. The Popup Key Lov has the same bug.
Thanks for bringing some light into that behavior
Patrick
Oracle APEX Essentials: http://essentials.oracleapex.info/
My Blog, APEX Builder Plugin, ApexLib Framework: http://www.oracleapex.info/

Patrick,
I've added your comments to a task already in our queue to examine all item types for correct behavior in read-only mode. I've noticed the quirks with display extra values also.
By the way, still interested in your thoughts re: Re: Bug Report: Images broke when using get_blob_file_src and not authentic .
Scott

Read Only Condition Question

Hello,
I would like the fields on the screen to be Read Only when the current
person logged on is not the person that created the Record.
The following case works in the Read Only condition:
NOT Exists (SQL query returns no rows)
SELECT 'X' FROM DUAL WHERE :P90_ASSESSOR_USER_ID = :GLOBAL_USER_ID
But this does not work:
Value of Item in Expression 1 != Expression 2
EXPRESSION 1: P90_ASSESSOR_USER_ID
EXPRESSION 2: GLOBAL_USER_ID
I've tried changing the Expression 1 & 2 fields to be prefaced with : and & and also used V('P90_ASSESSOR_USER_ID') and NV('P90_ASSESSOR_USER_ID'),
but can't get the second way to work. Anyone know why?
Happy Holiday Season!
Carol

Try
IN EXPRESSION 1
P90_ASSESSOR_USER_ID IN EXPRESSION 2
:APP_USER Cheers,
Hari

Authorization scheme for display/read only conditions on item level

Hi All,
I have question. I want to use an authorization scheme to manage if users with a certain role have the permission to either update an item or have the persmission to only see the item or that they don't have permission to see it at all.
So, the input for the scheme would be: 1. user role 2. the current page 3. the current item.
The output would be: 0 (update) 1 (read only) 2 (not displayed).
I think I can manage that.
And I can attach this schema to the items.
So far so good.
But how can I make it so that the 0,1 and the 2 will actually do what they need to do?
I have been thinking about making a function like GET_AUTHORISATON(ROLE,PAGE,ITEM) output: 0,1,2 but I still can't figure out how to connect this with the functionality I want to achieve.
Can somebody give me a hint?
Andre

Thanks Hari,
Thanks, it works, almost, but what if items are mandatory on a page, but not always mandatory?
If a user has a certain role, some fields are manadatory, otherwise not.
Again, a function would do the trick as far as the input and output information
something like IS_MANDATORY(USER_ROLE, CURRENT_PAGE, CURRENT_ITEM) but how can I make it work?
I guess a PL/SQL validation like:
IF IS_MANDATORY(USER_ROLE, CURRENT_PAGE, CURRENT_ITEM) THEN ITEM IS NOT NULL
END IF;
Andre
PS: personally I think item level security is not something you wish to implement in your system. I prefer different screens for different roles.
Far more straightforeward. Easy for maintenance. When something disfunctions, it's far more easy to pinpoint the location of the cause.

Tabular Form - Read only condition for certain users

Is it possible to make a select list field in a tabular form read-only to certain users? Here's the situation:
The tabular form lists the users who need to select "Approve" or "Reject" in that field (they are approving or rejecting an engineering change)
I want all of them to see the approval/rejection of their team, but only have access to edit the select list associated with their record.
Thanks in advance.
Apex 4.0.0.00.46

You could use either "authorisations" tab or "conditional display" for the relevant column attribute.
Report Attributes->Column Attributes->authorisationsIt would be better to have some more detail about what you are trying to get (maybe a quick mock up of the form, for example) but, I can envision something along the lines of the following:
For each approval/rejection field:
1. Create an authorisation appropriate for access to to each approval/rejection field e.g. authorisation scheme "FOO"
2. In the relevant fields column attributes, set the authorisation to "FOO"
3. now create a read only "public" copy of the above field, using the "display as text (based on LOV does not save state)" - set the authorisation for this field as "{NOT FOO}"
(if you don't want to use authorisations, you could build an equivalent using "conditional display" instead, which is basically the same thing, except column specific)
The downside is of course that you're duplicating fields in your query, which creates a bit of redundancy. There may be better ways to achieve this (maybe you could make use of the APEX_ITEM api, for example) but this is fairly easy to set up IMO.

How to make rows read only conditionally

Hi All,
I have a query region and when i select it shows the data in a table region, now based on a particular column i want to set the entire row read only.
Please let me know if it is possible.
Thanks
Tom.

Hi All,
I have finally figured out a way, i have created a SPEL attribute and set it to the read only property to all of the view attributes, and as soon as the query is executed i am filtering the rows based on my column criteria and set the value of the SPEL attribute to true.
Thanks again.
Tom.

Bug report: Read Only Condition Type

See
http://htmldb.oracle.com/pls/otn/f?p=24317:105
The item with label "readonly" has a readonly condition set to 1=1 so it should always display as readonly. But no matter what item type I change it to, setting this readonly condition makes it dissapear.
Thanks

Ah, I was mixing up "readonly" and "disabled". I expected readonly to show up as a regular text field but non-editable.
You are right, thanks for clearing that up.
Hope this bug with the readonly feature gets fixed soon. The workaround (define 2 "mutually exclusive' items and conditionally display one or the other) gets to be a pain since that readonly feature is (supposed to) solve this problem much more elegantly.
Thanks

Possible to make an item editable for certain users and read only for other

Is it possible to make an item editable for certain users and read only for others?
I've been able to accomplish this by taken the select statement that I used to define an authorization scheme, placing it in the Read Only condition of the item. However, I would like to simply reference the authorization scheme to utilize caching, and to help keep things cleaner for future maintenance.
Is it possible to reference an authorization scheme in an item condition similar to the way another item can be referenced by preceding it with a colon (i.e. :P1_First_Name)?

Thank you, your suggestion worked.
It would be nice on a future release of APEX if a drop-down box existed under the Ready Only section that would allow an existing Authorization Scheme to be selected or negated when applying the Read Only attribute to a form item.

Are 'read only' items causing my automatic row processing to fail?

I have a form that uses automatic row processing to update my table.
I recently had to add a check to lock down the fields using the read only condition where a record has been 'approved'. So, I turned off all of the fields and hid the update button.
Now they want me to check to see if the user is a manager, and if so, allow them to see the update button, and make a single field on the form modifiable.
I have the user identified as a manager, and can make the field accept the change (a yes/no combo box). Yet when they click the update button, the form just sits there. A branch is supposed to fire on hitting that button, taking them back to the previous report, but it doesn't happen. The source of the combo box in question uses a column on the table, and works fine when the form has all of the fields showing for modification.
I had some validations that I finally set to never fire, thinking that they were failing and just not giving the error messages. I know a bad sql or pl/sql atatement in a validation will cause the form to just keep sitting there doing nothing, and thought it might help.
Several of the various fields are combo boxes, several are text boxes.
I'm stumped.
Shall I keep the regular update button hidden whether it is a manager or not (because it has been 'approved'), and enable a new button that fires off a process to update the one field that the manager may want to change? Does making a field 'read only' always have a detrimental effect on the auto processes I've been counting on? Is that if fact what is happening now?
Thanks in advance for any advice or comments on this.
Clayton

Hi, Scott.
My version is 3.0.0.00.20
I have received info to set up the application, though I have not activated it as yet. I'm reluctant to try to load up the various tables to make it work. It could be done.
My workaround is to that the user (a manager) fires off to another form to show an individual record, and ask if he/she really wants to make this change. On submit, they will be taken back to the original locked down form, and I will update the single field in that process of returning them. This will actually be a plus, in that I expect to show them all of the 'duplicate' entries for that item, and show them that by 'activating' this particular item, they will 'deactivate' the one duplicate that is currently active. Or, if they are deactivating the sole item that is active, that there will in fact be no active items in the system. Convoluted as heck, but they swear this is how they've been doing business with their briefcases and file cabinets of Excel files. I'm surprise they even float at this point (these are ships we're talking about).
This all may be due to the form originally having a next/previous/count process once arrived at my clicking on the edit button of the report of items. All of that has been hidden away, and though the fields exist of the form, they are not used. They only see the current item that they clicked on from the report.
I read up a little on session state, as well as posts with the debug error I was getting. I'm still not on board with the whole issue of 'state'. Items stay as they are until they're changed, no? I suppose that sounds simplistic.
One of the things that caught my eye was several combo box lists that on read only mode, showed [] square brackets. Which, in some cases is okay.
What I'll try to do is set up a public application - for future use if nothing else. I'm going to be working on this for awhile. I have more than a bit of work to do to cleanse the data as well as get rid of the single sign on requirement (I'll assume that I should have to do this) in order to share the app.
I know you're expecting me to have this up and running for you to look at, but I'm under the gun. And they actually like my workaround.
I'll keep everybody informed, one way or another.
Clayton

Help needed with 'Conditions' for field with read only on demand

Hy guys,
I really need your help now, i have two items named P22_LOGIN_TYPE (..wich can be 'Default' or 'Special') and P22_PASSWORD, i need to turn to 'read only' the second item when the first item is 'Default', i'v tryied the conditional option but with no success, i know is managed from there but it's not working for me, it seems that i don't know exactly how to do it. By the way, i have APEX 2.2.
I need an exact guide (explanation) on how to do it, thank you very much.
Best regards,
Victor

Firstly you could set your First item to be a select list with submit. Make the branch go to the same page.
Secondly, on the read-only conditions for your second item, use the condition when item in expression 1 = value in expression 2, and set that to 'Default' in expression 2.
Essentially this will re-submit your page when you make a selection either 'Default' or 'Special'. If 'Default' is selected, then the PASSWORD item will be rendered as read-only. If you don't want to display the PASSWORD item at all, you can put the above condition for the read-only, into the conditions section of the item.
Hope this helps and is not too confusing. It reads a lot worse than it actually is ;)
Cj

AJAX and Read-Only Items

I used the examples from Carl Backstrom and Denes Kubicek to get my cascading select list working.
I have two select list fields (Origin and Type) that I use to determine the data to appear in a third select list field (Customer).
With help from people on this forum I was able to get things to work.
Now I have an issue when I conditionally make the Origin field "read-only".
When this occurs, data appears in my "Customer" select list on the INITIAL display of the form.
However, when I change the value in the "Type" select list field, no data appears in the Customer select list.
If I change the "Origin" field to NOT be read-only, I can change the value in the "Type" select list field and everything works OK.
I hope I have given enough information.
THANKS in advance.
Raymond

Raymond,
It looks like read-only select is really special:
(I replaced < > with [])
When select is not read-only generated html is:
[select name="p_t01" size="1" id="P1_ORIGIN_NO"
onchange="get_AJAX_SELECT_XML('P1_ORIGIN_NO','P1_DISPLAY_SSA','','','P1_CUSTOMER','CASCADING_CUSTOMER_LOV')";
[option value="%null%"]%[option]
[option selected="selected" value="001"]DOTIKI MINE[option]
[option value="S01"]ECO COAL PELLETIZATION NO. 12, LLC[option]
[select]
It means that P1_ORIGIN_NO in get_AJAX_SELECT_XML will be "001"
But when select is read-only your html code is:
[input type="hidden" name="p_t01" value="001" /]
[span id="P2_ORIGIN_NO"
onchange=
"get_AJAX_SELECT_XML('P2_ORIGIN_NO','P2_DISPLAY_SSA','','','P2_CUSTOMER','CASCADING_CUSTOMER_LOV')";
DOTIKI MINE
[span]
[pre]
P2_ORIGIN_NO in get_AJAX_SELECT_XML will be "DOTIKI MINE" which I think is wrong.
It looks like for read-only you need hidden item with code of
drop - down list or somehow you have to reach [input type="hidden" name="p_t01" value="001" /]
Lev
Message was edited by:
le

Read only text Items uses the maximum width

Folks,
I have a form with 3 regions and each region has 6 or more text items each with a different width (40, 30 24, 2...). I am using a Read Only Condition Type on all these items to disable them. I am setting the background color as bgcolor="#DCDCDC" in the Read Only Element Table Cell Attributes.
All my elements are disabled (Gray color) but with the maximum width of 40 bytes. I don't want a 2 byte text item 40 bytes long and grayed out. How can I set a specific width for individual items in Read only Condition? Please help
Thanks
Raje.

Try this alternative by disabling the HTML Form Item at the required process point.
I added this JavaScript to the HTML Header of the page which will allow me to disable the required item, plus set its background and color:-
<script language="JavaScript1.1" type="text/javascript">
    function disableFormItem(p_item, p_background, p_color){
                    disItem = document.getElementById(p_item);
                    disItem.style.background = p_background;
                    disItem.disabled = true;
                    disItem.style.color = p_color;
</script>In the Region Footer of the Region where my items are located I added this JavaScript code:-
<script language="JavaScript" type="text/javascript">
   ** Only disable the required Form Items if the Primary Key value is present,
   ** in this case it is P12_UEI. (Won't be present for new records as populated
   ** by on-insert db trigger and sequence.)
   if (html_GetElement('P12_UEI').value > 0)
      disableFormItem('P12_URESI', 'lightyellow', 'black');
      disableFormItem('P12_UZI', 'lightgray', 'black');
      disableFormItem('P12_UBI', 'lightgray', 'black');
</script> The resulting page is a lot better looking than using the APEX read only text item.
Regards,
Phil

Read Only condition on RadioGroup item

Similar Messages

Maybe you are looking for