Currently, when adding a property or editing an existing property, the category in which the property is to reside, is defined in a separate Custom Attribute. If a user manually adds this custom attribute, it is possible to type in an incorrect name, and create a whole new category.
This is a request to have a single master list of Categories, that can be selected on the property itself. "Category" could be a field on the property similar to Priority. This way the user sets the category based on a predefined list and doesn't have to enter the supporting fields that they need to enter in the Category custom attribute.
NOTE: This idea would actually be applicable to all of OpenPlant. So, the same across all schemas.
How frequently will feature be used? | Several times a day |
How much time will you save? | Hours if you figure in the administration time to add multiple classes for the variances in component display |
Your Industry | Other |
Other Industry | Infrastructure Software Company |