Flow Designer not triggering when trigger has filter

[George P]

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?

[MrMuhammad]

Hi,

As you mentioned, you are applying filter Catalog item is empty. I assume the Catalog item is a custom field on the custom table that you have created. If so, I'd like to understand how are you populating that field when the record is created via record producer.

Regards,

Muhammad

[George P]

It is the OOTB cat_item field extended from Task to Incident and now to my custom table, which is extended from Incident.  It is populated when an Incident is created via a Record Producer.  I do not know if we added that functionality, but it simply records the Catalog Page where the ticket originated if applicable.

[MrMuhammad]

I've never seen this field OOB. I think this must be a custom field in your system. 

Regarding the flow trigger issue, I believe the flow designer is triggering even before the catalog item field is populated. Can you please check on the record producer script field if we are populating this field from there? 

Regards,

Muhammad

[George P]

Muhammad, there was another comment from you that seems to have been removed, but it gave me some insight.  I am apparently mistaken in thinking this was an OOTB field, not sure how we created a field with out u_, but there it is.  So I am going to look for the script that populates that field to see where it fits in the process.  Thanks for the lead.

[George P · Accepted solution]

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.