Workflow - check user title in entitlemet.customproperty1 for approval

[VrushaliL]

Hi,

Test case: If the User title is present in entitlement.customproperty1 then access auto-approved. If the user title is not present in the entitlement.custompropert1 then it follows manager approval.
note: entitlement.customproperty1 has comma-separated multiple title values.

Please let me know if anything is required.

Thanks,

Vrushali.

[NM]

Hi @VrushaliL , add (entitlement.customproperty1.contains(user.title) eq true) in if else block

[rushikeshvartak]

entitlement.customproperty1.contains(user?.title) eq true

[VrushaliL]

Hello @rushikeshvartak, @NM 

I tried with the above query but its not working. Showing error while submitting request from ARS page attached screenshot for reference.

Workflow

Below is the screenshot of having data in entitlement.customproperty1 

Thanks,
Vrushali

[NM]

@VrushaliL , could you provide with the logs at the time of request submission? and i hope you are using parallel workflow.

[rushikeshvartak]

• ,"ERROR","Exception in workflow service"
  "2024-05-07T06:09:45.042+00:00","ecm","","","","javax.el.PropertyNotFoundException: Target unreachable, base expression '. customproperty1' resolved to null at de.odysseus.el.tree.impl.ast.AstMethod.invoke(AstMethod.java:84) at de.odysseus.el.tree.impl.ast.AstMethod.eval(AstMethod.java:78) at
•  
• Please add one more if else condition 
• entitlement!=null
• It seems you have raise new account request  and account will not have CP1

[VrushaliL]

Hello @rushikeshvartak ,
I added one more if-else block with the condition (entitlement!=null). But facing the same issue while submitting request new account request with new access.
When I only raised a request for a new account then it followed manager approval.
But I raised a request for a new account with new access and then got a server error while submitting a request.
Attaching screenshot of the workflow and logs file for reference.

Thanks 

Vrushali

[VrushaliL]

@NM, Yes I am using parallel workflow and please find the attached logs file for reference.
Let me know if anything is required.

Thanks

Vrushali

[Raghu]

@VrushaliL  add below also else condition include cp1 null condition try it

entitlement!=null and entitlement.customproperty1!=null

[VrushaliL]

@Raghu added both conditions (entitlement!=null and entitlement.customproperty1!=null) but showed the same error while submitting the request from the ARS page. 

In entitlement.customproperty1 have multiple title value with comma separated as shown in below screenshot.

I think by this workflow condition (entitlement.customproperty1.contains(user.title) eq true)

 saviynt are not able to read that title value from entitlement.customproperty1.

Thanks,
Vrushali

[Raghu]

@VrushaliL  For Testing purpose can give 'Test' select ent and check confimr ?

[rushikeshvartak]

Please check workflow type on left hand side should be parallel workflow

[VrushaliL]

@rushikeshvartak, Yes I am using parallel workflow.

[rushikeshvartak]

• Share workflow 
• share logs
• try only ent request

[VrushaliL]

@rushikeshvartak ,
Please find the below attached screenshot for the workflow and logs file for the entitlement request. 
Workflow: (Workflow type parallel)

Error on ARS page for ent request

Thanks

Vrushali.

[rushikeshvartak]

Validate no space and typo in condition 

[VrushaliL]

@rushikeshvartak 

There is no extra space or typo in if condition.
Using below conditions.

entitlement!=null and entitlement.customproperty1!=null

entitlement.customproperty1.contains(user.title) eq true

Thanks,
Vrushali

[Raghu]

@VrushaliL  can you remove Manager approval first false condition and attach reject try

[NM]

Hi @VrushaliL, try once with adding bracket at the start

(entitlement.customproperty1.contains(user.title) eq true) 

And keep only one value in cp1 and test whether it is going to approval or not 

[VrushaliL]

@NM and @Raghu 
I tried with above solutions but faced the same issue.

Thanks 

Vrushali

[Saathvik · Accepted solution]

@VrushaliL : Change the WF Logic as shown below and it should work as expected. This has been tested successfully

Request details:

User Title:

Entitlement CP1: