What To Do When ADF Editable Table Misbehaves

You know sometimes its a challenge to get correct behavior for ADF editable table - meaning, to have it as much as possible aligned with smooth user experiences. One of the challenges to control when validation rules are fired - often validation is fired too early or too often (same validation error messages are repeated multiple times). In some cases this can be resolved by setting Change Event Policy = None on iterator (default is Auto PPR), but still this doesn't cover all scenarios. There is special case when ADF editable table is set to support multi-selection. With multi-selection enabled, even setting Change Event Policy to None doesn't help - validation is still fired too early. But there is solution - set Immediate property to True for ADF editable table component - this will allow to skip annoying validation messages when editing data. Validation failure messages will show up on transaction commit - invalid fields will be highlighted in red.

Download test case application, where Immediate property is set to True - AutoPPRApp.zip.

Sample application is tested firstly with default settings for ADF editable table component and multi-selection feature enabled. User creates new row:

As soon as new row is inserted, all values are blank and user needs to type something. User moves mouse cursos to any of the fields from new row - immediately validation fires without reason for empty required fields (this is way too early - user was about to type something, ADF throws validation error in advance):

Switch validation control for editable ADF table by setting Immediate = True:

New row creation behavior is different now - blank row is inserted, and user can start typing data without getting annoying validation error failure message:

Validation is invoked later, when transaction is about to be completed - validation failures are highlighted for each of the attributes: