Welcome to the Jazz Community Forum
Can't add enumeration values w/o specifying default literal
We have recently updated from 2.0.1 to 3.0.1 - since then, I am unable to add values to enumerations because RTC is requiring a default literal on every enumeration in our configuration. I don't want to specify defaults - is there a way to modify our template or rules to allow enumerations without default literals?
Accepted answer
The problem with this workaround is that we cannot then set the attribute, using the enumeration, to mandatory, because it will always have a value, in this case "No Value"!
Hi,
You can make the attribute mandatory, just select the unassigned literal option as well: e.g
default literal: 'No Value'
unassigned literal: 'No Value'
This way even though 'No Value' is the default value of the attribute, it is also unassigned.
3 other answers
The problem with this workaround is that we cannot then set the attribute, using the enumeration, to mandatory, because it will always have a value, in this case "No Value"!
Hi,
You can make the attribute mandatory, just select the unassigned literal option as well: e.g
default literal: 'No Value'
unassigned literal: 'No Value'
This way even though 'No Value' is the default value of the attribute, it is also unassigned.
I followed this recommendation and I coincidentally am now seeing lag time (10 to 20 seconds), not only for the dropdowns (enums) where I have made this (unassigned literal; not null) change, but I'm also seeing delays in render time for lists like the Filed Against (work item categories).
I rebooted our app server just now. The situation continues.
Has anyone else experienced this on 3.0.1.2?
Any advice into whether this config change may have led to this outcome is greatly appreciated. (no other changes were made to our CCM space today)