Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
1 reply
Subscribers
8 subscribers
Views
988 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
User Interface
Certain fields are defined as *required in my portal forms. However there are sc
padmanabhanv
over 11 years ago
Certain fields are defined as *required in my portal forms. However there are scenarios where a user can just cancel and go back to the previous form; the system does not allow the user to cancel(using a Submit button) citing that the mandatory fields are not populated. What is the best approach to let the system know the difference between a cancel and a submit action?...
OriginalPostID-98878
OriginalPostID-98878
Discussion posts and replies are publicly visible
0
hemalathat
A Score Level 1
over 11 years ago
Irrespective of what the purpose of a button is, Appian always runs the mandatory check for any field which is defined a a required field. You can address this use case in the following ways -
1) Don't make any of the fields required at the form level, instead do the check after the form is submitted (may be in the form output or a script task). Redirect to the same task if the validation fails. Make sure you have activity chained these steps.
2) If you are on 7.4, you can try using SAIL forms which offer this functionality.
3) Last option is to use JavaScript. But using JS is not recommended as forms with JS are not supported on Tempo/mobile.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel