I have added some fields to the user interface (UI) and marked those fields as required. The UI that includes these fields has been merged with another UI. This combined UI is then linked to another UI that contains a "save" button. In the "save" button, I have set the validation parameter to true. However, after clicking the save button, the validation for the required fields is not being displayed.
Discussion posts and replies are publicly visible
What exactly do you mean when saying that some UI is "merged" and "linked"?
In general, a button with validate=true triggers all validations on all visible fields.
The save button and dropdown fields are located in separate UIs. During testing at the UI level, the validations are being displayed correctly. However, when the site is accessed, the validations are not appearing as expected.
How did you add this UI to that site? Are you aware that site pages of type interface do not support rule inputs?
I added this UI through an interface. However, the interface itself does not contain the rule inputs.
Did you make sure that the top-level interface used in the site has no rule inputs?
And, are you aware that a submit button only works in the context of a process start form or user input task? If you just add an interface to a site, a submit button will not do anything.
Yes, the top-level interface used in the site does not have any rule inputs. In the save button, we are currently utilizing the a!startProcess function based on the design. Are there any alternative solutions available for this?
First, a button with validate=true will trigger any validation on the form.
Second, the normal, Appian style way, is to define that interface as the process start form and then add that process model as page content.
okay thanks
Make submit = false and validate = true. It should work as per your requirement.