This feature would be fantastic for creating a modular environment. The passing of parameters between flows and essentially creating the ability to make functions would make flows an irreplacable asset to my work.
We are now working on this and will release it in the next couple of months.
Want the ability to Nest an Existing Flow within a Flow - Like in Logic Apps -
It will help us to split the indpendent flows and converge them into one based on the business need.
This is possible using the HTTP action and wrapping a manual request/response Flow in a custom connector so that your users can select your actions from the action list like any other action. My concern is that I quickly hit the 50 Flow limitation which does not make Flow a great platform to roll out enterprise workflows for large organisations.
Use HTTP Post/Request, similar to what's described here: https://flow.microsoft.com/en-us/blog/build-nested-flows/
Cascading of Flow into another flow will help to utilize reusability of the code.
A large piece of flow can be re utilized making this system as component based.
it would be great to have an action that would trigger another flow.
This would allow for organizing individual tasks into smaller, easier to understand flows. One task per flow, but linking multiple flows via an action that can start the next flow in the chain.
Currently, there is an action called Start Flow which many people on the forums confuse as being able to trigger a flow to start. Based on the number of people trying to use this action, there is clearly a need for this function.
Based on the number of votes on this, I would consider the solution recommended to not be sufficient. It may work, but I have tried it and been unsuccesful.
I would also add that if the HTTP action is the recommended way of doing this, it needs to be renamed.
In addition, the HTTP action pattern is not a user-friendly pattern. It is best suited to small modular actions like sending an email since it involves passing data in JSON objects that have to be built manually. This does not fulfill the no-code nature of the Business Application Platofrm. We need a method to nest a flow within a flow so that can be done easily within the UI without manually building JSON objects.
I would like to see this. It would enhance our ability to reuse flows.