đź‘‹ 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 have questions about Nintex Ideas, please contact ideas@nintex.com
If you require support, please visit Nintex Customer Central
If you have a sales inquiry, please contact sales@nintex.com
Currently when you are testing a workflow, if you get an error or a workflow stage fails, you need to restart the full workflow. When we have Approximately 30 Tasks, with forms, and then the associalted workflow processes, this is a painful thing to test. I would be good to be able to fix the issue and restart that test workflow from where it failed with the fix in place.
Added to this would be more assistance with testing the workflow too - a view to see a progress line throught the workflow diagram (making the connection lines green for success, and the action boxes green when successfully processed, and red where it fails. And the ability to see what the values in all the variables are from the testing screen.
Further to this is in production if there are failures, you can fix the item, and restart the instance from the failed step, forcing it to use the new build. Currently if you want to do this you restart the instance from the end of the start event. This is a headache in large workflows.
We have a workflow with over 30 human-based task steps, plus the automations, and if something fails for any reason you need to restart the instance from the start. Our issue with that is that start form is used by unauthenticated users, therefore we can’t use the save for later function, so we built that function, but this is another task form further in the workflow, so if we restart the instance, any time the parents have chosen to save for later, we lose all that data they entered. And we really have no way of telling if they used save for later or not unless we trawl through the steps of the instance.
Couple this with the fact that at any given time there is 6-700 active instances running for this workflow, if an issue is discovered, we can fix the workflow, but this will not apply to that 700 active instances.