Option to Make Classifications Required

[johnny.buccola]

Not much else to say here. Currently, you can create and save an item without slecting a classification (talking about the newer web-based one here).  A simple check box - like with all the other fields - making class selection (within, say, a certain root node) required, would be helpful in enforcing the classification of an item before it is created.  Most of my workspace's item details are class-specific, so a lazy user may not have much to fill out until they select a class.

[gasevsm]

Greetings, 

Not sure I follow your request exactly, kindly let me know if this is not answering it. Presently, you can define in PLM a default root class such that all items that get created will auto-classify with your root class. Also, in the classification manager, you can do one or both of these:

1. you can define the root class a phantom class. This would force the user to classify an item before saving the item.

2. you can configure a required validation for a class eg. a root class or the sub-classes. this would enforce the user to fill in required value for the [auto-]selected class before the item can be saved and created.

Does this help?

[johnny.buccola]

Nope, this will work just fine! Thanks for the help!

[benderk]

Thank you for submitting your idea. Have you tried the Modern Interface lately? We request that you review your idea in the context of the Modern interface. If your idea is not addressed, we invite you to create a new Idea in the context of Modern so that it can be addressed accordingly. Sincerely, Keri Bender | Global GTM Business Strategy Manager, Product Lifecycle Management