Behavior of readonly annotation changed (#632772)
The effect of the annotation readonly has been changed to achieve a consistent behavior in the Web Client and in CM/Track. In addition, it is now possible to make all kinds of fields editable in forms only.
The annotation readonly can have four values:
- all
The field is always read-only. - edit
The field is read-only when creating or editing a ticket, customer or resource. It can be edited in forms. - form
The field is read-only in forms. It can be edited when creating or editing a ticket, customer or resource. - unset
The field is always editable. This is the default behavior if the annotation is not assigned.
The behavior is identical in both the Web Client and CM/Track. It applies to regular fields and fields which belong to lists and structs.
When updating a ConSol CM system, the values of existing readonly annotations which had another value than false are changed as follows:
- Regular fields: The value is set to edit.
- Fields which belong to lists or structs: The value is set to all.
The behavior of existing installations changes if a regular field which is used in ACFs had the annotation readonly assigned.
Previously, the field could be edited in ACFs in the Web Client but was read-only in ACFs in CM/Track.
After the update, the field can be edited in ACFs in both the Web Client and CM/Track. It is not possible anymore to configure a field which can be edited only in ACFs in the Web Client.