Disabled Submit Button

At the time of submit the submit button is disabled. Is there a way to disable this functionality for certain form?

by default, on nextensio forms, it is done automatically, but what you seek is done by javascript. something like: I found this here: http://www.houseofscripts.com/scripts/javascripts/disablebut.htm As you can see, this code allows us to do disable any button - either Submit or Button. Just add onClick="Disab (1)" <HTML> <HEAD> <SCRIPT LANGUAGE="JavaScript"> function Disab (val) { if(val=="1") {form1.Submit.disabled=true} if(val=="2") {form1.Button.disabled=true} } </SCRIPT> </HEAD> <BODY TEXT="000000" BGCOLOR="FFFFFF"> <FORM name="form1" method="post" action="" enctype="text/plain"> <input type="submit" name="Submit" value="Submit" onClick="Disab (1)"> <input type="button" name="Button" value="Button" onClick="Disab (2)"> </FORM> </BODY> </HTML>

Similar Messages

Spry validation disables Submit button

Hey,
I'm using spry validation on text boxes and dropdown menu's
.. for some reason, on certain pages when the form is submitted and
validated, if there's a problem with one of the fields, the submit
button is disabled and won't enable again. Any ideas on how I can
stop this from happening?

Bump :o)

RESOLVED - iExpense: Disable Submit Button based on checkbox not working

Hi,
We have a requirement for a checkbox in iExpense Review form(FinalReviewPG) where there should be a checkbox stating the terms and policies are met etc. Unless the user checks the checkbox the SUBMIT button shouldnt be enabled. I am creating the custom checkbox using personalisation in the page with initial/unchecked value as N and checked value as Y. This is created at SITE level.
Now I have also created a custom controller extension xxButtonCO to extend the standard ButtonsCO controller which should do the disable/enable of the button OIESubmit. I ported this controller to the custom top and have extended the controller to both OIE Expenses Entry Flow function and Internet Expenses responsibility. But the checkbox though visible is not affecting the SUBMIT button. Also funnily, I save the controller class as xx.oracle.apps.ap.oie.webui.xxlcButtonCO and click apply only to see this concatenated to apps.ap.oie.webui.xxlcButtonCO / Function.
Is that causing an issue? Also, sometimes I just run into an arbitrary NULL pointer exception and other times it says oracle.apps.fnd.framework.OAException: Could not create Java class. I have verified the class file not java file is in correct directory and has right permissions.
What could possibly be wrong here?
Edited by: 865082 on Jun 15, 2011 5:33 AM
Edited by: 865082 on 20/06/2011 22:21

Hi Kali,
Many thanks for your response. I have quit trying to run this page directly from the instance and am now trying to do this firsly from the JDeveloper. The same issue is occuring from that end as well. My checkbox value is not getting recognised in the code. The checkbox is added to the Business Expenses tab and the intial/unchecked value is N while the checked value is Y. I am trying to control the submit button in the buttonbar based on the checkbox value using the following command
OAMessageCheckBoxBean cbbean = (OAMessageCheckBoxBean)webBean.findChildRecursive("XXReviewCheck");
where XXReviewCheck is the checkbox ID. However the print statements show that the cbbean is null. It is definitely calling the controller and trying to figure out the value. The value is just not coming to this section. Any ideas?

Custom validation is disabling submit button

Hi there,
I am using the update/insert feature within ADDT, but wanted to use my own validation using JavaScript. Everything works fine, the validation pop-up works etc, but the submit button is disabled. I'm guess that the transaction has started with the ADDT, but the javascript has stopped it. How can I get around this? any suggestions welcome...
Thanks in advance...

Hi,
Have you tried different browsers to double check. I remember a couple months ago I was helping someone with a similar problem, it worked in one browser fine but not the other so we had to rewrite the code. Initially the code looked fine but just didnt work in IE.

Disabling submit button after resetting the form.

Hi. I'm new to JSF/Richfaces and there's something I'd like to do that I just can't figure out.
Currently, I have a form with various fields to be edited, and the standard Submit and Reset buttons. The Submit button is disabled until a user changes a value on the form, and then I enable it using an A4J event. My problem is that I would like to disable the submit button again if the user clicks Reset. I'd like this to be completely client-side if possible, which I understand would require some javascript to implement, but I haven't been able to come up with a solution that works. Does anyone know how I could do this (with an example, preferably)?
It's a pretty simple scenario, but here's the button code anyway:
<h:commandButton id="submitButton" value="Submit" action="#{dataBean.submitForm}"
disabled="#{! dataBean.pageEdited}" />
<h:commandButton value="Reset" type="reset">
<a4j:support event="onmouseup" reRender="submitButton" />
</h:commandButton>

