Skip to main content
J
JohnWenner6-Contributor
6-Contributor
April 18, 2023
Solved

Dual contractors in same Product, need help?

  • April 18, 2023
  • 2 replies
  • 2972 views

Our scenario is we have two contractors delivering a vehicle in the same Product.  We will refer to them as CONT1 and CONT2.  CONT1 is building existing vehicles and CONT2 is building new Model Year.  Probably 90% of the data is common between the vehicles.

 

The goal is CONT2 can see EVERYTHING (no real issues); however, CONT1 cannot see anything NEW CONT2 creates.  For example, we have a WINDOW at REV.C and CONT2 revises to REV.D.  Now, CONT1 can see REV.C, but not REV.D.  

 

Any ideas how to execute this?  Should I use Security Labels or possibly something like Edit Access Control and use folder control within the Product?   (Not sure our Admins have that setup yet for us).  

 

I was thinking I could move REV.D to the CONT2 folder or possibly set a Security label for that REV.D file.

 

Thanks!

Best answer by avillanueva

@JohnWenner , do you have ProjectLink module installed? This indeed does work. You are able to share specific revision. If the person has access to the Project, they will only see that version and this leaves the latest version in the Product area.

avillanueva_0-1681910770695.png

avillanueva_1-1681910848667.png

 

2 replies

B
BenLoosli23-Emerald III
23-Emerald III
April 18, 2023

Security labels are over kill for this type of data segregation.

Set permissions so that Cont1 cannot see items that are not released. Only release items that are in the existing model.

Another method would be to use multiple contexts, one for the existing, one for the new. The new context gets the new revisions that Cont2 is doing only. Context ACLs can prevent Cont1 from seeing the work that Cont2 is doing in the 'NewModel' context. When it is done, move the files into the existing model context.

J
JohnWenner6-ContributorAuthor
6-Contributor
April 18, 2023

Can you move files between context at a certain revision.  So context 1 would have REV.A thru C and context 2 has REV.D and above?

 

B
BenLoosli23-Emerald III
23-Emerald III
April 18, 2023

You cannot put different versions in different contexts or even folders. They are tied by the master name index so you move all or none.

avillanueva
avillanueva23-Emerald I
23-Emerald I
April 18, 2023

Sounds like a case for a project. Put CONT1 in a project and share what you need with them. They operate in the Sandbox and everything can be checked into the Product when complete. 

    jbailey
    jbailey18-Opal
    18-Opal
    April 20, 2023

    Agreed. It is the prime use case for PJL

    Terms & ConditionsAccessibility statement