How to pull variables dynamically from the Create Catalog Task action in Flow Designer?

[Maurice Murphy]

We're trying to reduce the need to create bespoke Flows for each catalog item we create, however we're struggling with the fact that 99% of our fulfillers work out of an SCTASK rather than a RITM, and as such there is always an ask that variables for the RITM are brought down into the SCTASK.

I understand that this is possible simply by specifying the catalog item in the "Create Catalog Task" action in Flow Designer, and then selecting your variables from there, however the problem we have is that if we want to use one Flow for multiple catalog items (for example, items built in Catalog Builder by citizen developers), we have no way of dynamically selecting these catalog items:

My question is this: Given that there is no data selector, is there any way for us to dynamically select a catalog item with all of its variables based on the item that has been submitted?

I imagine this will require some kind of custom action to be created, but I doubt we are the first (or the last) organization that will encounter this particular thing.

[Josh Petrick · Accepted solution]

We changed the Variable Global field (item_option_new.global) to have a default value of true.  That way all newly created variables are global, and don't have to be specified in the flow to show up on catalog tasks. 

[Maurice Murphy]

I just tested this and it looks like it's even retroactive on previously submitted catalog items. This is great, thank you!
I do have one question, though. I am going to test this, for certain, but have you run across any issues with variables that are marked as global, but are also specified within a Flow when creating a task? Do you know if it creates any duplicates of the variables on the SCTASK, or does it just work as normal without conflict?

We have a number of Flows already individually specifying variables to appear on a task, so mainly wondering if I should make a bulk change to all variables, or simply make it the new default so anything new picks this up.

[Josh Petrick]

I haven't noticed any issues with variables being global and also specified within a flow.  It doesn't create a duplicate on the sctask.  You'll need to do that for any variables that are used in the flow itself.

[SAI VENKATESH]

Hi @Maurice Murphy 

You can use the action "Get Catalog Variables" as attached in the image

Thanks and Regards

Sai Venkatesh