cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

We are happy to announce the new Windchill Customization board! Learn more.

Policy Admin priority

DonSenchuk
7-Bedrock

Policy Admin priority

I have a sub-type for WTChangeOrder2 (Change Notice) and for WTChangeActivity2 (Change Activity) workflows. The main (non-sub-) type for each is the Engineering Dept release process. The sub-type for each is Manufacturing's 'production release'. Each of the two workflows uses different roles and responsible people so, naturally, each needs to have different permissions for the various stages (states).

 

Everything is working as I wanted it to in testing so now it's time to do up the Policy for all the various roles in each workflow.

 

My dilemma is about the priority of policy concerning main types and sub-types. Here is what i have.

 

 

When I get Policy set for WTChangeOrder2, does that override any policy set for MfgECO?

Or does MfgECO override WTChangeOrder2?

 

I assume MfgECO would inherit any policy settings from WTChangeOrder2 if I forget to set it in the sub-type, but correct me if I'm wrong.

 

Any traps I should be aware of?

1 ACCEPTED SOLUTION

Accepted Solutions

‌Hi

Why are you creating not two SubTypes of the WTChangeOrder2? Modify the out of the box WTChangeOrder2 type that no instance can be created and set the tick to the sub types. So each type can have separete attributes and access rights.

I would answer your question, that the access is being inherited from the default type to the subtype. So if you allowed  to create a Change Order you also allowed to create the subtype.

Regards

BJörn

View solution in original post

3 REPLIES 3

‌Hi

Why are you creating not two SubTypes of the WTChangeOrder2? Modify the out of the box WTChangeOrder2 type that no instance can be created and set the tick to the sub types. So each type can have separete attributes and access rights.

I would answer your question, that the access is being inherited from the default type to the subtype. So if you allowed  to create a Change Order you also allowed to create the subtype.

Regards

BJörn

I only have a single sub-type because the main Change Notice workflow was initiated over a year before I was asked to expand it into manufacturing as well. It wasn't necessary to create a new sub-type to get both of the workflows to work correctly so I didn't bother.

 

re: inherited from the default type to the subtype

Do you mean that if I set policy for the subtype that is different from the main type then the subtype ignores its specific setting and defers to the main type? Or does it just defer if I don't set something in the subtype?

Tech support replied:

 

The subtype will take the permissions from the main type. For any conflicting permissions the main type wins.

 

Thanks for your reply.

Top Tags