Mandatory reason on second step of approval workflow

Hi,

If we talking about a web portal - then yes, you can create a checkbox or implement other type of control/validation. I've used such approach in recertifications, and mandatory field was Last name of employee. So, even all requests/cases were marked, submit button still inactive until employee entered last name which should be the same as in employee card.

Hi Pavel.

Thanks for your reply. I forgot to mention that we only want this for a group of system roles. If we create a checkbox or other control/validation for this in the web portal, it will be implemented for everything, right?

Are there no "out of the box" solution inside Manager to control a requester has the reason field mandatory AND the recipient manager has to fill out reason of approval?

There is currently no "out of the box" solution to control your requirements for the reason property of a request or approval. There is an RFE logged with VPR#31836 that would allow you to control if the reason property (or the pre-defined reason) is mandatory during request, approval or denial.