Solved: disable "set state" option for CAD Author

mmontgomery-2 · ‎Jun 16, 2014

Greetings,

We've recently migrated to Windchill, we like the promotion process however the "out of the box" configuration allow the CAD author to completly bypass that process by simply using the "set state" option in the right click menu. I've configured the lifecycle template to not allow "set state" for transiitons but it still allows. I've also gone into Policy administration and tried to limit permissions, to no avail. Any help would be greatly appreciated, thanks in advance.

Marc

MikeLockwood · ‎Jun 17, 2014

1. Users do not have Set State available unless you specifically configure a permission (ACL) for it - to EPMDoc at some state, or all states - or possibly for WTObject.

2. Non-admin users can only Set State if the lifecycle transition is in place. Your experience listed above indicates that the users are Site and/or Organization admin and/or Manage of the Product/Llibrary where the data is stored. Or - If the lifecycle template at one time had a set state transition defined, it's possible that CAD Doc's which have not been revised since iterating the lifecycle template have the transition still.

3. Windchill should come with a Product / Library template with ACL's just to experiment with. Try creating a Test Product and make it "Private." Then delete all the ACL's that are created from template (laborious - there are a lot). Log on as test user - that user will not be able to access the Product. Add back Read for Cabiinet and subFolder. From there, add incrementally for EPMDoc.

View solution in original post

MikeLockwood · ‎Jun 17, 2014

1. Users do not have Set State available unless you specifically configure a permission (ACL) for it - to EPMDoc at some state, or all states - or possibly for WTObject.

2. Non-admin users can only Set State if the lifecycle transition is in place. Your experience listed above indicates that the users are Site and/or Organization admin and/or Manage of the Product/Llibrary where the data is stored. Or - If the lifecycle template at one time had a set state transition defined, it's possible that CAD Doc's which have not been revised since iterating the lifecycle template have the transition still.

3. Windchill should come with a Product / Library template with ACL's just to experiment with. Try creating a Test Product and make it "Private." Then delete all the ACL's that are created from template (laborious - there are a lot). Log on as test user - that user will not be able to access the Product. Add back Read for Cabiinet and subFolder. From there, add incrementally for EPMDoc.

mmontgomery-2 · ‎Jun 17, 2014

Thank for your reply Mike. Turns out in permissions, Cad Author had full permissions set up for WTObject. I simply removed full permissions, denied "set state" and "administration" and now it's gone. Thanks again.

MikeLockwood · ‎Jun 19, 2014

clues continue to build

So - If it works as desired in a Private context but not in a non-private one, then there is some deny permission in place at Org or Site (likely Org). Private does not use any permissions at Site or Org. Deny permissions are labeled various ways depending on the Windchill release - could be a Deny column, or a minus sign, or an exclamation point.