Time execution of sub workflows within one big workflow

Hi all,

I have created one bigger workflow that brings together a few sub workflows in the end of the main workflow as the sub workflows need to be merged. In each of the sub-workflows I have components integrated whose parameters can be adjusted by the user on the WebPortal. Problem is just that when I execute the workflow on the WebPortal the components that the user goes through are quite mixed between the sub workflows. So what I’d like is that the user first selects all options he has within one sub-worklow and then the components of the next sub-workflow appear in the WebPortal.
Apparently it is not possible to change the order of the components to appear in the WebPortal as they get populated as executed in the workflow. But since my components are quite independant of each other due to the fact that they just get merged in the end of the workflow, I was wondering whether there is at least an option to time the execution of the workflow so that I can determine which sub-workflow to execute first so that the respective components also appear in the right order on the WebPortal.
Hope I explained my problem here properly, otherwise please feel free to ask.

Thanks a lot in advance and merry Christmas!

BR,

Tim

Just a thought, what if you were to:

  1. get the user to enter what screens they want to adjust. Let’s say they choose screens A, B and D
  2. have a mapping table of sorts in terms of how those screens should be ordered, e.g. A is first, D is second and B is third, as well as their locations for step #4
  3. Sort the workfows based on the mapping table order (which may be where you use the timer to dictate order, offline)
  4. then you run a call workflow within a table row to variable loop, where each call workflow location is indicated by the table row and based on the mapping table above?

Theoretically it will call each workflow in the order you had defined in the mapping table.

Hope this helps with an idea at least! Would love to see the outcome!

1 Like

I may have mis-read the question. The timer node could be set to deeper granularity levels, so it goes within each subcomponent. The Node ID would identify which component each node belongs to. This way you can take the timer output and parse out the time for each subcomponent. The steps I provided could be used after, or you could specifically lay out the sequence of subcomponents you need.

1 Like

Hi @supersharp,

thanks for the quick reply and apologies for my late one now as I was on vacation between Christmas and New Year’s.
Unfortunately I have to admit that I can hardly follow your proposal, it sounds good though. :wink:
Would you be able to come up with a short and easy exemplary workflow, that would help a lot! I tried to find the timer node you mentioned but I could only find the timer info node which does not look like the one that helps here?!
Thanks a lot in advance!

BR,

Tim

Have you tried implementing a wait node and delay the excecution of certain subworkflows?
br

1 Like

Hi,

I solved it in a completely different way now, but your ideas, also the one from @Daniel_Weikert helped a lot as inspiration, thanks a lot!

BR,

Tim

1 Like

congratulations.
Maybe you can shed some light on what your solution looks like for others as well
br