Currently, the “forward” option on workitem is disabled for end user who requested the access and pending for approval.
Would like to enable 'Forward" option for the requester who initiated on workitem. Is there any configuration available for this or any customization recommended?
Only certain elevated capabilities have the ability to reassign/forward work items in that manner. There’s no way to enable that globally. If there was, it would open up a big can of worms as you would then have to come up with a way for users to not be able to reassign it to themselves (or a friend) for approval, and would largely negate the whole purpose of requiring an approval in the first place.
A better alternative would be to dig into the access request workflow and set up automated reminders and escalation (reassignment via the workflow) to try and address the non-responding approver.
Brian is correct. However, we have used special custom approval assignment rule and try to identify the correct approver in the beginning of the request. Assuming you talk about LCM Provisioning. It is possible to pass the argument “approvalAssignmentRule” into the step (and workflow) Approve and Provision.
We try to assign there correct and active Identity as approver for the request to avoid delays for the requester. The approvalAssignmentRule can then provide possibly best approver for the request.
Thank you - @brian_weigel and @neeme_vool for your quick reply.
We already use the “approvalAssignmentRule” for assigning the best possible approvers and self approval is restricted.
The use case we are trying to solve here is when the approver is not available requester can forward the request to other approvers (filtered identities) instead of reaching out to admin users which causes delay in getting approvals.
Unfortunately, this is not possible OOB. You do have a few options on how to handle this kind of scenario, but none of them will allow the requestor (or anyone else that doesn’t have the correct IIQ rights) to manually reassign approvals in the way you’re describing outside of building a separate custom workflow that has that capability.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.