Define legacy values in legal value list and/or enumeration attribute constraints

[AndersKullenber]

When assigning a legal value list or enumeration constraint on a attribute, those values are applied when creating and editing that attribute. But it also applies when searching for objects

based on that attribute. If one of the values becomes invalid for new objects or new iterations of existing objects, the value can be removed from the list.

This however means that it is not possible to use in search any more.

If a value could be defined as a legacy value, similar to legacy values in filebased revision serie, it could be allowed in the search but not in create or edit.

An alternative solution would be to disable the constraint in search all together.

BR

Anders

I found this relatively old article on the subject but I have not found any product idea

https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS175784

[olivierlp]

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.