Configuring Sequential approval mechanism

[youssef_anegay3]

Hello,

i have setup a sequential approval mechanism. So when a user requests a role, it first has to be approved by his manager, then by the role owner (exactly as in the page 21 of the documentation http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/80f324e1-925f-2f10-a7a5-dea9be51b...).

The first approval works fine. SO the manager receives the notification mail and he can approve the request. But once he has done that, for some reason IdM triggers 2 mails, one for the ROle owner and one for the Manager (again), and any one of them can approve the request.

Is that normal behaviour ?

I have made a trace of it, and in the approvers list, both (manager and role owner) appear in the list.

For the second approval i only want one mail to be sent to the role owner, and not to the manager anymore. Is that feasible ?

BR

Y.

[normann · Accepted solution]

Hi Youssef,

if you are using attribute MX_APPROVERS you must not add the role owner as approver using operator {A} because then you have both - manager and role owner - as approvers for next step. You need to use operator {M} or {R} (to remove the manager when you add the role owner).

Regards

Norman

[youssef_anegay3 · Accepted solution]

i am indeed using the attribute MX_APPROVERS to first add the manager and then the role owner as showned in my screenshots ... how do you use the operator {M} or {R} ? is it in the identity store ?

[normann · Accepted solution]

Hi Youssef,

that is all described quite nicely in help (either MMC help or online:

Specifying the destination of a To identity store pass)

Regards

Norman

[youssef_anegay3]

Thanks all for your help problem is solved

[jaisuryan]

Hi Youssef,

Can you confirm if the manager is not configured as approver for the role? or the approver of the role is configured to reference to other role which is assigned to role owner and manager?

It would good if you post the screenshot of both the approval tabs of the approval tasks and destination tab of approver addition tasks and the approvers tab of the role.

Kind regards,

Jaisuryan

[youssef_anegay3]

Hello Jaisuryan,

here is the workflow as defined in here:

the manager is only manager and has no authority on the roles. The role owner is not a manager and not defined as manager

the manager approval is defined as follow:

and for the role owner:

[terovirta]

Like Norman said you need to have the attribute operator that replaces the exisitng value with new one. Now you're adding another approver in the second step.

regards, Tero