Constraint Errors And Forced-Set Attributes

Content

Behavior has changed on constraint errors. Now when a constraint is hit, regardless of the attribute type, the field becomes user editable. This is really stupid when the system is trying to push a value into a forced-set field! Also, if the constraint rule is not set up correctly the error message does not show up - the only indication anything is wrong is the "forced-set" field has become a "set" field. This behavior is not very user intuitive as it either: A) gives the user the impression he/she can change the value (which will only be overwritten by the