Idea Summary
Currently the validation on a column is fired even when the data is changed in any column for that specific row with the Execution Scope defined as “For Created and Modified Rows”. Validations should not be fired unless there is a change in column value.
Use Case
Though the column value is not changed, validations specified on this column are fired when other columns' values are updated indicating that particular row is modified.
Validation with Execution Scope of “For Created and Modified Rows” is considerable when a column(say Commission) is dependent on other column(say Salary) to check the commission cannot be greater than 10% of salary. But the validations on employee columns say Firstname or Lastname need not be fired unless there are modifications for those specific fields.
This is just a simple case. But in the use case of Interactive Grid having 100 columns with 20-25 validations on different columns, executing all these validations on all columns even though few of the column values are changed will have a significant performance issues.
Preferred Solution (Optional)
Please include another Execution Scope say “When column value changed” in the Server-side Condition section for validations.