Enumeration List and Unassigned Literal

Which avoids the fuzziness of the definition "required".

Hi Ralph,

I have a simple javascript condition that checks if another attribute is blank. If this attribute is set then I want my enumeration list attribute to be mandatory. Unfortunately mandatory means users can still select the value that we have assigned to be the "Unassigned literal" (None) in this case.

This method works fine for regular single select enumeration (single select) attributes.

Version is 5.0.2

So what checks for mandatory and what does that mean in case of an enumeration list? If it is the required for condition precondition that ships with RTC, I would assume that - if it works at all for list attributes - that it checks for a literal has to be available, The "Unassigned literal" is a literal.

You might consider this a bug, if so approach support with a PMR, On the other hand, as I mention, what "required" means for a list type attribute is something completely different from a not list type attribute. You can argue about what should or should not be available for selection and how the condition should work, there might be good reasons for multiple different approaches.

i.e. for an enumeration list, default is blank. For type enumeration default is the default literal.

I was using "required attributes for condition" only but I was advised that it is good practice to always have "Attribute Validation" as a precondition also