It definitely makes sense. So we’re actually talking here about 3 features
- the ability to chain processes (a business process is made of multiple subprocesses
- FO - requires human interaction and
- BO - unattended
- the ability of having customized input forms for FO interactions
- a tricky workaround (not elegant) would be to build those forms in an external app (VS)
- the ability of assigning FO work items to humans
We’re definitely looking into 1 and 2 on medium term (1year).
Point 3 gets more complicated and we need to decide on the direction we move on
- we do offer this functionality out of the box in Orchestrator
- we do offer and improve the way Orchestrator integrates with other workflow tools (BPM, DCM, etc) in which case the FO interaction, data inputs, etc will happen in an external system and then an UiPath (sub)process will be triggered via API.
Somehow I feel that the last option makes more sense since these systems already resides in an enterprise infrastructure. In time we could do both and offer a lightweight workflow tool in UiPath but it will take time.