I have a requirement where i need to disable buttons once the user submit the form. I tried using buttonaction rule input but its not working . Any suggestions?
Discussion posts and replies are publicly visible
Submitting a form leaves the form, as Stefan has been trying to explain. Thus, under any normal configuration, "disable buttons once the user submits" just does not make sense.
Can you tell us exactly how you have this form configured / where you're using it, and exactly what the user is experiencing?
NOTE: You've tried this in a process, and not just in the interface designer, I hope?
Yes, its being used in the process where it's setting the button action value.
Where in the process is it being used? How/where is the process accessed by users? What happens in that process after this form has been submitted? A screenshot of the snippet of the process where the form in question is being used might also help.
Is it possible there is a validation being triggered that you don't realize is happening? One tricky thing I've seen before is if you have a validation message that returns a space only like " " then it still triggers the validation and won't submit the form (even though it doesn't show a message).
Peter Lewis said:Is it possible there is a validation being triggered that you don't realize is happening?
This doesn't sound like it relates to what the original poster is describing here... she never mentioned a form that refuses to submit, as far as I can tell.
In this interface, once the user submits the form, they can review the form after submitting and gets the option of editing. The requirement is to disable the submit button after submission which can be enabled when there is a new form or some editing is done on it. whenever the user reviews the submitted form, it should be disabled
Tan18 said:once the user submits the form, they can review the form after submitting and gets the option of editing
Can you describe what process model setup you're using to try to accomplish this? Can you clarify whether you mean the user gets a *second* task for reviewing the values entered on the original form?
The user is not getting any second task for reviewing. It's displayed in the form grid where they can see the status as well as an edit if want to correct anything. In the scenario, when they go back to check the status, there they again see submit button active.
this is a pretty painful process, but it doesn't really answer Mikes question. -> "Can you clarify whether you mean the user gets a *second* task for reviewing the values entered on the original form?"
thanks for the screenshot - can you add some context and/or clues as to what task node(s) in question are relevant to your original question? I can see at least that we're not dealing with a Start Form, which is useful info.
Richard Michaelis said:this is a pretty painful process
no kidding...