I have a Sail form with a confirmation message set on the submit button and mult

I have a Sail form with a confirmation message set on the submit button and multiple required fields, including some set within an applyComponents function. My issue is that if a required field is not completed but the user clicks on the submit button the confirmation message is displayed before the fields are shown in error.
I have added an indicator for one of the fields and added this as a condition to the confirmation message and this works for that one field. Is there any way to check if any required fields are missing without having to put indicators on every required field? What would be the best way to do this?

OriginalPostID-149851

OriginalPostID-149851

  Discussion posts and replies are publicly visible

Parents
  • @smcgill Hi, Documentation at https://forum.appian.com/suite/help/7.9/SAIL_Components.html#SubmitButton or https://forum.appian.com/suite/help/7.9/SAIL_Components.html#Button under 'Notes' say that "The SAIL interface only refreshes and the saveInto state change only occurs if the user clicks Yes".

    As far as my understanding is considered, the approaches discussed above also lead you to make usage of the indicators which you are already doing.

    AFAIK there isn't a possibility of detecting the outstanding errors by making use of OOTB functionality. I guess there is no other alternative apart from the one you have chosen. The only thing which we could give a thought about at the moment is, how best (generic in terms of development, less dependency on the other components and effective in terms of execution) we can implement the alternative approach.
Reply
  • @smcgill Hi, Documentation at https://forum.appian.com/suite/help/7.9/SAIL_Components.html#SubmitButton or https://forum.appian.com/suite/help/7.9/SAIL_Components.html#Button under 'Notes' say that "The SAIL interface only refreshes and the saveInto state change only occurs if the user clicks Yes".

    As far as my understanding is considered, the approaches discussed above also lead you to make usage of the indicators which you are already doing.

    AFAIK there isn't a possibility of detecting the outstanding errors by making use of OOTB functionality. I guess there is no other alternative apart from the one you have chosen. The only thing which we could give a thought about at the moment is, how best (generic in terms of development, less dependency on the other components and effective in terms of execution) we can implement the alternative approach.
Children
No Data