OOTB Promotion Request --> is there a way that just one user of the approver group has to approve PR

[boemi]

Version: Windchill 13.0

Use Case: We would like to work with the OOTB Promotion Request Approvel process. The goal is to allow state changes to obsolete and in work with the PR. Just a small number of users will be allowed to approve this. But only one of these users should approve the PR

Description:

OOTB Promotion Request

--> is there a way that just one user of the approver group has to approve the PR.

Actually every user in the group has to approve it.

Any sugestions how to modify this?

Thanks for the help

[avillanueva]

Its certainly possible but might require modifications to the OOTB workflow. What you are asking for is specifically for obsolete and back to In Work that that approver list is shorter. We had modified our workflow not to make use of an Approver group at the context team level since each PR could have a dynamically created list of approvers. You could create a new role for those cases and added a routing condition that if it was a normal transition, to use the approvers group else it uses this special approver role/group that has a special task to handle approval for that. It would need to split based on the transition state you are moving toward. 

[d_graham]

Doable for sure but as @avillanueva  says it’s going to require custom code.

First, tell us how you know it can be approved by a single Approver vs requiring all Approves.

Is this determine by the PR’s container, a PR attribute, the user who submitted the PR, something about the objects on the PR, etc.

I would write a custom Java class that runs in the complete transition of the workflow task that determines if all or only one Approver is required. If all required the the custom code would then check if everyone has approved it. If yes, the workflow moved on. If no, it doesn’t.

That should get it done for you.

David

[BenLoosli]

If the list of approvers is static, you can simply modify the workflow for the acceptance step so it only requires 1 approver. I had modified my last system so it would require 2 of the users to approve a release. If either rejected it, the promotion was rejected, but it still required two approvers to look at the promotion request.

If you have different approvers, then you will need custom code to build your approver list.

[Catalina]

Hi @boemi 

I wanted to see if you got the help you needed.

If so, please mark the appropriate reply as the Accepted Solution or please feel free to detail in a reply what has helped you and mark it as the Accepted Solution. It will help other members who may have the same question.

Of course, if you have more to share on your issue, please pursue the conversation.

Thanks,

[joe_morton]

Here's the main thing to look at:

You can have multiple approvers in the role, but set it so that only 1 has to approve - "Any"

This would be modifying the OOTB promotion request workflow. 

For us, we have many custom promotion request workflows. For each Product/Library, you can set the Promotion Preferences so that when going to a given target state, the appropriate workflow is used.

Hope that helps!