Lookup Select Box variable on Flow Designer

[Dariussiriuse]

Hi everyone!

I am finding myself into a situation where I have a table with simple fields {name | number | sys_id}.

I created a catalog item that has a Lookup Select Box to get the values from that table.

Moving forwards, I created a flow to handle the submission of this request.

My issue is that when I pull in the variables from the catalog, the variable in question is of type 'choice' but displays no values inside of it? So, on a condition of 'if (get catalog variables -> var1)  |  is  |  --none--' , the '--none--' will have no other choices to select. 

I tested as well a copy of itself using only a Select Box, but my issue with this is that on the Catalog Item, I can't bring the table where the records are for choice, and therefore I have no choices displayed (unless I create those choices manually onto that variable configuration page). But I don't want this, I need the user to be able to input those new choices via record. And the Lookup Select Box is perfect for this!

But yeah.. I can't get the choices onto the flow.

Any ideas how I can make them appear?

regards,

Darius

[Dariussiriuse]

Also, just to mention, I have just now created an action to log the value of the var1, it says undefined....

Yet on the requested item record, it does show the actual value

[Teresa Carvajal]

Hi Dariussiriuse,

I am running into the same issue that you described. Have you found a solution?

Thank you,

Teresa

[Dariussiriuse]

Hi Teresa, I'm afraid I haven't tried to find a solution for this anymore as I moved on to different projects, but see for yourself if you could perhaps handle the comparison through a flow action:

You could try to lookup for both the table of choice (store them into a var list) via script, and then access the created requested item record (from which you extract the value or f the variable desired) via script as well. Maybe you could compare the two within that action this way?

It seems to be overcomplicating, but I frankly don't know how else you would be able to do this.

My recommendation would be to do this first on the /sys.scripts.do page (Scripts - Background), and make sure that it works on there. Once you have the desired effect, just copy paste it on your flow action really.. and of course make the changes so that you have an output for the rest of the flow. Have as answer 'yes' or 'no' returned, and use that as the comparison on your flow after calling this action. 

Maybe you could have the sys_id of your requested item as input to this action, it would be easier.

But yeah, try this in scripts.do first, and then move on to flow action.

Let me know how you get on with it, I should be available.

Regards,

Dariussiriuse

[Vishal Birajdar]

Hi @Dariussiriuse 

It will be better if you share some screenshots please...!! if possible..