When require_preferred_label_for_ca_objects = 1 is enabled in app.conf, the strict label validation logic works perfectly upon creating (inserting) a new object. However, the constraint is completely bypassed when editing (updating) an existing object.
If a user clears out the preferred label of an existing record and saves, the system does not throw a validation error. Instead, it falls back to the legacy behavior of converting the empty string into the literal text [BLANK] and saves the record successfully.
(I'm working with v2.0)
When
require_preferred_label_for_ca_objects = 1is enabled inapp.conf, the strict label validation logic works perfectly upon creating (inserting) a new object. However, the constraint is completely bypassed when editing (updating) an existing object.If a user clears out the preferred label of an existing record and saves, the system does not throw a validation error. Instead, it falls back to the legacy behavior of converting the empty string into the literal text
[BLANK]and saves the record successfully.(I'm working with v2.0)