Relation between REST and visible elsewhere option

[Diogo Soares]

I have a catalog item with variables and a flow associated. The variable values are sent via REST using a scripted rest api. Those values should be caught by flow using Get Catalog Variables action. However, the flow is not doing what it should.

What I discover was that having a variable with Visible Elsewhere option false and the value of it sent through REST API, it won't be catch by flow associated with catalog item.

When Visible Elsewhere is true then the flow catch the value of variable sent through REST API.

Are really those related? Visible Elsewhere need to be true so the flow can considered the sent variable value?

The main goal is to hide variables sent by REST in RITM.

[OleksiyK]

It's not about the flow or flow action. If you examine Variable Ownerships [sc_item_option_mtom], the table which links runtime variable values with their RITMs, then you find out that no runtime value is created for a variable which is Visible Elsewhere = false. Hence your flow action physically won't find it, and your flow won't transmit it.

Yes, I find it very "exciting" too...