Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

How to pass new Account and Add Access to Resource Owner Approval Block

harishyara
Regular Contributor
Regular Contributor

Hello Everyone,

We have a use case of Request Approval Process as below.

1. Manager Approval (New Account and Add Access)

2. After Manager is approved 

3. Check If entitlement is ROLE_APP_ADMIN then the Request (New Account and Add Access) both should go for Resource Owner Approval.

4. After Resource Owner is approved New Account and Add access Tasks need to create.

 

For this I build the workflow as shown below.

harishyara_1-1697653833674.png

 

Issue - After Manager is approved only Add Access (with entitlement name as ROLE_APP_ADMIN if condition match) is going for Resource Owner approval and New Account Task is getting created as it is not going for Resource Owner Approval.

But, I want New Account and Add Access both should go for Resource Owner Approval. How can we send both New Account and Add Access to Resource Owner for approval ?? 

 

Regards,

Harish

4 REPLIES 4

SumathiSomala
All-Star
All-Star

@harishyara Could you please share the request history details for the above scenario.

and when else is satisfied, is it creating the task for both new account and add access task?

Regards,
Sumathi Somala
If this reply answered your question, please Accept As Solution and give Kudos.

harishyara
Regular Contributor
Regular Contributor

@SumathiSomala - I don't have issue with Else condition it is working fine. Problem here is whenever IF condition satisfies New Account and Add Access both should go for Resource Owner approval, But currently only Add Access is going for Resource Owner Approval, but not New Account.

@SumathiSomala Can you please help to update on above one?

Hi @harishyara 

The above behavior is as expected.

In the approval workflow, if the account and entitlement are requested then workflow breaks into account and entitlements tasks. Since the account doesn't have the entitlement, the if-else condition will evaluate to false for account always and it won't go for RO approval. 

You can try the below approach and see if it works.

Select the Security system-> Create Task Action-> EntitlementsOnly and then test with same workflow.

Regards,
Dhruv Sharma
If this reply answered your question, please accept it as Solution to help others who may have a similar problem.