Make Approver role mandatory in Promotion Request

I would add a code check for this in the transitions of that workflow task. It only needs to throw a WTException to kick it back to the user and not allow them to complete the task.

Hi @DK_11085982,

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.
Please note that industry experts also review the replies and may eventually accept one of them as solution on your behalf.

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

Thanks,

@DK_11085982 and @ES_11249468 ,

You can do this with a form delegate. The delegate is just a Java class with the appropriate code to get the job done.

It runs when the user hits the "Finish" button. Simple to setup.

In short, the Java code runs when you hit the Finish button during the Promotion Request creation.

The custom Java class delegate that I wrote does 5 checks including checking for at least one participant in the mandatory roles.

Currently the checks include:

1. If the creator has added himself/herself to any restricted roles, for example Approver or Review. No one should be the Approver or Reviewer for Promotion Requests that they create.
2. Do all mandatory roles have at least one users.
3. Are any of the promotables already on an active Promotion Request.
4. Validates all promotables are in the same container as the Promotion Request
5. Validates the select workflow is in the same container as the Promotion Request

The code can be edited to do whatever is specified.  It's just a matter of knowing what's required.

If any of the checks find a problem, the user cannot create the Promotion Request until the problems are fixed, and a window is displayed to the user stating exactly what the problems are.

The idea is to fix everything BEFORE the Promotion Request is created and the workflow started.

Here's a screen shot showing the errors.  In this case I'm creating a Promotion Request that has an object that is already on an active Promotion Request and I have neglected to specify Approver an Reviewer.

You might consider a second delegate to run in when editing a Promotion Request.

The edit delegate/class I wrote checks two thing.

1. Are any of the promotables already on an active Promotion Request (other than the one being edited of course).
2. Validates the promotables are in the same container as the Promotion Request

If any of the checks find a problem, the user cannot edit the Request and a window is displayed to the user exactly what the problem is.