Feature Request: Flow as step #3510
Description
Showing every single task (and in the case of update_dependencies, many subtasks) as individual steps in MetaDeploy can be overwhelming and confusing for more complex installs.
We have some pre and post install processes that string together a bunch very small OOTB tasks together to do something. We put these in a subflow that must be run as one chunk (and would love to make the flow optional as well). We could write our own task but that is a lot more work than using the provided ones in a subflow. It is also unclear if or how I can call other tasks from inside a custom task so I don't reinvent the wheel ( like doing an mdapi zip deploy/retrieve, something not easily available in simple-salesforce)
Right now, customers will see a bunch of tasks in MetaDeploy like retrieve config, "copy file", edit config, then deploy. Really it is one unit of work "backup customizations".
I can see a couple of ways this could be handled in MetaDeploy:
- Allow ui_options to "hide", but still run, tasks. This would have logging issues so probably not practical.
- Allow a flow to be shown and run as a single step in the plan (including ui_options like name and is_required)
- Allow a flow to be marked "collapsed" and have groups/sections of tasks collapsed by default but can be expanded to see the details.
- Documentation on how to write custom tasks and call standard tasks from my custom one so that I can put it all into a single custom task.