Blocking the row navigation in a table, tree and treeTable on error
Problem : Framework is letting the business user to navigate to different row in a table(tree or treeTable) even when the currently selected row has some validation error. As there are validation error binding layer does not respond to the row selection and the UI appears to be not synchronized with model in such cases.
Solution : The 11.1.1.7.0 release has introduced a anew flag "blockRowNavigationOnError" for af:table, af:tree anf af:treeTable.
Example:
<af:table blockRowNavigationOnError="always".../>
Copying the description of this flag from the tag documentation.
Property Valid Values
blockRowNavigationOnError always, never, auto
Whether we want to block row navigation in case of validation failure.
This is when you select a row and do some editing inside the table or in a related form, and this editing causes some validation failures. At this time, if you click on a different row in table, we want to block you from moving to the new row.
possible values are: always, never and auto. default value is auto.
Solution : The 11.1.1.7.0 release has introduced a anew flag "blockRowNavigationOnError" for af:table, af:tree anf af:treeTable.
Example:
<af:table blockRowNavigationOnError="always".../>
Copying the description of this flag from the tag documentation.
Property Valid Values
blockRowNavigationOnError always, never, auto
Whether we want to block row navigation in case of validation failure.
This is when you select a row and do some editing inside the table or in a related form, and this editing causes some validation failures. At this time, if you click on a different row in table, we want to block you from moving to the new row.
possible values are: always, never and auto. default value is auto.
- always means we block the row navigation
- never means we don't block and let the row navigation happen
- auto means the framework will make the decision
|
|
I struggled for hours trying to add a simple innodb table with a particular name without any foreign keys removing .idb files, I realised that my InnoDB data directory file must be corrupted by having a reference to the table even though it no longer existed so I stopped MySQL and removed. To get more info please visit help-essay.com/essay-examples.
ReplyDelete