Hahaha, I just made up that name, Flow + Inception = Flowception. I refer it to the flow which help me to create another flow. Currently I am compacting my flows, merging several flows with one trigger each to single flow with the combined triggers. So a single flow can contains 5-10 triggers. To separate the logic, I have to use parallel expression. It is quite painful to select each trigger, edit, rename, copy, cancel out, create a new condition and paste the trigger, double quote it and etc.Econdoc wrote: Now I am intrigued! Where can I find Flowception?
So I just make helper flow (flowception) to trigger when selecting multi trigger flow, parse the trigger name, automatically change it to expression using == if single choice, or containsElement() if multiple triggers selected. The flow will wait until I created expression, and the automatically paste the expression and save it. Kinda confusing, but it is just automating the flow creating process. I am still perfecting it, maybe can be put into single flow only.
There is other which I use to test that 11 triggers flow. The whole triggers are time based for the range of 1 week. It is impossible I wait for 1 week to test them out. So I just create simple input dialog, parse that 11 trigger so I can test each trigger by executing it manually and choose the triggers name. Another is simple time counter, I had shared it in Parallel vs Series, where we measure the execution speed. Later, I have much better way to measure average speed per elements.