Use a child flow (or other method) to initialise a list of variables and then feed back into main flow

[Rhys_AMSHelix]

Hi,

I am working on a very large flow and have reached the maximum limit for the number of actions (mainly due to creating a lot of variables)

Is there a way to outsource the creation of these variable to another flow, child or otherwise, and then have the variables available in the main flow? I've not used child flows before and can't figure out how to feed the initialised variables back into the main flow.

Thanks for the help

[VictorIvanidze]

Hi,

don't you think minimization of amount of variables is much better way?

Try to replace pairs Initialize variable/Set Variable  to Compose actions.

Also I guess a significant part of your variables are constants.  Use a single array instead of several variables.

[Rhys_AMSHelix]

Most of my variables aren't constants but are strings used later in the flow. I'm also not sure that I can use the compose action to initialise/ set a variable because I need to initialise the string variable and then append it later based on a control action

[srduval]

if you have a premium license, you might be able to spin some tasks off via the HTTP action. You won't get any feedback (back into your main flow) that it completes but for anything that doesn't have any downstream implications, it's a simple way to split flows into smaller chunks. You can write the HTTP body to accept parameter/variable values, so you can pass values from flow a to flow b when you invoke flow b. Beyond that without seeing your specific flow it's hard to see what's going on. 

[VictorIvanidze]

Hi @Rhys_AMSHelix,

understood. What about using array instead of  set of values?

[Rhys_AMSHelix · Accepted solution]

I have managed to reduce the number of actions by using compose actions instead.

Rather than initialising a variable and then appending it with one of two statements depending on a condition action I was able to remove the initialise action and have two compose actions in the yes and no sides of the condition action. So effectively reducing action numbers by 1/3.

Thanks everyone for your input

[VictorIvanidze]

Hi @Rhys_AMSHelix,

it seems I've suggested you to use the Compose actions, do you remember?