asked on June 30, 2020
The ability to invoke Workflows from inside the repository has opened a lot of doors. But I think the integration can be tightened even further.
- It would be great if the client applications had the ability to display a dialog box that prompts the user for additional input when they are invoked. Those inputs can then be directly passed as input parameters to workflow. Right now, any such input first needs to be encoded into the selected entry, then retrieved as field values by workflow. This is not only clunky, it's also not always appropriate.
- Workflows can be invoked from the client applications, but the only thing the user sees is a success message saying the workflow started. What about its results? What if it needs to provide some kind of feedback to the user, such as "Selected entry has successfully been routed to <path>" (where <path>" is a hyperlink) or "something went wrong: <error message>"?
0
0