Configure Buttons with Conditional Requiredness
SAIL Recipes give you an opportunity to explore different interface design patterns. To learn how to directly use SAIL recipes within your interfaces, see Adapt a SAIL Recipe to Work with My Applications.
Present two buttons to the end user and only make certain fields required if the user clicks a particular button
This design pattern is not recommended for offline interfaces because reflecting immediate changes in an interface based on user interaction requires a connection to the server.
This scenario demonstrates:
- How to use validation groups to evaluate particular fields on a form
- How to use the requiredMessage parameter to set custom required messages
Test it out
- Click Onboard Employee without entering any comments. Notice that the custom required message that we configured using the
requiredMessage parameter shows up rather than the generic product message.
- Click Submit Future Onboarding without entering any comments.
Notable Implementation Details
validationGroup can have any string that you define. See also: Using Validation Groups
- For ease of implementation, these values are being saved into individual local variables. To use this form in a process, these local variables should be replaced with rule inputs.