We use Change Orders to manage the changes to our Items. We "Restrict Item Lifecycle State Changes to Change Orders", so that Released items cannot be WIP'd without being in a Change Order, which for the most part works really well.
However, we want to implement an Item "Quick Change" State in which our Engineering Management can use to allow minor changes to an Item/drawing. This would circumvent the Change Order process, not bumping the revision, and allowing these minor type changes to occur. When the engineer has completed the required changes, the manager then puts it back into Released. This completely circumvents the Change Order process, which is what we want.
To recap:
- Engineering Management Group is allowed to change the state of an item from Released to Quick Change and Quick Change to Released
- All other changes and state changes MUST go through the change order process
- I do not want to make the Engineering Managers Administrators in Vault.
What I've tried:
- I've added "Quick-Change" to the Item Release Process Lifecycle Definition.
- I added the Engineering Management Group, with Permissions = Allow, to the Released-to-QuickChange and QuickChange-to-Released Transitions.
- I added the "Project Management" role to the Engineering Management Group.
The Engineering Management Group can now change the state of the released item to any state (WIP, In Review, etc). If I try restricting access (Transitions) then it prevents state changes within the Change Order.
