Skip to main content
lgrant16-Pearl
16-Pearl
August 11, 2026
Question

Same workflow task to same Role in different contexts

  • August 11, 2026
  • 1 reply
  • 49 views

The company is not using the normal team templates and they have run into an issue where they have the same Role in two different Product contexts and they want to send a task to that Role and have (ALL) both users get the task and both vote (or take the action). The developer is saying that “Windchill only allows 1 role per task, so the same role selected in multiple contexts and/or change teams, will combine all of the users from those teams for a given role”.

The problem is we need everyone selected regardless of context in that Role to get the task and complete the task. As it is now, if anyone completes it then all tasks are completed.

We could create versions of the same Role and append with the context name…
But it seems like PTC should have come across this issue before like having Doc Control process CR’s for all product contexts by having the task sent to a group and all members of the group must complete the task?

The customization is the use of a Document with sections for Approvers, Reviewers. These documents sit in each context and have a “Team Document” name that the workflow looks at. It a way to get around who can manage the approval templates. Another custom interface manages the selection for the task using that document as the resource pool and that feature also manages the ALL or ANY.

When they do use ALL, the workflow skips the second user in the same Functional Role selected in another context as soon as one context votes.

1 reply

joe_morton
joe_morton19-Tanzanite
19-Tanzanite
August 12, 2026

Let me see if I understand the scenario:

  • The company has Product A and Product B. In both Products, there is a role, let’s call it Approvers.
  • The company has a workflow that might run in either Product A or Product B. When the approval task is generated, they want that task to get assigned to Product A’s Approvers AND Product B’s Approvers.
  • All the Approvers should click the “Approve” button - not just 1

Did I get that all right?

Assuming yes, here are my thoughts:

  • I know it would be a big shift, but I’d recommend re-evaluating the customization. I would bet you can manage this easier using more standard promotion requests or even a Set State that kicks off a custom workflow.
  • I would recommend against creating Role’s with the context name appended. The point of Context/Role is that you have the “Approvers” (for example) set in Context A and different “Approvers” set in Context B. Documents that live in Context A get approved by Context A’s approvers, and vice versa. This makes it so you can reuse the same workflows across Products when there’s different people responsible.
  • Why are the documents in different Products to begin with? If they need to be approved by the same people, why not combine them?
  • Alternatively, just put all the required approvers in the Role in both contexts. Make sure to set the approval to “All”. And if your customization can’t do that.. well, see my first point.
  • I’ve never seen a workflow use roles from multiple contexts. I know of Shared Teams, but I’ve never used those. You can assign tasks to a Group. Groups live at the Org level, so only Org admins can update them, but they can be used by workflows in any Context.

Hope that helps!

    Terms & ConditionsAccessibility statement