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

Similar Messages

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

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?

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

Make expense report read only after approval

Hello,
Please guide on how to make an expense report read only once it is approved and no change option should be enabled on enterprise portal. I have tried all the combinations of security in the ESS roles inside ABAP but not able to find the right combination. Please suggest.
Thank you.

it needs P_travl authorisaiton
Create a new Travel Request or Expense report (AUTHF W)
Change open travel Request or Expense report (AUTHF W10, W30)
Change returned Travel Request or Expense report (AUTHF W11, W31)
Create Expense report from approved Travel request (AUTHF W21)
use the note 1402925
If you create an expense report based on a not approved travel request,
the system asks for authorization to change this request
(W11 or W10) for AUTHF and then 30 or 31 for AUTHS.
THis combination is of course given by your P_TRAVEL object.
You need at least 2 seperate P_TRAVEL objects, whereas only 1 of them
contains AUTHS values for expense report. This must only contain
W2* and 30 / 31. Hopefully this could help.

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

This operation is not available for read only field 'Type MVF'

Hi All,
We are using OrderToCash PIP and we are on Siebel 8.1X.
While Synching the customer from Ebiz to Siebel facing the following issues:
Method 'WriteRecord' of business component 'Account' (integration component 'Account') for record with search specification '[Row Id] = "2d3434313239353"' returned the following error:"This operation is not available for read only field 'Type MVF'.(SBL-DAT-00402)"(SBL-EAI-04451)
Please suggest us what steps to be done in Siebel.
Thanks
Maanasa

First check the process why this is calling Account BC WriteRecord(). The field "Type MVF" might be read only and this sync process is trying to update this field which is read only. This is the reason for the error. Check the OM log / EAI Obj Manager Comp log (set log level to 5) and check.
Joseph Arul Dass

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

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.

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.

Oracle Report reading only upto 1600 lines

Hi all,
Just would like to post an issue regarding oracle report.
My version is DS 10g n i have a code which is approx 2000 lines, the issue is that my query executes till near about the 1600 but the rest is omitted.plz throw some light in this.
Thanx
Ron

What are you talking about exactly:
i have a code which is approx 2000 lineIs this a pl/sql procedure?
my query executesOr is it a very long query?

Read Only Display Settings Help

Hello,
I am trying to control what some users can see in a page. Right now I have an item field (Roles) display as checkbox. Roles is a field in my table that I created with RolesA, RolesB, RolesC. Note: these are not htmldb roles.
In my Edit Page Item --> Read Only Display Settings --> Read Only Condition Type --> PL/SQL Function Body Returning a Boolean. Under Expression 1, I coded:
return not htmldb_util.current_user_in_group(p_group_name => 'APP Admin')
I want this item to read-only unless the user happens to be a member of group 'APP Admin'.
The expression is not working. It seems that no matter what user is logged in they can modify this item. Is there another way I can do this for controlling what my RolesA, RolesB, and RolesC can modify? BTW, this item is a checkbox.

Dung,
That API seems to have a bug, it returns true/false/null, so you could use 'return not nvl(htmldb_util.current_user_in_group(p_group_name => 'APP Admin'),false)' to get a false value.
Unfortunately there's another problem: using the read-only attributes for checkbox or radiogroup item makes them hidden. My suggestion would be to create another item that has disabled="disabled" in the HTML Form Element attribute in the item definition and display that item or the non-disabled item alternately, using conditions based on the current_user_in_group logic.
Scott

How to display the "display values" in READ Only mode for a SHUTTLE

Hi,
I have a form item of type *'Shuttle'* and using the following LOV.
   select DEPTNAME d, DEPTNO r
    from DEPTIn normal mode..it displays the department name and internally store the Deptno..
Now I converted this item to Read Only mode using Read Only Condition Type
the problem is as soon as it becomes read only...it displays the deptno....not the department name
            Department-   10:20:30How can I display the "display values" i.e the actual department name in read only mode..
            Department-   Department1:Department2:Department3Thanks,
Deepak

Hi,
It seems feature. Shuttle is span tag when it is read only.
Work around could be that
you compute display as text item with LOV display value according shuttle session state and show shuttle and this item conditionally depend case
Br, JAri

Read Only Element Table Attributes not working since we migrate 3.0.1

Dear all,
I have a page to dispaly the content of a journalling table and highlight the changes in red.
To do it, the guy before me use the read only.
In the read only condition type he put pl/sql expression.
the expression is :P120_OLD_DEADLINE_DT NOT LIKE :P120_NEW_DEADLINE_DT
And in Read Only Element Table Cell(s) Attributes the code is bgcolor="#FF0000"
In 2.2 the background was red and in now the the background doesn't work.
Do you have an idea why in 3.0.1 it doesn't work.
Thanks
Eric

Scott,
The background works only with the read only condition always.
In my new item the select is select 10 from dual.
In the read only condition I select Value of item in expression 1 is not null.
I put in expression 1 the name of my item :p997_test.
The read only doesn't work.
In your test, did you select the condition always or you chose something else ?
Thanks
Eric

Bug report: Read Only Condition Type

Similar Messages

Maybe you are looking for