Enumeration - Default Literal
With RTC 3.0x and higher, it has become a mandatory requirement to assign a default literal value.
is there a way around this ? It negates the ability to set an enumeration as mandatory on a specific state or state change as the "default" is already set and therefore populated. Did I miss something ? |
Accepted answer
Jared Burns (4.5k●2●9)
| answered Mar 14 '12, 12:01 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER With RTC 3.0x and higher, it has become a mandatory requirement to assign a default literal value. If you want the user to have to choose some value other than what is initially selected in the editor, you should set the Unassigned Literal to be the same as your Default Value. This value will then be selected by default, but the attribute will still be considered unset. Hope that helps, - Jared Jared Burns selected this answer as the correct answer
Comments Jburns,
With RTC 3.0x and higher, it has become a mandatory requirement to assign a default literal value. If you want the user to have to choose some value other than what is initially selected in the editor, you should set the Unassigned Literal to be the same as your Default Value. This value will then be selected by default, but the attribute will still be considered unset. Hope that helps, - Jared I just got pinged about this question and saw this response for the first time. The final part of the puzzle is that you need to configure a precondition on Work Item Save that requires the attribute to be set.
That precondition won't consider the attribute to be "set" if it matches your selection for the Unassigned Literal.
I was the "pinger" and the combination of Default Literal = Unassigned, plus the "Required Attributes" precondition got me exactly what I want - a non-meaningful default that comes up when the workitem is created that the submitter then needs to change before saving.
I hadn't put 2+2 together on what "Unassigned Literal" meant but that's exactly what it is - a value that effectively plays like "empty" or unassigned while still having a textual display you can customize.
I like!
|
2 other answers
Karen - I actually found a way around this. You cannot save it from the GUI side, but you can go into the Process Configuration Source and change it there.
Do a search for your enumeration in the source, the one with all the values. There will be one listed with default="true". Just change the True to False and it comes up blank, and gives the user an error if they don't change anything. |
Great question Karen. I was just looking into this myself, as the client does not want Unassigned to be a valid value. But, if we cannot change the default literal to none, most users will just keep the Unassigned value (or whatever the default one is). Hopefully someone can answer this for us.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.