Skip to main content
S
STEVEG21-Topaz I
21-Topaz I
March 4, 2014
Question

Root folder check in

  • March 4, 2014
  • 5 replies
  • 3520 views

A while back I set the rights so that our users cannot check files in to the root of our Product Context. Because now use change management PTC said we have to give modify rights to any user that creates an ECN Task. Is this true. We continue to get user's forgetting to change the folder of the CAD file.


Steve G

5 replies

M
MikeLockwood22-Sapphire I
22-Sapphire I
March 4, 2014
May want to approach in a different way rather than using permissions.

Object Initialization Rules (OIRs) direct new objects to a specific folder. OTB, all OIRs for all Types direct them to the root folder of the context (/Default). Can just add a folder definition to each existing OIR by extending to /Default/myfolder.
S
STEVEG21-Topaz IAuthor
21-Topaz I
March 4, 2014
Mike,

That seems like a decent option but we would still get users putting files in the wrong folder. 99.5% of the files that get checked in are being set to the correct folder. But when they forget obviously it yells at them to set the folder. And when it does they set the correct folder.

Steve G
M
MikeLockwood22-Sapphire I
22-Sapphire I
March 4, 2014
Ok - Then the permissions in place now for objects other than change objects should apply for change objects as well.
Doesn't seem like anything would be fundamentally different.
S
STEVEG21-Topaz IAuthor
21-Topaz I
March 4, 2014
The difference is that I set the permissions on the Cabinet. Setting the permissions to that affects everything so that no matter what gets checked into the root folder PDMLink will allow (or disallow) it.

As far as I know you don't set the permissions on a Type like EPMDocuments or WTDocument, etc for the root folder.

Steve G
D
ddemay1-Visitor
1-Visitor
March 6, 2014
You can deny modify on cabinet and grant modify on subfolder. This allows
you to make sure everything requires a folder. However change notice tasks
in Java are CabinetManaged and not Foldered. Therefore, you have to use a
load file to create an addition subdomain and cabinet per context. The OIR
for change activities/tasks is then updated to point at this alternate
cabinet. Ours is called /ChgActivities along with the domain of the same
name. In this domain, you can define a modify cabinet permission for the
change activities.



Hope this helps someone.






    Terms & ConditionsAccessibility statement