GRC 5.3 CUP Approver Determinator

[mmanara]

Hi All,

we are on GRC 5.3 CUP-RAR (SP20) capabilities deployed.

Our scenario is: the same role can have several approvers, identified by different local divisions  and process the role belongs to (a matrix).

Eg.

ROLE 1 for (Request Functional Area "AA") AND (Role functional Area "BB")  -> Approver X

ROLE 1 for (Request Functional Area "CC") AND (Role functional area "DD")  -> Approver Y

the role is the same with different functional area assigned.

To realize the scenario above we have defined a CAD (Custom Approver Determinator) formed by two fields.

1) Request Functional Area AND

2) Role Functional Area

The combination of those two attribute identify the approver.The stage approval/Rejection level is at Role level.

It seems that the Functional Area of the Role is not properly taken into account during the identification approver.

Any similar experience?

Thanks.

Massimo

[Former Member · Accepted solution]

Hello,

I had this issue in 5.2. To fix it I made the CAD look at the "Company" in the request and "Functional Area" in the role. That is the only workaround I had.

If you can consider the "Company" from the header level instead, that may be the better solution in the log run.

[mmanara · Accepted solution]

Thanks for your reply. We have tried in several ways without reach our goal.

At the end we have changed our role concept to setup a role owner as approver.

Many thanks.

Massimo

[Former Member · Accepted solution]

Sorry to hear that the strategy had to be changed.