Hi there,
I have also encountered this issue migrating from Legacy over to modern Windows.
Our use case is an REFramework robot with a dynamic process layer, it is able to execute multiple different small steps/subroutines through a singular invoke activity. This works fine on legacy by setting the workflow file name/path as a variable from a config value and the input queue data.
By removing this function in modern windows, we now need to explicitly invoke 10+ hardcoded processes in a switch statement, which seems like a huge step back in terms of usability/functionality.
Are there any plans to re-integrate dynamic workflow, or a way to adjust the project.json to allow for dynamic workflow invocation within the modern windows ? @marian.platonov @alexandru