Preventing the Duplicate Form Submission??

Hi,
How to prevent the duplicate form from been submitted without disabling the back button in IE???
Thanks,
JavaCrazyLover

I had the same wonder. I found the following articles are quite helpful. They give detailed background info, a design pattern to deal with it, and a Struts implementation.
http://www.theserverside.com/articles/content/RedirectAfterPost/article.html
http://www.theserverside.com/articles/content/RedirectAfterPost2/article.html
Cheers,
littlemonster

Similar Messages

Prevent duplicate form submission from same user

What's the best way to prevent the same person/computer from
submitting a form? I am wondering about cookies, ip address,
etc.

Rking1966 wrote
I am wondering about cookies...
You got me wondering, too. I thought of something like:
formPage.cfm
============
<cfif isDefined("cookie.isFormSubmitted") and
cookie.isFormSubmitted>
You have already submitted the form. You may only do so
once.<br>
<p>
<a href="someOtherBusinessPage.cfm">To
business</a>
</p>
<cfelse>
<form action="actionPage.cfm" method="post">
<input name="field1" type="Text">
<input name="send" type="Submit" value="Send">
</form>
</cfif>
actionPage.cfm
=============
<cfif NOT isDefined("cookie.isFormSubmitted")>
<cfcookie name="isFormSubmitted" expires="never"
value="true">
</cfif>

Prevent the Duplicate of Check No

Hi Experts ,
Could help me to prevent the Duplicating of Check No on Bill of Exchange screen [ F-36 ] .
with combination [ check NO and Bank Keys and Bank account number ,fiscal year ]
thanks a lot for your quick response

not required

Preventing duplicate form submission when page is loaded from history

Hi
We have record insertion forms some of which insert unique
records into sql databases and some which may not. Is there a way
of stopping the user pulling the page from history (or using the
back button) and then resubmitting the data?
I have put a trigger on the databases that basically updates
existing data rather than re-inserting it if a duplicate is entered
but as some of the record submissions are not unique this isn't
always possible. I would also rather restrict the submission client
side to reduce bandwidth and database calls.
I have tried various 'no caching' techniques on the page but
none seem to work. Anyone have any bright ideas ... I am all out of
ideas bright or not!!!
TIA
Karen

Karen
I have used session variables to control this sort of thing.
Basically the
insert/update statement tests for the existance of a variable
with a
particular name. If no variable exists then this will
indicate that the
request is coming from a history file, and it will not allow
the process.
Equally as part of the insert process change the value in the
variable and
do not allow and insert if the variable holds that value.
Paul Whitham
Certified Dreamweaver MX2004 Professional
Adobe Community Expert - Dreamweaver
Valleybiz Internet Design
www.valleybiz.net
"big_old_bird" <[email protected]> wrote in
message
news:e2totv$ec9$[email protected]..
> Hi
>
> We have record insertion forms some of which insert
unique records into
> sql
> databases and some which may not. Is there a way of
stopping the user
> pulling
> the page from history (or using the back button) and
then resubmitting the
> data?
>
> I have put a trigger on the databases that basically
updates existing data
> rather than re-inserting it if a duplicate is entered
but as some of the
> record
> submissions are not unique this isn't always possible. I
would also
> rather
> restrict the submission client side to reduce bandwidth
and database
> calls.
>
> I have tried various 'no caching' techniques on the page
but none seem to
> work. Anyone have any bright ideas ... I am all out of
ideas bright or
> not!!!
>
> TIA
> Karen
>

Preventing duplicate form submission

how do i prevent from the form being submitted twice in case user clicks the submit button twice?

Search at the net "struts tokens".

Duplicate form submission

We created a form for our website to receive inquirys. On a regular basis we receive a duplicate of the same email.
Can anyone help?

We do not prevent people from submitting multiple times. Can you confirm if those duplicate are because people have submitted more than once or maybe click on the submit button multiple times?
Gen

TS3276 On received mail, I delete sender's name, address, etc. then forward it. The forwarded mail has a duplicate of the original mail, show original sender's name, etc. How to prevent the duplicate from being sent?

How to prevent duplicate of orginal mail (with original sender's name, address) being "attached" when forwarded?

Maybe I am mis-understanding what you are seeing.
When I forward a message, the receiver will see the original mail (unless I edit it, such as removing any previous sender's information) and the length will be the same as the message was before forwarding except for the added line "Begin forwarded message" (again, unless I edit bits out), and there will be no attached copy of the original message.
So when you say in your reply above "The orginal email with the sender's name and address was also sent with my forwarded email." do you mean:
a) that it is still visible at the head of the text of the message (which I was saying does not happen for me because "after hitting delete, the previous sender's information disappears." [and since] "it has disappeared, it cannot be in your forwarded mail." Disappeared means it is not there.
b) another copy of the original message is attached to the forwarded email at the end, either as an included file or as repeated text.
c) some other situation.
Sorry about the previous mis-spellings! I hope that we can get to the bottom of this.

