- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-03-2022 11:13 AM
I have created a rather simple Flow that works against a custom table extended from Incident. I want the flow to run when a new record is created via the Service Portal (Record Producer). Tickets are able to be manually created, but those should not activate the flow. The flow works successfully when tested, and works successfully with no filter applied when submitting a ticket via the Record Producer, but it also runs against manually created tickets. When I add a filter Catalog Item is empty, the flow does not run at all. How do I get the flow to run only when a Catalog Item creates the new record?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2022 06:37 AM
Okay, I figured this out. cat_item is OOTB on sc_req_item, we promoted that field to task and thus inherited it down to incident. This was years ago, so I have to get that from one of our long-time folks.
The script that populates the field is running on Item Produced Record, so you were correct, it was not updating the value before checking the flow condition. To get past this I used a Record Producer Script to populate the field at insert. Now the Flow Condition can use cat_item.active is true to execute the flow.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-03-2022 11:17 AM
What is your trigger condition?
Is it catalog item or the extended table?
Aman Kumar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-03-2022 11:26 AM
record created on extended table > Catalog Item
After posting I tested that the filter does work in an IF Flow Logic, and then I can End the flow. But that is not ideal as it runs the flow needlessly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-03-2022 11:46 AM
There is no condition as such that trigger will not work with filter condition
Check below how it works.
https://developer.servicenow.com/dev.do#!/learn/learning-plans/quebec/citizen_developer/app_store_learnv2_aescreateappfromscratch_quebec_triggers
Aman Kumar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-03-2022 12:28 PM
I see what you mean, so I tried cat_item.active is true and it doesn't like that either. Does this not work with dot-walking either?
