It is a functional requirement , suppose in application one fields is dependent on another field for its value or any property (required,disable,visible), it means when you select first field and put value in that then second field's value or other property is populated.
or second one is, you have multiple required attributes (cascading) in page and any of that's
AutoSubmit is set to true, in this case when user puts value in first field and goes to second to enter value but before this a large message window appears with required validation and all fields get red
This is very much annoying for user to face this kind of message each time, as i had a scenario where there was 15 required fields in af:form on popup and 10 of that are set to
AutoSubmit true .
to avoid this see steps
- Suppose i have page with create button for Departments table (default HR Schema) on pop up as a form and all fields are reuired
- When user clicks on create button and put value in field of DepartmentId, all required fields throw exception
- To avoid this i have set immediate true for first required field that is DepartmentName, it means when any validation occurs on popup , DepartmentName field will skip all validation on page and will shows only of its own
- Now when user put value in DepartmentId field, only DepartmentName field shows exception (required)
Happy coding......!!