A separate field / attribute for the Change Notice TEMPLATE NAME is needed.

[dritter-3]

Please create a separate field / attribute for the Change Notice TEMPLATE NAME.

At the moment the Change Notice name itself (attribute "name") is also used as change notice "template name".

Because of that a new change notice template cannot be created with an empty or prefilled/pre-defined name/explanation...

To have a separate field for the template name would help here, so that the change notice name attribute can be used different to the template name.

[BjoernRueegg]

Yes! Also it would be very helpful if the required attributes can be left empty, so the user is required to select the right value. This is at the moment very painful, since the constraint needs to be deleted in the Type and Attribute Manager. After creating the templates, the constraint needs to be set again.

[dritter-3]

Hello Brueegg, thank you for your Kudo.

FYI: To set required attributes empty for change templates you can export the template, adapt the XML, delete the old template in the system, and import the adapted template again. With this workaround, you do not have to temporarily delete the constraint in the Type and Attribute Manager (-> risky, because the users can create a new change object with empty attributes during this time).