How to Prevent the Duplicate record insertion by JDBC Receiver?

HI Experts,
I have File Sender to JDBC Receiver scenario.I am using SAP PI 7.1 system.
Purpose of this Scenario is to read the data from specified file and INSERT or UPDATE the same records in Oracle Database.
Before inserting the data I want to check in the same table for prventing runtime error(Key fields Duplicatin).
So if records with the same key fields are available in table then I want to UPDATE the same record instead of INSERT.
Please Suggest me the poosbile way.
Thanks & Regards
Jagesh

Hi Jagdesh,
The JDBC receiver format has the following structure
<root>
<StatementName1>
<dbTableName action=u201DUPDATEu201D | u201CUPDATE_INSERTu201D>
<table>Table1</table>
<access>
<col1>val1</col1>
<col2>val2new</col2>
</access>
<key>
<col2>val2old</col2>
<col4>val4</col4>
</key>
This structure creates a query in this way :
UPDATE( OR UPDATE_INSERT) into Table1 set col1=val1 and col2 = val2new WHERE col2=val2old and col4=val4.
The key field works like a Where clause. So for the receiver format when you specify the key, it checks the DB with that field as the where criteria. Hence for a UPDATE_INSERT query, when you specify the key field, it checks whether that value specified within the key field exists in the DB or not. Then it proceeds to execute the statement for only those values.
Hence it makes sense to provide a primary key attribute in the key field of the JDBC receiver format.
Regards,
Kshitij

Does anyone "Trap" javascript errors and prevent the submission of a request?

I am wondering if anyone has implemented a way to capture when a JS error is triggered and prevent the submission of a request.
Websphere 6.1
Oracle 10g
Linux 4
RequestCenter 2008.3 sp7
I am wondering if anyone has implemented a way to capture when a JS error is triggered and prevent the submission of a request.
I have noticed that if someone selects a unique option (that was not considered or tested) that a JS error occurs and then they can submit the requsistion with out any validation.
This causes problem especially if a mandatory field was missed farther down the form.
Thank you
Daniel

Hi Daniel,
Interestingly, we've found that in Version 9.1, all errors are trapped and the form locks up (which is a change in behaviour) and we were planning on logging a defect for it! As, when service definitions change over time, it can very rather tricky to unpick absolutely everything without having an impact on the new service definitions (particularly when you have upgraded from 2007.x where ISF was the only way to do anything!).
Thanks,
Ant

How to prevent dupilcate form submission in JSF 1.x

Hi All
How to prevent dupilcate form submission in JSF 1.x application. As of now ,when the user clicked the submit button two times , application inserts 2 records in database.
Please suggest how to prevent dupliacte form submission without using Javascript. Kindlly share examples if any.
Regards,
DEV

Your problem is not really double submission but the fact that your application allows double insertion. The fix is functionally easy but technically very cumbersome: before inserting, check if the data already exists. If you build in such a guard you also protect against other methods of causing a resubmission, such as the browser back button.
PS: what's the deal with the no javascript limitation? You do realize that when you use JSF you're tanking your application full of javascript, right?

How do you prevent form submission if Spry validation fails?

After reviewing and implementing the SpryValidationConfirm and SpryValidationPassword widgets on a test page, I am unable to prevent the form from being submitted if the validation of either widget fails.
A feature of both widgets is "Blocking form submission if the password criteria is not met".
I ihave included my code below:
<script src="SpryAssets/SpryValidationPassword.js" type="text/javascript"></script>
<link href="SpryAssets/SpryValidationPassword.css" rel="stylesheet" type="text/css" />
<script src="SpryAssets/SpryValidationConfirm.js" type="text/javascript"></script>
<link href="SpryAssets/SpryValidationConfirm.css" rel="stylesheet" type="text/css">
<cfform method="post" action="result.cfm">
<span id="sprypassword1">
    <label>Password
      <cfinput type="password" name="mypassword1" id="mypassword1" size="30" />
    </label>
    <span class="passwordRequiredMsg">The password cannot be empty</span>
    <span class="passwordMinCharsMsg">The password must contain at least 15 characters</span>
    <span class="passwordInvalidStrengthMsg">The password must contain 2 special characters, 2 uppercase characters, 2 lowercase characters, and 2 numbers</span>
</span>
<span id="spryconfirm1">
    <label>Confirm Password
      <cfinput type="password" name="mypassword2" id="mypassword2" size="30" >
    </label>
    <span class="confirmRequiredMsg">A value is required</span>
    <span class="confirmInvalidMsg">The values don't match</span>
</span>
<cfinput type="submit" name="submit" value="Go to the next page">
</cfform>
<script type="text/javascript">

</script>

