# Provisioning Completed Workflow Trigger Filtering

**URL:** <https://developer.sailpoint.com/discuss/t/provisioning-completed-workflow-trigger-filtering/32146>\
**Category:** SHF Discussion and Questions\
**Tags:** workflows, identity-security-cloud\
**Created:** [February 23, 2024, 9:13pm UTC](https://developer.sailpoint.com/discuss/t/provisioning-completed-workflow-trigger-filtering/32146 "2024-02-23T21:13:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dominick-miller](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/dominick-miller/32/29002_2.png) [@dominick-miller](https://developer.sailpoint.com/discuss/u/dominick-miller)\
**Post date:** [February 23, 2024, 9:13pm UTC](https://developer.sailpoint.com/discuss/t/provisioning-completed-workflow-trigger-filtering/32146/1 "2024-02-23T21:13:42Z")

</div>

Hi,

I am unable to trigger a provisioning completed workflow using the following filter logic:  
$.accountRequests[?(@.source.name==“Test Active Directory” && @.provisioningResult==“committed” && @.accountOperation"Create")]

I have also tried the following variations with no luck:  
$.input.accountRequests[…]  
…@.accountOperation(“CREATE”)…  
…@.provisioningResult==“SUCCESS”…

The workflow, with no json filter query, executed fine and the above path should work based on the csv results I was able to pull from the successful run. The only thing I can think of is if the json path filter does not support logical operators like == and &&.

Does anyone have any ideas?

---

<div class="post-metadata">

**Author:** ![GOKUL\_ANANTH\_M](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/gokul_ananth_m/32/14416_2.png) [@GOKUL\_ANANTH\_M](https://developer.sailpoint.com/discuss/u/GOKUL_ANANTH_M)\
**Post date:** [February 24, 2024, 12:15am UTC](https://developer.sailpoint.com/discuss/t/provisioning-completed-workflow-trigger-filtering/32146/2 "2024-02-24T00:15:26Z")

</div>

Hi @dominick-miller ,

Welcome to Sailpoint Developer Community.

Try this,

1. As provisioning got completed, provisioning completed trigger will be executed right. Hence, in filter use:

`$[?($.sources == "Test Active Directory")]`

1. Use compare strings operator to verify the operation:

In value1, provide “$.trigger.accountRequests[\*].accountOperation”  
In value2, provide “Create”  
Operator “Equals”

Thanks!

---

<div class="post-metadata">

**Author:** ![RAKGDS](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/rakgds/32/2795_2.png) [@RAKGDS](https://developer.sailpoint.com/discuss/u/RAKGDS)\
**Post date:** [February 24, 2024, 4:53am UTC](https://developer.sailpoint.com/discuss/t/provisioning-completed-workflow-trigger-filtering/32146/3 "2024-02-24T04:53:47Z")

</div>

Hi Dominick,  
Please use the following. It should work

$.accountRequests[?(@.provisioningResult == ‘committed’ && @.provisioningTarget == ‘Test Active Directory’ && @.accountOperation==‘Create’)]

Thanks  
Rakesh Bhati

---

<div class="post-metadata">

**Author:** ![dominick-miller](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/dominick-miller/32/29002_2.png) [@dominick-miller](https://developer.sailpoint.com/discuss/u/dominick-miller)\
**Post date:** [February 26, 2024, 4:03pm UTC](https://developer.sailpoint.com/discuss/t/provisioning-completed-workflow-trigger-filtering/32146/4 "2024-02-26T16:03:17Z")

</div>

This worked perfectly, thank you. I think the core of my issue was 1) sometimes forgetting equal signs and 2) capitalization.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [April 26, 2024, 4:03pm UTC](https://developer.sailpoint.com/discuss/t/provisioning-completed-workflow-trigger-filtering/32146/5 "2024-04-26T16:03:35Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.