ClassDefinition: allow database customization for display properties
Description
is caused by
relates to
Activity

Fabian Pichler 18 March 2018 at 06:28
there are multiple additional possible configurations on a class definition which do not relate to the storage or java handling. These are only related to how the values are presented in the editor. E.g. "size" on a static list influences only the size of the selection box. With Class-Collection it has been possible to change these settings "online" and for customers needs. Thus it IS a BUG that this feature is not working anymore with class definitions.
Marc Sladek 16 March 2018 at 16:49
Fields defined by a ClassDefinition do not allow customization, they will be reset eventually. This is not a bug but ensures reliability for the static definitions. To allow database specific changes would be an improvement instead, but reading out ClassField values has then to check the BaseClass as well, not only the static definition.
Adding additional fields is already possible, they won't be deleted upon restart.
Details
Priority
MediumAssignee
Marc SladekMarc SladekReporter
Edoardo BeutlerEdoardo BeutlerComponents
Details
Details
Priority
Assignee
Reporter

Components
Clockify
Start / Stop
Clockify
Start / Stop
Clockify

ClassDefinition does not allow overwrites on installation. On each save any change gets reverted to the configured ClassDefinition. The Save-Message of those reverts is "created/updated XClass".
Solution: Change
XClassCreator
behaviour the followingonly create the
BaseProperty
if it does not exist for display related properties of aPropertyClass
, e.g.size
orvalidationRegExp
also update the value for fixed properties of a
PropertyClass
, e.g.name
ormultiSelect
to achieve this extend the ClassFields by: