Bug 29925 - Default values for UDM objects via default templates
Default values for UDM objects via default templates
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UDM (Generic)
UCS 4.1
Other Linux
: P3 enhancement (vote)
: ---
Assigned To: UMC maintainers
:
: 2206 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-01-04 15:17 CET by Alexander Kläser
Modified: 2019-01-03 07:24 CET (History)
4 users (show)

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Further conceptual development, Release Goal
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kläser univentionstaff 2013-01-04 15:17:36 CET
Currently the usage of default values for UDM objects is somewhat obfuscated. Default values are predefined by UDM modules, however, these are at best static values, otherwise some form of complicated logic needs to be implemented. Other default values can be specified via extended attributes.

An ideal way to deal with default values would be by having a default template per module (and where applicable). Then one single place with default values would exist (also for extended attributes as these should be shown in the templates, as well). These could be transparently modified by users and installed software packages.

With respect to bug 29635, it would then also be great to have for each ComboBox a mandatory empty value in case the attribute is not required.
Comment 1 Alexander Kläser univentionstaff 2013-01-10 12:16:16 CET
*** Bug 2206 has been marked as a duplicate of this bug. ***
Comment 2 Florian Best univentionstaff 2016-10-21 15:05:59 CEST
Sounds like a generic user template implementation.
Comment 3 Stefan Gohmann univentionstaff 2019-01-03 07:24:04 CET
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.