HTML DB - Read only - Disable elements

Hi everyone,
I made a javascript to disable elements when my user is in a particular group. It's ok. But, I want my disable elements look a like "not disable elements". My disable elements are less attractive for the eyes. The only difference that I want is disabled := 'true' or disabled = 'false'.
I try also Read only.... but the frame of my elements disappears. How I can add attributes to those elements (check box, textfield, radio group button) to look a like "not disable elements" ?
Thanks. Bye.

Hello,
Your css style is bad.
try something like this
style="border:4px solid #CCC;"
here is a nice primer on borders in css http://www.w3schools.com/css/css_border.asp
Carl

Similar Messages

Getting Nullpointer exception if i try to get value from messageChoicebean in read only/disabled mode

Hi,
I have standard notification page and there are three messagechoice components in that page. my requirement is to set default values for those three components and make read only/disable the components.
I could be able to achieve this through controller extension, but in standard code some where it is trying to get the values from these three components as a result getting null pointer exception. how to make component values should be available in readonly/disabled mode to standard code.
Regards,
Satya.

Hi Sandeep
Thanks for the update.
Page: /oracle/apps/fnd/wf/worklist/webui/NotifDetailsPG
Following is the code used to set the messageChoice to set default value and make it disabled. when i submit the page using approve button, it is trying to get the value from disabled dropdown.
It is returning null value. If we remove disable property then it is returning value. my requirement is to set the default value and disable the dropdown. pls let me know any alternative to do this.
OAMessageChoiceBean oabuttonbean=(OAMessageChoiceBean)webBean.findChildRecursive("NRR0");
oabuttonbean.setSelectionValue(pageContext,"PRORATE");
oabuttonbean.setDisabled(true);
Thanks,
Satya.

Edit, read only, disable, blur items. Which to use?

I've searched the forum and have found some threads that somewhat discuss my question, but none have addressed it specifically.
I have a page that has 20 or so items on it. There are 3 fields (like status) that determine which items may be edited, so whether these items may be edited or not will change from row to row.
As I've stated I've searched on the words disable, etc. and have some ideas on how to best handle this process. For one, I don't want to use disable. But, I'm new to ApEx and don't know the best route to take. Should I use the ReadOnly setting on the item and code using PL/SQL? Or, should I handle it in JavaScript and check the status, etc. there and blur the item?
I want to do this the best way, because I want all of our future apps to use the same concept. And, I want to use a concept that will run efficiently.
Thanks in advance for your response.
Tony

I have done this several different ways and have found that it has been best to utlilize pl/sql from the Read-Only using "pl/sql function body returning a boolean". From the read-only, we call a package that handles all the READ-ONLY checks (we put the call into every field by default).<br><br>
Then all we have to do is pass in the current page number and the userID and the package determines whether or not that user is credentialed to view the items on the page item by item.<br><br>
For your example, you could pass the values of the fields on the screen and get your boolean result back for read-only. The advantage to the pl/sql returning boolean is that you can impact the whole application by changing the package that does the credential checking, as opposed to creating and editing page specific javascript for all pages where you want to protect fields.

Ho to make a read only / disabled input text mandatory?

Hi All,
I'm using ADF to display data for a human task. Part of my requirement is to display a payload attribute as an output text/ read only input text. If this is null, the form should compel the user to choose from a list of values.
How do I make an output text mandatory? Is there another way around this?
I tried creating an input text and making it read only and mandatory, this doesn't work. Apparently, you cant make a disabled/read only input text mandatory?
JDev : 11.1.1.4
Thanks
PP

Hello! What does mandatory field mean for you? If there should be validation while saving, it will be: faces message will be shown with text, as it is defined in business rules in entity object. If you just wish to see blue “*” in front of label, just use “panelLabelAndMessage” component with “showRequired” property = “true”. If you wish to see some red frame around disabled field or button, if it has null value, I don’t know how to help you, but wish to know how to do that too.

Read-only textbox and/or disable buttons in Infopath 2013

In a InfoPath 2013 custom list form, my requirement is to make textboxes read-only, disable buttons, and/or create new buttons so users can not update fields in a custom list once the user has updated data in the list. Basically after the user hits the 'save'
button so that the data is saved.
The requirement is not to set up custom permissions since my SharePoint administrator said I should find another option. This administrator said he does not see a reason for only an 'add' permission.
Thus can you tell me how to meet my requirements? Can you show me screen prints, pictures, or urls on how to solve the problem?

