How to differentiate account vs entitlement in workflow as part of modify request

[Saathvik]

Team,

We have a requirement, As part of service account modification user can modify account details and also add/remove access to/from service account.

Now if user submits both changes like modified account details and also added/removed the entitlement as part of request we need to differentiate the account vs entitlement and send account changes to auto approval whereas entitlement should go through approval.

To differentiate the account vs entitlement I tried below options

1. (entitlement==null)
2. com.saviynt.ecm.workflow.Request_Access.get(new Long(requestaccesskey))?.accesstype==3 with groovy enabled

Can someone assist me with logic to achieve above scenario

[armaanzahir]

Hi @Saathvik 

Can you try using the following variable to achieve your use case:

entitlement.entitlement_value == null

We are currently using this to segregate account and access flows.

Thanks,

Armaan

[pmahalle]

Hi @Saathvik ,

Can you try below for entitlement related request.

requestcounts.ADD_ACCESS_REQUESTS_COUNT > 0 OR requestcounts.REMOVE_ACCESS_REQUESTS_COUNT > 0

[Saathvik]

Thanks for the replies. Not sure why it didn't work but I recreated the new WF with same condition (entitlement==null) is started working now. Testing further will keep the post updated if I face any further issues

[Saathvik · Accepted solution]

We have identified the issue is with one of the if-else block which has same name as other if-else block which is causing the issue