Entitlement based approval workflow

[CWMoo]

Hi,

Is it possible to have an approval workflow based on the entitlement selected by the requestor?

In a workflow, request should be routed to individual approver based on the entitlement.

Example:

Operator - approved by Approver 1

Technician  -  approved by Approver 1

Engineer - approved by Approver 2

Data Admin - approved by Approver 3

Thanks.

Regards, Cw

[BorisLekumovich]

If your approval workflow grouping type is configured as "Create an individual job for each change", then in the workflow you can decide who will be the approver and assign him the approval job.

The downside in that approach, is if you have more than 1 entitlement with the same classification, then the approver will be assigned with multiple change items to approve.

for example: If a user request the following entitlements: operator1, operator2 and operator3, then approver1 will see 3 approvals which will be assigned to him

[AmitKhatua]

Hi Boris Lekumovich, Venkata Palakaveeti

My approval workflow is mapped as Create an individual job for each change. 

for example: If a user request the following entitlements: operator1, operator2 and operator3, then approver1 will see 3 approvals which will be assigned to him

In this scenario the approver1 is getting 3 activity with one change item to approve each to approve. 

In my example, ent 102 is attached to shekhar.pandey and 103 is attached to shekhar.pandey and apurba.sen. And user has requested for 102 & 103. I'm using VIA 7.0.2

The downside in that approach, is if you have more than 1 entitlement with the same classification, then the approver will be assigned with multiple change items to approve.

I can see multiple activity for a same CR is getting assigned to approvers with one change item to approve.

Logged in as shekhar.pandey - 

Opened first activity from shekhar.pandey - 

Am I missing anything ?

This also related to the discussion 

Approval Worflow: Using Custom Attribute to Assign An Activity 

Getting SOD name & Remidiator List in a approval workflow 

[BorisLekumovich]

Are you asking why you see 2 change items while you expect to see only 1 change item?

I assume it's because you selected All Changes.

Switch to Changes To Approve and check how many items you see.

From the Perform an Approval from the User Interface help section

Select All Changes to display all change request items. Change request items for which you are not responsible are grayed out.

Select Changes to Approve to display all change request approval items that only you are responsible for processing. For example, you are responsible for processing approvals for requests for access or changes in access to an asset for which you are a business owner or technical owner after user supervisors have performed their approvals in the previous approval phase. As an asset business or technical owner, you would be required to review and process the approval related to your asset and no others.

[VenkataPalakave]

Hi Boris,

I guess what Amit mean here is the approver is supposed to approved both 102 and 103. However, he is getting that into two different activities instead of approving or rejecting at one shot. This is again issue with grouping of activities as we requested for your help in the below link

https://community.rsa.com/message/892775

[AmitKhatua]

Hi Boris, 

Venkata is correct. Being shekhar.pandey attached to entitlements 102 & 103, he should ideally get one activity with 2 changes to take action for one CR (#398) instead of 2 different activities.

 

Actually, what is needed here is the task will be grouped by entitlements (Create an individual job for each change) followed by group by approvers. One approver should not get multiple activity for one CR if he has multiple changes to approve for that CR. 

Any workable solution or workaround in RSA to achieve this ? 

I hope that clarifies your query ? 

Thanks, Amit

[AndyCheek]

Don't know if this is still an issue, but you're essentially asking to have your cake and eat it (as the saying goes).

You can't configure your workflow to create a separate instance for each single change … and then expect the WF engine to somehow magically group approvals together. The approval task is created by the WF instance with the scope of the WF instance. You have specified 1 change per WF, hence 1 change per approval task … even if they are assigned to the same approver.

The alternative option is to look at Group By Custom Category, but this is not blindingly straightforward and needs proper research and analysis. it does work though.

[CWMoo]

Thanks. This is not an issue anymore as I managed to resolve it by using the public system function that allows approvals to branch based on Categories.