Skip to main content
A
AJ_2224731-Visitor
1-Visitor
January 4, 2012
Solved

WNC 10M020: How to prevent creating new objects in the root folder?

  • January 4, 2012
  • 1 reply
  • 6838 views

Windchill 10.0M020: How do we prevent users from creating new objects in the root folder of a product or library? They should be able to create in subfolders. I tried denying permissions for the default domain and granted permissions on a different domain then used it for sub folders, but the sub folders are also getting deny permissions. What is the best way to do this on Windchill 10M020?

Best answer by OliverDroop

Deny permission is the strongest and can not be overwritten with grant on a lower level. Deny should only be used in very rare cases. All ACLs will be inherited from parent domains.

You can easily achieve this by removing modify permission for cabinet. That will do the job - all objects need to be stored into folders.

Default Domain of Context/Cabinet Object/TeamMembers/Read

Message was edited by: OliverDroop

1 reply

M
22-Sapphire I
MikeLockwood22-Sapphire I
22-Sapphire I
January 4, 2012

Don't attempt to control this via permissions. Instead, configure the OIR for each object type (e.g. EPMDocument) to a folder below root (e.g. /Default/CADDocuments).

Note: This is also an easy way to prevent creation of an object type in a specific Product or Library - don't create the specified folder. For example, we have a Library used for Patent Documents, and do not allow WTParts to be created there.

A
AJ_2224731-VisitorAuthor
1-Visitor
January 5, 2012

Thanks for the post Mike. Seems like there is a problem if the folder that we specified in OIR is not existing.

https://www.ptc.com/appserver/cs/view/solution.jsp?n=CS36541

I also tried to direct into a folder which has restricted permissions, in the OIR, but then the location seems to be changing to the value of the "/Default" location.

OliverDroop
OliverDroop15-Moonstone
15-Moonstone
January 12, 2012

You should remove the write permission to cabinet object (like root for that context) in the default domain. Subfolder is a different object.

It might be that you need to add modify permission in the subdomain again - not sure how WC10 handles this meanwhile but first I would try without it.

Terms & ConditionsCookie settingsAccessibility statement