Disable Save and Submit button

RE: Disable Save and Submit button

Mike Schmitt — Thu, 21 Jul 2022 15:59:32 GMT

[quote userid="85715" url="~/discussions/f/user-interface/25247/disable-save-and-submit-button/98174#98174"]this is a pretty painful process[/quote]

no kidding...

RE: Disable Save and Submit button

Mike Schmitt — Thu, 21 Jul 2022 15:54:09 GMT

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.

RE: Disable Save and Submit button

Richard Michaelis — Thu, 21 Jul 2022 15:54:03 GMT

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?"

RE: Disable Save and Submit button

Tan18 — Thu, 21 Jul 2022 15:45:01 GMT

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.

RE: Disable Save and Submit button

Mike Schmitt — Thu, 21 Jul 2022 15:09:29 GMT

[quote userid="88894" url="~/discussions/f/user-interface/25247/disable-save-and-submit-button/98168#98168"]once the user submits the form, they can review the form after submitting and gets the option of editing[/quote]

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?

RE: Disable Save and Submit button

Tan18 — Thu, 21 Jul 2022 15:06:45 GMT

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

RE: Disable Save and Submit button

Mike Schmitt — Tue, 19 Jul 2022 17:36:32 GMT

[quote userid="2478" url="~/discussions/f/user-interface/25247/disable-save-and-submit-button/98038#98038"]Is it possible there is a validation being triggered that you don't realize is happening? [/quote]

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.

RE: Disable Save and Submit button

Peter Lewis — Tue, 19 Jul 2022 17:18:26 GMT

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).

RE: Disable Save and Submit button

Mike Schmitt — Tue, 19 Jul 2022 16:39:49 GMT

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.

RE: Disable Save and Submit button

Tan18 — Tue, 19 Jul 2022 16:29:24 GMT

Yes, its being used in the process where it's setting the button action value.

RE: Disable Save and Submit button

Mike Schmitt — Tue, 19 Jul 2022 15:10:05 GMT

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?

RE: Disable Save and Submit button

Stefan Helzle — Tue, 19 Jul 2022 14:11:00 GMT

How is that done? A loop in the process model?

RE: Disable Save and Submit button

Tan18 — Tue, 19 Jul 2022 14:09:55 GMT

yes its giving user ability to submit again even after submitting

RE: Disable Save and Submit button

Stefan Helzle — Tue, 19 Jul 2022 14:06:10 GMT

OK. To make it more clear. The interfaces I build do close on submit. Yours seem to not do that. There must be a difference which I do not understand.

RE: Disable Save and Submit button

Tan18 — Tue, 19 Jul 2022 14:03:09 GMT

if(
              ri!canSubmit,
              a!buttonWidgetSubmit(
                label: "Submit",
                style: "PRIMARY",
                value: cons!L_BUTTON_VAL_SUBMIT,
                saveInto: ri!buttonAction,
                disabled: if(
                  isnull(
                    ri!noData
                  ), 
                   rule!SS_ER_isEmpty(
                    ri!Items,
                    ri!Value,
                    
                  ),
                  false
                  
                ),
                skipValidation: if(
                  isnull(
                    ri!noData
                  ),
                  false,
                  true
                )
              ),
              {}
            ),

RE: Disable Save and Submit button

Stefan Helzle — Tue, 19 Jul 2022 13:53:43 GMT

As I tried to explain, I do not understand your implementation. Do you have a few more details? Screenshot, code snippets?

RE: Disable Save and Submit button

Tan18 — Tue, 19 Jul 2022 13:51:18 GMT

Even after submitting the form, the submit buttons are enabled. It's getting disabled when there is no data but when the user edits any field it gets enabled again. But now the requirement is once it's submitted, it shouldn't provide users the ability to submit again.I tried with button action value with if condition but didn't worked

RE: Disable Save and Submit button

Stefan Helzle — Tue, 19 Jul 2022 13:43:58 GMT

Can you give us more details about your use case?

I general a form is closed after submit. There is the exception of a process model using a start form as a page in a site. Then the user will just see the empty form again.