cancel
Showing results for 
Search instead for 
Did you mean: 

GRC AC request- Requestor to Update

former_member218247
Participant
0 Kudos

Hi Experts

We have a requirement from our client that the SOX approvers instead of rejecting the request should be able to send the request back to the requestor to update in case of any value is wrong(Such as user group,validity dates etc)

Solution which i am trying

Create a new stage after SOX approver stage with agend id(Requestor) so that the request flows to requestor after SOX approver stage and the requestor can update the field which is wrong as per commnets of SOX approver and then resubmits the request and then it flows to security admin for final approval.

Now my main challenge is that the Request to flow back to Requestor after SOX approver stage needs to be scenario specific(Like User group is wrong,Valdity dates chosen is wrong).I guess i need to create a rule id in BRF+ for this scenarion which looks quite complex.

Let me know if anyone has better idea on this.

Thanks

Nitesh

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member218247
Participant
0 Kudos

I guess there is varaible for Return to Requestor.

Let me check if i can use it here

former_member193066
Active Contributor
0 Kudos

hello Nitesh,

workflow can be send to people who exist in system.

if user does not exist in GRC system , i think its not possible.

Regards,

Prasant

former_member218247
Participant
0 Kudos

Hi Prasant

The request needs send back to the requestor not the user.

Requestor can be self(If user is existing) or other person.

Thanks

Nitesh

former_member193066
Active Contributor
0 Kudos

Hello,

not sure if you are using enduser logon to raise request.

Requestor can be anybody.

he can raise request for self or others.

if the user id either of requestor exist in GRC system then request can be sent to user.

if it does not exist then you cannot send it.

as far i know.

Regards,

Prasant

former_member218247
Participant
0 Kudos

Hi

The requestor will exist in GRC system.We wont have case where requestor is not in GRC.

I can return varaible can be used here for sending the request back to user in case of more detaisl required

Thanks

Nitesh

former_member193066
Active Contributor
0 Kudos

OK..

in this case, these is no such standard behavior.

but you can achieve it.

i believe requestor has to send it back to manager as well.

you can have a path and map agent to requestor.

you need to use BRF+ to have Requestor as agent that can be achieved using DBLOOKUP.

Regards,

Prasant