Some use case needs to interact with multiple application and in such condition each application has its own way to handle the transaction and we can’t build one workflow for every application with there n no validations and conditions. it is always better to have separate workflow depending on which application we are going to work with current transaction and call only that application workflow.
It was just use case i have explain , but i really not understood why UiPath has removed this functionality from Invoke Workflow Activity. If you could add this feature asap that will really makes developer life successful.
Seems the problem is with Windows compatiblity. I tested on another machine with Studio 2022.10.7 with both Windows (Legacy) & Windows - it’s working with Windows (Legacy) but not on Windows.
They are not supported in windows/cross-platform due to compilation. We are actively working to remove this limitation and most likely in 23.6 we will remove this limitation.
@alexandru but i want to understand why does it support windows legacy but not windows? and may i know when the newest version going to launch and how come i know that version will does contain this update?