I see, thanks! I looked up another example on using the DOM (I told you I was new!) and created the following javascript function, and it worked perfectly. I like that it automatically re-renders the button too so I don't need an A4J event.
function disableSubmitOnReset(){
document.getElementById('main_form:submitButton').disabled = true;
}Definitely as simple as I figured it would be. :P

Disable submit button after clicking on it

Hi all,
I m beginner at working with JHeadstart.
I searched through this forum but I couldn't find any solution for my problem,
Now, i want to know how i can disable save button (or any other button) after clicking on it.
I dont know, but It can be done by writing .vm, do u have an idea?
Thanks for ur kind replies:)

Hi,
If you only want to be able to submit once you can add the following disabled property with EL expression to your save button in the jspx page.
disabled="#{adfFacesContext.postback}"
The save button will only be clickable upon initial entry of the page.
To persist this change when generating your application you can use a custom velocity template. Have a look at the JHeadstart developers guide, paragraph 4.7
http://download.oracle.com/consulting/jhsdevguide1013.pdf
If you want to have an insert only form you can also use an insert only View Object (go to the view object editor and select the tuning tab and the "No rows" option)
Regards,
Ruud Bijkerk
JHeadstart team

Disable submit button after submission

We have a form that we have distributed to multiple users. The form is set so that submissions go to a pre-defined server location. The problem is that some of the users submit the form multiple times (not sure why). Perhaps they don't notice the message that says "Form submitted". In any case, we would like to disable the submit button after the form is submitted (even it is only for that "session"). I know that once the form is closed and reopened the button will work again and that is ok. If anyone has some suggestions I would appreciate it. Thanks.

hi,
modify the above script to:
this.access = "readOnly";
your submit button will be set to read only.
Regards--
Chalukya

How to disable the submit button

Hello ,
I have multiple controls on a page . I want to disable submit button until the user enters all the fields .
How to do this . appreciate your help in this .
rgds
kumar

Hi Kumar,
watch this post: disabling the submit button
Tobias
http://apex-at-work.blogspot.com

How to disable submit more than once?