Hi,
According to your description, you might want to prevent users from editing the existing items.
There are two workarounds I can provide as below:
As the first workaround, you can remove Ribbon from SharePoint InfoPath List Form via modifying the OOTB settings of InfoPath Web Part.
Here is a link about more details, you can use it as a reference:
http://the-north.com/sharepoint/post/Remove-Ribbon-from-SharePoint-InfoPath-List-Form
As the second workaround, you can apply the CSS code below to your page, it will hide the “Edit Item” button in the Ribbon:
<style type="text/css">
#Ribbon\.ListItem\.Manage\.EditProperties-Large{display: none !important;}
</style>
About how to add JavaScript/CSS into SharePoint page:
http://blog.cloudshare.com/2012/10/29/how-to-insert-custom-javascript-code-in-sharepoint-2013-pages-part-i/
Best regards
Patrick Liang
TechNet Community Support

Render HTML text as read-only field

Hi,
I want to display the text entered in a rich text editor as "true" HTML in read-only mode. If I make the field read-only (Read Only = Always), the display is screwed up quite badly. Obviously CSS gets in the way somehow.
Here's how to see my problem:
- create a report/form with a text field (e.g. a CLOB, but that doesn't matter), displayed as "Rich Text Editor", and enter some text.
- create the same report/form again, this time making the field read-only.
Quite a difference...
Has anybody a quick answer?
Thank you,
Thomas

Hi,
yeah, that would be ok. I tried it already, but if I use something like "&P8_HTML.", the HTML text is displayed and not rendered.
But I followed this up again after reading your advice, and I found that if I enter true HTML code as the region source, it's rendered as expected. The rest was simple:
- create a separate region for the HTML display (as you proposed).
- make the region type "PL/SQL (anonymous block)".
- use "BEGIN \n htp.print(:P8_HTML); \nEND;" as region source.
Thank you all very much for this instantaneous help!
Cheers,
Thomas

How to make a page READ ONLY / all fields are DISABLED ?

Hi all,
I am using ONE page to do ADD/EDIT/DISPLAY data. When users are in DISPLAY mode, I want all fields on the page to be read only / disabled.
How is the best approach to do that ?
(other than going to every fields and set the ReadOnly/Disabled property)
Thank you for your help,
xtanto

Hi Xtanto,
My business logic is somewhat different - I don't do this for new/editted rows, but based upon other security. You could certainly set something in your backing bean based upon a user clicking "new" or "edit"
John

Authorization RADIUS - read-only user on FWSM

Hi support community,
I am experiencing an issue while trying to create some read-only users on my FWSM.
I've setup the authentication on my RADIUS Server, which works fine, and put the aaa authorization command LOCAL command.
I've also set the commands - associated priviege :
privilege show level 3 mode configure command dhcpd
privilege show level 5 mode configure command privilege
All this things works great when i authenticate locally on the FWSM.
However, this is not working whe authenticating via the RADIUS server:
aaa authentication enable console MY_RADIUS LOCAL
aaa authentication http console MY_RADIUS LOCAL
aaa authentication ssh console MY_RADIUS LOCAL
And i set up the authorization locall, because i dont run any TACACS server :
aaa authorization command LOCAL
I managed to make this work on ASA, by sending RADIUS attributes (cf a document that i can't find anymore...).
So what are exactly the differences between asa and FWSM ?
On my ASA there was a command i could not run on the FWSM :
aaa authorization exec authentication-server
(i am running version 4.1 on FWSM and 8.4 on ASA).
Thank you for your help.
Florian

You really need to see the example given here,
[Read only user for a schema|http://arjudba.blogspot.com/2008/09/create-read-only-user-for-schema.html]
[Global read only user|http://arjudba.blogspot.com/2008/09/how-to-make-global-read-only-user.html]

Read only af:inputText being rendered as "span" instead of read only input

I am using JDeveloper 11.1.1.6.0
I have noticed that when using components such as "af:inputText" and "af:inputDate" with the "readOnly" attribute set to true, the resulting render is a label as a "<span>" element as opposed to a read only <input> element which I would have expected. I see the expected behavior if I utilize the JSF "h:inputText" component with "readOnly" set to true, however I cannot utilize the JSF component as it does not appear as though I can get "autoSubmit" behavior to work with the JSF component so that will not work. To add on to the oddness of the behavior, if the af:inputText has its Rows attribute set to be greater than 1, it will render as a read only <input> element as opposed to a label.
In addition, the af:inputText's default readOnly form looks glaring when using the simple skin or other skins based on simple. It adds a box that wraps around the exact length of the text in the inputText as opposed to the amount of area that the inputText would have consumed if it was not in "readOnly" mode.
Is there any way to properly get the af:inputText to render as a read only input as opposed to the label that it is currently being displayed as?
Thank you.

Hi,
its a decision made by the component renderer. If this is a problem for you and if you have a customer support contract then you could file a service request for a change.
Frank

HTML-DB 1.6 (HTML code for read-only elements)

Hi everyone,
We have elements that we want to be readonly or disabled. We put this code under html form elements attributes
readonly="readonly" style="background:#ddd none;color:#222;"
It works well.
But we want other elements to be read-only under a read-only condition type
(HTML cell attributes on read-only), we want a kind of shadow (like we got with read-only) or a little border. I tried style="border=4px;" but everything still to be the same.
It’s not easy HTML-DB (1.6) doesn’t offer us very good example.
How can we do this ? We need help.
Thanks. Bye.

Hello,
Your css style is bad.
try something like this
style="border:4px solid #CCC;"
here is a nice primer on borders in css http://www.w3schools.com/css/css_border.asp
Carl

Read Only and HTML Table Cell Attributes

Hi Guys,
I believe i have come accross a bug - i'm been working on a form that can be filled out and printed - when going into print for sake of the output looking nice i set the form element to read-only.
As soon as an element such as a drop down box, text feild, text area, etc which display as "[selected value]" in plain text in read only mode, are changed to the read only mode apex seem to ignore the html table cell attributes.
For example i have a id number in the top left and then a version number in the top right. Both use a text feild; the top left uses 'width="100%"' for it's HTML Table Cell Attribute to push the right cell to the right. and the right cell has 'align="right"'. Now this works fine when read only is off... but as soon as read only is on, both the width and the alignment are totally ignored, and i can't find any sign of them in the code.
Because this is for printing; using the "disable" on the form element instead of "read only" function, isn't appropriate as disabled will make the elements faded and hard to read when printed, and keeping the elements as is will allow the user to edit information on the print screen - which is not appropriate.
Is this a bug? Will it be fixed soon? Is there any work around?
Cheers,
Alex

Use the "Read Only Element Table Cell(s) Attributes" in the Read Only region of the Item edit form.
Scott

Can I suppress HTML escaping in a read-only item?

I have an item that is displayed as read-only. The item contains HTML markup. HTML DB seems to automatically escape special characters in the item value.
Is there a way to suppress this?
For example, I have a text input item with the value:
<b>Hello</b>
(that is, it contains the bold elements which I want to output as is).
HTML DB seems to be escaping the item value so I see the bold elements in the browser and what I see in the page source is: &lt;b&gt;Hello&lt;/b&gt;
There doesn't seem to be "escape special characters" / "don't escape special characters" options for read-only mode like there is for "Display As Text" items. Can anyone suggest a workaround?
Thanks,
Eric

Eric - Text input items are escaped on output whether they are read-only or not. But to answer your question generally, APEX does not emit input items of any type to the browser without escaping them unless there is a guarantee that they have been escaped on input, e.g., when passed in through the URL, or that they acquired their value from within the application. These guarantees apply only to non-POSTable item types such as Display As Text (does not save state) items and a couple others. So in short, we observe the rule (which should be observed by app developers) that it is never safe (from an XSS-protection standpoint) to emit a POSTable item without escaping it first.
In your case, can you define a safe item type (Display as Text, does not save state) and set its source to the markup-containing item that you are now displaying as read-only? If so, you can conditionally display only the safe one and hide the other.
Scott

Change programmatically textfield to textfield(disabled) , no Read Only

By pressing on a edit link of a report column I enter a page with a form
and would like to disable some of the textfields
I do not like to make them READ-ONLY , but to switch from
Text Field --> Text Field(disabled, saves state).
Maybe this is possible by using javascript ?
Any ideas ??

Hello,
you were right this is a solution.
Only the textfield(disabled,save state) has not a database column as source but
the source is the normal textfield. Or else there is a conflict because two textfields
address the same database column...
I wonder if it is possible to change the html properties of a textfield (input) conditionally, caus there exists the html property "disabled".

Problem with HTML in a read only textarea item

I'm working on a messaging system for our site. For the body of the message, we use a standard textarea item. However, if we come to the messaging page from a certain page in our system, then we pre-load the textarea item, and make it read only. The only problem with this is that there are HTML tags in the body that we try to pre-load. This is causing problems because they aren't being interpreted as tags, but are being displayed as text. If I make the textarea editable, then everything looks fine, it's just when I set the area to be read only that it doesn't work. Any thoughts on how to fix this? Thanks!

Not always. A user is allowed to edit that area in most circumstances except for when the user arrives at the page coming from 1 page in particular. In this case, then the field is read-only. At all other times though, it is editable.
As a workaround, whenever I know I'm coming from this page, I set a variable, and if the variable is set, then I use a Display Only item and then hide the Textarea. If the variable is not set, then I hide my Display Only item and show the Textarea. Not very elegant, but it works.

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

HTML DB - Read only - Disable elements

Similar Messages

Maybe you are looking for