Team Members granted Set State to WTObject, all states?

[avillanueva]

I am reviewing access rights and noticed that all my contexts have Team Members granted Set State rights to WTObject for all states. This is wrong on many levels and I am surprised I never noticed this before. Is there some reason for this? I checked the General Product Template and its granted in that template so I assume that PTC defaulted that to be true. 

Wouldn't this grant users the ability to change states, like setting something In Work to Released and visa versa? Does your system show this?

[HelesicPetr · Accepted solution]

Hi @avillanueva 

My OOTB system do not contains that ACL settings.

I would check when the template has been changed. 

PetrH

[avillanueva]

The only time it was ever updated was during upgrade. This was the General Product Template. The system started at Windchill 7 so its old.  I removed the ACL line.

[BenLoosli]

I just checked both of mine and they match what PetrH has. My system was started at Windchill 11.0, I believe and is now at 11.1. I also checked the test system which is 12.0.2.10 and uses the 11.1 data set.

[KB_10455226]

I have the opposite problem as the original poster. I want my my team members to be granted Set State rights. Can anyone teach me how to give them that?

[avillanueva]

As the original poster, I would caution against list. Its good to establish a good change management process, whether you use promotion objects or change objects. Those workflows should handle the setting of states.  It would be ok for a small, counted on one hand, list of people to have that ability but not all team members.

[KB_10455226]

I understand where you are coming from. Please trust me, though, what I'm after is good for the situation I'm in. Is there anyone that can teach me how to give all Team Members set state privileges?

If no one is comfortable telling me that, then I will fully explain my situation. 

[avillanueva]

This would in each context utilities page - Policy Administrator.  Create a new right in default context. For the objects you want to give access, there should be a set state right that you can grant. You can give it based on all states or certain states. Click the starry icon to create a new ACL rule. https://support.ptc.com/help/wnc/r12.0.2.0/en/#page/Windchill_Help_Center%2FPolicyAdminACLManage.html 

[BenLoosli]

It is under Site-Utilites-Policy Administration.

You need to drill down to the proper context and object type and then edit it for the current state from the table.

If this doesn't help, explain your situation and someone can give a better explanation.

[BenLoosli]

Are you utilizing Promotion Requests to set file states? If so, you should let the workflow handle the Set State changes and only grant the system admins the ability to Set State. It does depend on which direction you are changing the state to/from.

I allow all users to change the state from Design (initial state for all objects) to Pre-Release. This can only be done IF the file version is at a numeric number. We use alpha version for prototype work and numeric for production releases. The user does a revise, then overrides the next alpha version for the numeric version. They have to do the Set State to Pre-Production at that point. The promotion request workflow is set so only certain states can be selected depending on the current state. Design state gets promoted to Prototype and Pre-Production goes to Release or Verification Required.