The idea is:
The idea is to provide a way to publish all dependent workflows together with a main workflow.
My use case:
I have a main workflow that calls dozens of sub-workflows. This structure was chosen because the overall flow is quite large and has memory constraints.
I think it would be beneficial to add this because:
- It would make deploying new workflows much easier, since all related workflows could be published at once.
- I understand the concerns about mass-publishing, but in some cases you simply want to enable everything.
- With the current approach, you need to manually publish each workflow one by one, which is time-consuming.
Any resources to support this?
In my case, the main workflow calls 15 different sub-workflows. Sometimes, an inner workflow calls yet another one. This means I have to navigate through all 15 workflows and publish them individually.
It would be much easier if there were an option—such as a checkbox in the “Publish workflow” screen—to publish all dependent sub-workflows automatically.
Are you willing to work on this?
Unfortunately, I don’t have much knowledge about the internal implementation.