User access to templates under a product

[Paul123]

Version: Windchill 13.0

Use Case: I need users within a specific group to access and initiate workflows.

Description:

I have created a new product "Parts" and set up the groups and users.

I need the user within the new "CAD User Group" to initiate a workflow.

The issue is they can not see the Templates option under "Parts".

I added both the Workflow Authors and Workflow Administrators groups to the user with no change.

I can see if I add the Org Admin group to the user they can see templates, but then they have too much authority.

[TDT]

Hi @Paul123,

Why do you need your users to initiate the workflow manually?

Create a acl at product level to provide access to read templates for the required groups.

[Paul123]

Our routes are more for notification of next steps. i.e. mechanical design is complete so the parts are ready for check and to have punch programs created or modified or engineering is complete and planning needs to be notified to check production job affected.

Sorry, what is an acl?

[TDT]

Access Control List.

Create an Access Control Rule, to enable templates at product level for particular group of users.

[Paul123]

I have tried adding wt.workflow.engine.WfExecutionObject to the new product with no change.

Should I be looking at a different control type?

Which control type is for access to the templates?

[joe_morton]

Try looking for the object "Workflow Template"

But to echo what Paul said, there are better ways to manage this. You can have an object that when created automatically initiates a workflow. Some examples:

• If you will change the design's state at the end of the workflow, you can use a Promotion Request. You can configure different workflows for different target end states (meaning different workflows to get to Prototype vs Production, for example) 
• If you just need a generic workflow, you can make a Document Subtype. If you have different workflows, you can have a different subtype for each one.
• If you want to have a record of what objects were in the workflow, but don't want to change state, you could consider using a Baseline.

Having an object (Promotion Request, Document, or even Baseline) to manage the workflow is much better because you have a nice place to go check the status and view history afterwards.