Which takes precedence in setting up operational attributes Item Status or User definition?
There are few operational attributes controlled at Item Status Level, Template Attributes and some are manually passed whole creating the item in UI or FBDI.
Understanding is that Item Status takes the highest precedence followed by FBDI/Manual change and Template.
We notice that FBDI/Manual change takes precedence over the Item Status, which doesn't seem to be correct. For example, We do not want the users to create items in Inactive Status but have Purchased attribute set to yes.
Please suggest if this is a bug or intended behavior?