Thanks so much!
I removed the <cf prefixes from the cfform and cfinput tags and form now does not submit on invalid data.
I did not rename the 'password' fields as I think there needs to be 2 inputs that can be compared for the confirmation widget to function.
I have attatched the working code below:
<script src="SpryAssets/SpryValidationPassword.js" type="text/javascript"></script>
<link href="SpryAssets/SpryValidationPassword.css" rel="stylesheet" type="text/css" />
<script src="SpryAssets/SpryValidationConfirm.js" type="text/javascript"></script>
<link href="SpryAssets/SpryValidationConfirm.css" rel="stylesheet" type="text/css">
<form method="post" action="result.cfm">
<span id="sprypassword1">
    <label>Password
      <input type="password" name="mypassword1" id="mypassword1" size="30" />
    </label>
    <span class="passwordRequiredMsg">The password cannot be empty</span>
    <span class="passwordMinCharsMsg">The password must contain at least 15 characters</span>
    <span class="passwordInvalidStrengthMsg">The password must contain 2 special characters, 2 uppercase characters, 2 lowercase characters, and 2 numbers</span>
</span>
<span id="spryconfirm1">
    <label>Confirm Password
      <input type="password" name="mypassword2" id="mypassword2" size="30" >
    </label>
    <span class="confirmRequiredMsg">A value is required</span>
    <span class="confirmInvalidMsg">The values don't match</span>
</span>
<input type="submit" name="submit" value="Go to the next page">
</form>
<script type="text/javascript">

</script>
Again thanks so much!

Prevent multiple users from editing/approving the same form SPD 2013,SP 2013

Hello all, I have a workflow with a to do task, the task is assigned to a group so any of the users in that group can go in and do a quality check on form data and approve it. How do I prevent multiple users from working on the
same form? do I just require check out? or is there a way to notify the rest of the group that a user has already started the quality check.

The "Require Checkout" option is your best bet. You can also enable the auto checkout on edit option to allow minimal effort on the side of the user. Other users will then get the error message stating the item is checked out, if they try to
edit it.
If you'd like, you could add a workflow to the task list that triggers when something is changed. That workflow can check if the item is checked out and if so, email the other users assigned to the task.
I trust that answers your question...
Thanks
C
|
RSS |
http://crayveon.com/blog |
SharePoint Scripts | Twitter |
Google+ | LinkedIn |
Facebook | Quix Utilities for SharePoint

How do you duplicate a PDF fill in form page, WITHOUT linking the text (for MAC)??? That is, while still being able to type different things into the blanks on the duplicate pages?

The Situation (again, I have a Mac): I am filling out a 5 job application- it is PDF format, with questions, and fill in the blanks for your information- such as name, date, and employment history. Page 3, is the page used for employment history. But, there is only room for two jobs on page 3. The instructions tell you, you can "have as many page three's" as you want. In my case, I will be putting 8 jobs- at two jobs per page, that is a total of 4 page three's. I already know how to duplicate a PDF page, simply by opening the thumbnail viewer on the side, holding down the "alt" key, and clicking and dragging the desired page to create a duplicate. So what is the problem??? When you duplicate the page, the boxes into which you type, are linked. So if on the original, you type "Job A", into the experience box, it forces the same answer on the duplicate page, making it impossible to describe different positions!!!! Is there a way to work around that? Thank you!!!!!

You're probably using Acrobat if you can duplicate pages like that. This is the Adobe Reader forum...
To answer your question, though: The only way this can be done automatically, without having to manually rename each field, is to use a Template to spawn new pages. This is something the form's author should have done, but you can do it yourself as well, using some code.

Prevent double running the same FORM application

Dears,
Anyone knows how to prevent users from running same FORM application in the same computer twice? Is there any ways to detect the application is already running and refuse to run it again?
Thanks,
Vic

i have a tree-menue where i use code like this in the when-tree-node-activated trigger which opens new forms:
frmId := find_form(frmToOpenName);
-- Open form only if there's no instance (for current user) of it at the moment
if id_null(frmId) then
open_form(.....);
else
go_form(frmId);
end if;
of course, if the user opens another tree-menue, he can open the same form again. but in one browser (i use 9i), he can open it only once.

Prevent multiple users accessing the same form

hi,
i am working in forms
i have a requirement like this
if more than one user are using the same form and try to access the same record then the second user should not be able to do transaction
he should be popped up with a msg saying that other user is working on it
can any one suggest how to do this in my form
thanks in advance
selvaraj s

That is pretty much exactly the way Forms works automatically.
Two users can use the same form, and can even display the same data record. One of the users can make changes to the record -- Forms locks the row upon the FIRST keystroke in the first field the user begins to change.
Once the row is locked, the second user is free to look at the record, and won't even know if another user has begun making changes. However, if second user tries to change even one field in the record, Forms pops up the message, "Could not reserve record (2 tries). Keep trying? Yes / No"
There are also protections so if the first user actually changes the row and commits, then the second user tries to make a change. Forms will automatically detect whether changes were made, and if so, will undo the change and issue the message, "FRM-40654: Record has been updated by another user. Re-query to see change."
The above automatic processing works very nicely. If it will not work for you, then what is it you need?

Preventing the Duplicate Form Submission??

Similar Messages

Maybe you are looking for