How can we stop this dialogue box when we click on save option?

What is your "save option" and what is it doing?

 a!buttonLayout(
              primaryButtons: {
                a!buttonWidget(
                  label: cons!ISR_TEXT_BUTTON_SAVE,
                  value: cons!ISR_TEXT_BUTTON_SAVE,
                  saveInto: {
                    a!save(local!visibility, true()),
                    a!startProcess(
                      processModel: cons!ISR_WRITE_TO_DB_FINAL_APPROVAL_PM,
                      processParameters: {
                        gsr_j_meeting_amd: local!gsrAmdMD,
                        gsr_j_meeting_study: local!gsrMD,
                        isr_j_meeting_study: local!isrMD,
                        isr_j_meeting_amendment: local!isrAmdMD,
                       
                      }
                    ),
                    a!save(ri!buttonAction, save!value),
                    a!save(ri!isrMdApproval, local!isrMD, ),
                    a!save(ri!gsrMdApproval, local!gsrMD, ),
                    a!save(ri!isrMdAmdApproval, local!isrAmdMD, ),
                    a!save(ri!gsrMdAmdApproval, local!gsrAmdMD, ),
                   
                  },
                  submit: false(),
                  style: "NORMAL",
                  validate: false(),
                 
                ),
                a!buttonWidget(
                  label: "Save AND END TASK",
                  value: cons!ISR_TEXT_BUTTON_SAVE_END_TASK,
                  saveInto: {
                    a!save(local!visibility, false()),
                    a!save(ri!buttonAction, save!value),
                    a!save(ri!isrMdApproval, local!isrMD, ),
                    a!save(ri!gsrMdApproval, local!gsrMD, ),
                    a!save(ri!isrMdAmdApproval, local!isrAmdMD, ),
                    a!save(ri!gsrMdAmdApproval, local!gsrAmdMD, ),
                   
                  },
                  submit: true(),
                  style: "PRIMARY",
                  validate: true,
                  validationGroup: cons!ISR_TEXT_BUTTON_SAVE_END_TASK,
                  confirmHeader: "Submit?",
                  confirmMessage: "Are you sure you want to Submit, decision taken cannot be changed later."
                )
              }
            ),

I am just saving the comments for later without submitting. Actually, we have two buttons one is "save" and other is "save and end task", save and end task denotes submission of the task. 

Please find the code configuration for that buttons

I am confused. A non-submit button does not trigger that browser message.

I am really missing the context here. Can you feed my remote healing powers with more details?

yeah sure .Could you please let me know  when this browser message will trigger in appian

When there is modified data in an input field and you try to navigate away.

cant we control that dialogue box?

Unknown said:

I am really missing the context here.

1. The users enter data.

2. The user clicks on this bespoke non-submitting "Save" button which performs its save via StartProcess call.

3. The user tries to navigate away, having "saved" already, and the Appian pop-up about losing unsaved data appears (but is now unwanted).

This seems like a reasonable question.  I'm not sure the use case is quite common enough to require something custom from Appian to handle.  I would merely suggest to the OP that they consider implementing a "non-submitting save" in the traditional manner, meaning it's actually submitting (but perhaps not validating or at least validating less), chaining immediately back to the form after information is persisted into the process instance and/or database.

What do you mean? No, you can't! There is unsaved data in the form. And Appian does not know that you somehow persisted it in the background.

But, to get rid of this, why not just hide the input fields and show a success message to the user. Then he/she can easily navigate away. This would also make this a less awkward user experience.

Unknown said:

just hide the input fields and show a success message

good point, this is probably the one other reasonable workaround here.  IMHO it still might be a stronger approach to design the "save" pattern in the usual manner, i.e. submitting of the task and looping-back.

Unknown said:

just hide the input fields and show a success message

good point, this is probably the one other reasonable workaround here.  IMHO it still might be a stronger approach to design the "save" pattern in the usual manner, i.e. submitting of the task and looping-back.

 I am sorry,Could you please explain little mor on this

sireesha said:

please explain little mor on this

Which part?  There were a few different things there.

What do you mean? No, you can't! There is unsaved data in the form. And Appian does not know that you somehow persisted it in the background.

But, to get rid of this, why not just hide the input fields and show a success message to the user. Then he/she can easily navigate away. This would also make this a less awkward user experience.

This part

sireesha said:

But, to get rid of this, why not just hide the input fields and show a success message to the user.

After the user presses your "save" button, and after the "save process" is completed successfully, hide the editable portions of the interface.  When there are no editable fields with (what Appian thinks of as) "unsaved" data being displayed, the "unsaved data" warning dialog you're talking about here will not be displayed when the user attempts to navigate away.