Hi,
I have a form with a huge number of fields and validations on their validate event.
The form has a submit button with the following routine:
myDoc.submitForm(
cURL: URL,
cSubmitAs: "PDF"
My goal is that the user will be able to submit the form only once.
If I hide the submit button after this script there is a chance that one of the fields not pass the validation, the button disappear and user is not able to submit any more.
Otherwise nothing avoid from the user to submit the form multiple times.
Anyone has an idea?

here you can use
if()
else if()
else if()
else
write code that you want to execute in last.
Untill top conditions are not satisfied, code below that condition will not be executed. So no need to disable submit button because when user will click on submit button it will check all the condition from top.
Thanks

How to prevent multiple clicks of submit buttons in OAF Pages

Hi All,
Our page takes around 30 seconds to 1 minute for processing.
Some users are not patient enough. I have tried putting the below code in my PR method.
OAWebBean body = pageContext.getRootWebBean();
if (body instanceof OABodyBean)
((OABodyBean)body).setBlockOnEverySubmit(true);
This code disables submit button for some time. After few seconds, the submit button can be clicked again by the user.
Also, if I click on other browser window and come back to OAF page, the submit button can be clicked again immediately.
Have also searched OAF forum but didn't find any satisfactory answer.
Need answer from Oracle on this. If not answered on the forum, will raise an SR.

Hi Amit,
Try using the Processing Symbol , after clicking the Submit button. Which does shows you processing clock symbol once you click Submit Button.
Regards
Raghu

How can i disable a submit button and execute submit_action method on click

Good Day,
On my page I have a submit button that execute the submit_action method of the page backing bean that submit data captured on the page into a database and activate another class that send mail at the same time on a click of the submit button,the mail process takes a while before returning back to the page.I was able to disable the submit button to prevent the user from keep click while the process is running but the issue is on clicking the submit button it only disable the submit button without executing the submit_action method of the page backing bean.How can i disable the submit button and execute submit_method of the backing bean at the same time.
Thanks in advance.

I tried this out on one of my pages to see if it works.
First, I added the following JavaScript to my submit button's onClick event:
this.disabled=true; return true;When I clicked the submit button, it was disabled but the form was not submitted.
I deleted the JavaScript from the onClick event and added the following JavaScript to the form's onSubmit event:
var button = document.getElementById("form1:submitButton"); button.disabled=true; return true;When I click the submit button, it was disabled and the form was submitted but the button's action method was not called.
The next thing I tried was to change the onSubmit event code:
var button = document.getElementById("form1:submitButton"); setTimeout("button.disabled=true", 500); return true;This seemed to work. The difference was that I added a 1/2 second delay before disabling the button.
See if that works for you. If not then I'm fresh out of ideas.

Submit button in Compressor disabled after update Pro Applications Update 2010-02

Dear all,
I recently bought FCS and the whole software works fine after installation. However, I had to use Compressor over the last couple of days and the submit button was completely disabled and in the cluster field the option this computer had dissapeard. I checked this forum for a solution and found it. It seems that the problem was Qmaster. After reinstalling both Qmaster and Compressor everything works again. I have use the following set of instructions:
http://www.digitalrebellion.com/blog/posts/how_to_reinstall_compressor_and_qmast er.html
The problem is that now each time I do a software update, I am asked to install the Pro Applications Update 2010-02. After installing this update, the problem occurs again (the submit button is grayed/greyed out). It seems that in my computer the update creates a problem.
Does anyone have the same issue and if so, what suggestion you recommend?. At the moment I am avoiding the update, but I may me missing important bug and other fixes.
Thanks a lot,
Oliver

I have experimented a bit and got the problem sorted. Iuninstalled FCS using the uninstaller from http://www.digitalrebellion.com/fcsremover/.Before installing the whole suite again, I realised there was and additionalApple Qmaster package in the Applications folder. I deleted this file and emptythe trash. Then did a fresh installation of FCS, performed an update andinstalled Pro Applications Update 2010-02.
And now all is up and running workingperfectly.
Oliver

Need to disable the submit button record wise

Hello all,
I have two blocks. Block A and Block B. Block B is a summary block which records will be displayed.
Block A is a Control block and i have a submit button in it.
Based on some records in block B i need to disable the submit button .I would be record wise.
Please guide regarding the trigger use on this
Regards,
\Kiran

Kiran,
You can write the code in the WHEN-NEW-RECORD-INSTANCE trigger of the block B. it will fire when you navigate to that record.
Hope this helps.
Regards,
Manu.

Enable Submit Button at User Level and Disable at Block Level

I developed a query_find form having empno field:
Once the Employees‘s data is returned, then the new form that opens up should have the following fields.
Employee Name
Employee Number
Salary
Address
Notes
and submit button.
i have taken Employee Name,Employee Number,Salary,Address,submit button in xx_emp block.
and i have given Query Data Source as xx_EMP_v view.
and Notes related to xx_dum_emp block and for this query data source as xx_emp_details table(here notes field is contorl item)
And i have written the following code in the submit button
IF :xx_dum_emp.NOTES IS NOT NULL
THEN
INSERT INTO xx_emp_details
(employee_number,
employee_id,
employee_name,
address,
salary,
notes
VALUES (:xx_emp.employee_number,
:xx_emp.employee_id,
:xx_emp.employee_name,
:xx_emp.address,
:xx_emp.salary,
xx_dum_emp.notes
END IF;
commit;
I have taken all the fields in the same canvas.
Requirement:
Submit Button should be enable for the specific user.For other users it should be in disable mode.
so i have written code in POST_QUERY of the calling block as below:
IF l_name = 'TESTUSER'
THEN
SET_ITEM_PROPERTY ('XXMZ_EMP.SUBMIT',
enabled,
property_true
ELSE
SET_ITEM_PROPERTY ('XXMZ_EMP.SUBMIT',
enabled,
property_false
END IF;
It's working fine.
Suppose i query with empno 10 it will return Employees‘s data.So in that form i just enter some text in the Notes field
then click on submit.then close the form.again query with the same number then i need to disble Submit button at this level.
Is it possible to Disable the Submit Button?

Hi Dhana;
If your issue about Forms Customization please follow below and see its helpful:
Subject: Customization in Oracle Applications Doc ID: 743490.1
Subject: Forms Customization Doc ID: 69995.1
Subject: Setup & Usage (Customization) Doc ID: 104697.1
Please see "Oracle Developer Guide" available at:
Applications Releases 11i and 12
http://www.oracle.com/technology/documentation/applications.html
Also see:
http://oracle.anilpassi.com/forms-customization-steps-in-oracle-applications.html
http://oracle.anilpassi.com/a-new-custom-form-in-oracle-apps.html
I hope those are can be helpful for you
Regards
Helios

Disabling radio button/ submit button while ppr is in process

hi all,
In our project we have a PPR event on radio buttons ie user can only select one address as primary out of 10 (let say).
its working fine... but the problem is that the execution of ppr takes some time lets say 1-2 sec(fairly enough i suppose) and if user selects any other radio button or click on submit button page hangs up and an error (not the same error everytime) occured as the ppr has not been completed yet.
We want to know if there is any way to disable or grey out those buttons (radio/submit) while page is rendering (ie ppr is executing) to restrict user from clicking those buttons.
any help would be appreciated
thanks in advance
Shivdeep Singh

Hi,
Instead PPR on radio buttons, Use radiogroup for all the radio button and set intial value for one radio button to true.
You can get the selected radio button value in processFormRequest by using following
String radioGroupValue = pageContext.getParameter("RadioGroup");
Thanks,
Kumar

Disabled Submit Button

Similar Messages

Maybe you are looking for