Both upstream view (Design) and its downstream view (Manufacturing) version of part using same LC template. In order to create EBOM and MBOM, both designers and manufacturing roles supposed to be configured with same set of access control in Inwork state and some other states.
Designer should be configured with create and modify permissions in Inwork and revise permission in Released state to work on EBOM.
Manufacturing role should be configured with create and modify permissions in Inwork and revise permission in Released state to work on MBOM.
I am looking ways to prevent Designers modifying MBOM and also to prevent manufacturing roles modifying EBOM or even deny creation of Design version of part.
I don't know if this might help you:
This approach is promising. Need to test this out.
There is a prerequisites to create product context using MPMLink template.
Our users will be creating manufacturing view versions for existing parts in existing products and libraries. We need to find how much effort to convert all of existing contexts so that those looks like MPMLink template driven contexts.
What we did.
(1) Created a dedicated product context to store all downstream view version of parts. To achieve this we have configured ACL (only Revise, Create) on that single context and rest of the existing products configured with only New View Version access.
(2) One drawback in this process, manufacturing users are forced to use MAPSE because that is the only UI where users have flexibility of choosing Downstream part context. Even if users try to create downstream view version parts using some other means, the system going to throw an error because users don't have option force new view version into separate context.
We are planning for long term solution of modifying or writing validators on Revise and Modify and that has work based on View value.