👋 Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!
If you are looking for the Nintex roadmap, you can find that on Nintex Community
If you have questions about Nintex Ideas, please contact email@example.com
If you require support, please visit Nintex Customer Central
If you have a sales inquiry, please contact firstname.lastname@example.org
Our recently released and revised 'Call a workflow' action in Nintex Workflow Cloud also automates the configuration of these External start features you have mentioned when using external start to call a workflow from another workflow. To explain further, when designing what will be a child (or called) workflow, the designer can in addition to determining start variables, can now also specify what variables should be considered 'output' variables of the workflow.
When configuring the 'Call a workflow' action in the parent (or calling) workflow, the designer can choose which External start workflow from within the tenancy the action should call. Once selected, the action configuration panel renders controls for configuring the input and output variables that should be sent to and received from the called workflow.
I hope you find this information useful.
The concept/idea presented here is very different and with different opbjective than the External Start with "Output" variables. Let me try to provide more details here:
We can now call/trigger Nintex Workflow Cloud's External Start workflow today with the following payload.
This is great as the workflow once completed will be able to make a callback to the "callbackurl".
Now, as the External Start workflow only understand the payload of above (i.e. with "startData"), we can only parse the payload to take passed parameters/values into the workflow's variable(s).
If a External Start workflow besides parsing the mentioned payload, it also take the entire payload/request content into a variable. We can now make the External Start as a service endpoint for "call back" purpose. Meaning we can now parse the return of another workflow of the following content:
This External Start workflow is now handling the return/ reponse of the first External Start workflow, and process the returns the way we want it. Such as feeding that responded data to Sharepoint Online list item, etc.
Support of "callbackurl" in the return is good, but it is not easy to implement, as we need to create endpoint to receive the response from the called "External Start" workflow. Now, with this idea, we can simple turn another "External Start" workflow as the endpoint for the callback.
Hope that clarifies.