on 02-25-2015 11:55 AM
Dear all,
we have problem in our production environment of GRC 10.0 (SP15).
We have access requests which includes multiple role assignments, which must be approved by multiple role assignment approvers.
Now we have recommended that one role assignment approver can reject the request for all role assignment (for the complete stage) for all roles if he press the Button "Other Actions->Reject".
The request for all role assignments is rejected. Other Role assignment approver can not edit the request anymore.#
They don't have the access request in their Work Inbox.
The request will be closed.
If the role assignment approver reject on item level and press "Submit", everything is ok.
But if he press the Button "Reject", - not only the approval for the roles of this role assignment approver are rejected. (header level).
In summer 2014 we have implemented the SP14/15.
After the SP we have not changed the workflow settings.
As far as I remember the behaviour was different before SP14/15.
Can someone help?
BR
Melanie
Dear Melanie,
simply change the rejection level for this stage to "Role" instead of "Request" so that the role owner cannot reject the whole request.
Let us know if it works.
Regards,
Alessandro
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Melanie,
You need to remove REQUEST REJECTED checkbox from your stage settings. This gives option to reject entire request
Rejection Level roles gives option to change the Lineitem status to REJECT
If you have both then even if I role owner rejects using OTHER ACTIONS -> REJECT then entire request gets rejected. So remove Request Rejection option for this stage.
Regards,
Madhu.
Hi Melanie,
If the role owner select the REJECT option under OTHER ACTIONS and reject the request then it implies that entire request is rejected.
If the role owner changes the approval status as REJECT at Line Item level and click on SUBMIT button, then only that particular role is rejected and not the entire request.
This is the correct behavior.
Regards,
Madhu.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.