Univention Bugzilla – Bug 47273
Improve usability of creating Extended Attributes
Last modified: 2022-03-15 16:59:28 CET
This is based on feedback from attendees of the UCS technical training. We made it quite easy to create Extended Attributes by adding the "CUSTOMIZE THIS PAGE" button in the UMC. The challenge is that a lot of attributes need to be filled in manually, allowing plain strings although simple typos will break the functionality. E.g.: * Language code: We could provide a preconfigured list/combobox of "en_US", "de_DE" and "fr_FR" * LDAP object class / LDAP attribute: We could provice a preconfigured list/combobox of "univentionFreeAttributes" and "univentionFreeAtribute1" to "univentionFreeAtribute20" * Syntax class: We could provide a preconfigured list/combobox of all supported syntax classes * Tab and Group names: We could provide a preconfigured list/combobox of all existing Tab/Group names and add an option to create a new one * Also, there should be a way to display an overview of the current ordering. Just entering an ordering number without any reference to the other entries is more some kind of gambling/guessing. All those preconfigured lists could be a LDAP object on their own. This way, they could be extended by the customer, if needed. Or when adding values that are not part of the preconfigured lists, one could use UDM instead of UMC.
This issue has been filed against UCS 4.3. UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.
(In reply to Michael Grandjean from comment #0) > This is based on feedback from attendees of the UCS technical training. > > We made it quite easy to create Extended Attributes by adding the "CUSTOMIZE > THIS PAGE" button in the UMC. The challenge is that a lot of attributes need > to be filled in manually, allowing plain strings although simple typos will > break the functionality. > > E.g.: > * Language code: We could provide a preconfigured list/combobox of "en_US", > "de_DE" and "fr_FR" Works now > * LDAP object class / LDAP attribute: We could provice a preconfigured > list/combobox of "univentionFreeAttributes" and "univentionFreeAtribute1" to > "univentionFreeAtribute20" All object classes and attributes are now accessible > * Syntax class: We could provide a preconfigured list/combobox of all > supported syntax classes Works now > * Tab and Group names: We could provide a preconfigured list/combobox of all > existing Tab/Group names and add an option to create a new one This is not done yet. > * Also, there should be a way to display an overview of the current > ordering. Just entering an ordering number without any reference to the > other entries is more some kind of gambling/guessing. This is not done yet. > All those preconfigured lists could be a LDAP object on their own. This way, > they could be extended by the customer, if needed. > Or when adding values that are not part of the preconfigured lists, one > could use UDM instead of UMC. Better not duplicate them.