Let's Reconnect, thank you for making 2022 our best year yet.

Look Back
Constraint Errors And Forced-Set Attributes — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Constraint Errors And Forced-Set Attributes

Received Response
edited Jan 30, 2016 3:09AM in Configure Price Quote 11 comments


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

Howdy, Stranger!

Log In

To view full details, sign in.


Don't have an account? Click here to get started!