Flow Designer: Triggering conditional tasks based on List Collector Selection(s)

[Josh Pirozzi]

We've been tasked to develop a Catalog Item and Flow where our end-users can select multiple Business Application CI's and, based on the selected CI's, conditionally trigger Approval Requests and/or Catalog Tasks. 

We've created the Catalog Item with a List Collector Variable that references our Business Application Table and when initially trying to incorporate a 'For Each' Step in our subflow, the selected CI's were not recognized and no Tasks were generated. 

Thanks to @Ankur Bawiskar and his fantastic post on the subject (https://www.servicenow.com/community/developer-blog/using-list-collector-in-flow-designer-for-each-l...) we made an attempt to create a Custom Action, but after incorporating the Action into the subflow, we received errors that the selected CI's didn't carry through the Action and weren't available for our For Each Step. The Custom Action has been built to include the updated notes Ankur provided where Output Type = Array.Object.

Here is the Error Message: 'Error: Cannot convert null to an object.,Detail: Cannot convert null to an object.'

We're currently on Vancouver Patch 4 HotFix 1a, and wanted to see if there have been updates on how to handle entries in a List Collector in Flow so the Flow recognizes each selected CI. 

[Ankur Bawiskar]

@Josh Pirozzi 

thanks for checking that blog.

I think the way list collector now works is somewhat different when that blog was crated.

there are some latest discussions in that blog which should help you

[Josh Pirozzi]

Hi @Ankur Bawiskar ,

I was thinking the same thing. After reading through the recent posts on your blog post, it seems like the issue is still there, or came back with Vancouver. Would you happen to know an alternative or update to the Action?

Thank you,

Josh