Leveraging Intelligent Recommendations for Operational Transformation. AMS Partners click HERE | EMEA/APJ Partners click HERE |
05/06/2024 08:03 AM
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.
Solved! Go to Solution.
05/06/2024 08:18 AM
Hi @VrushaliL , add (entitlement.customproperty1.contains(user.title) eq true) in if else block
05/06/2024 09:01 AM
entitlement.customproperty1.contains(user?.title) eq true
05/06/2024 10:50 PM
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
05/06/2024 10:55 PM
@VrushaliL , could you provide with the logs at the time of request submission? and i hope you are using parallel workflow.
05/07/2024 07:48 PM
05/07/2024 10:58 PM
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
05/06/2024 11:17 PM
@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
05/07/2024 11:46 PM
@VrushaliL add below also else condition include cp1 null condition try it
entitlement!=null and entitlement.customproperty1!=null
05/08/2024 12:51 AM
@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
05/08/2024 02:45 AM
@VrushaliL For Testing purpose can give 'Test' select ent and check confimr ?
05/08/2024 03:55 AM
Please check workflow type on left hand side should be parallel workflow
05/08/2024 04:01 AM
@rushikeshvartak, Yes I am using parallel workflow.
05/08/2024 04:12 AM
05/08/2024 04:36 AM
@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.
05/08/2024 04:40 AM
Validate no space and typo in condition
05/08/2024 04:50 AM
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
05/08/2024 06:21 AM
@VrushaliL can you remove Manager approval first false condition and attach reject try
05/08/2024 07:12 AM
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
05/08/2024 10:34 AM
05/08/2024 11:11 AM
@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: