Hi @srikanth kommul,

 

I just realised this involves some customisation and complexity to consume approval rules. Better to go ahead with your custom implementation.

 

It involves in below steps if you want to use this

 

1) Creating a custom table which extends sn_grc_appr_approval

2) Addinga reference field sn_risk_risk in above custom table

3) Write Business rules and approval workflows that make use of those configurations which you have created.(We have some API like

new sn_grc_appr.ApproverEvaluation().evaluateApprovers("sn_risk_advanced_risk_assessment_instance", current.getUniqueValue())) to support the configuration you have defined.

)

4) Have a reference field of the above custom table in the Approvals table to update the assessment to approve every time and some more items.

 

 

Thanks,

Naveen

Hi Naveen ,

 

           So, this Approval configuration will not work for Risk register form or its seems to be complex right?

 

Thank you

Yes for the risk register form, it doesn't work directly. It needs some code implementation. Please let me know if you need more information. Please give thumbs up if my responses were helpful.

View solution in original post

OK, Thank you Naveen

SauravP67797804
Tera Expert

@Naveen Kumar4  I have a question here , so for any GRC based application approval for the approver user do we need to assign the role - sn_grc_appr.approver or approver user role is sufficient.

What is the use case for assigning users with "sn_grc_appr.approver" role ?