All ideas

Error handling was recently introduced. Where supported, it will cause a workflow instance to Pause instead of fails. This then gives the opportunity for the instance to be resumed at the failed step for it to try again. This is a great feature! H...

We can rename workflows by publishing a new version. It would be great if we could rename workflows without having to re-publish the workflow. Perhaps, include a Rename option in the ellipses menu on the NAC dashboard.

If we want to trigger a workflow based on SharePoint site and library events, we have to create separate workflows for each SharePoint site and library which would explode our workflow limits under license. Can we not have a way to trigger the sam...

Unauthenticated task forms are sent to external user email with a static url token. This could be compromised if someone else gets hold of the url. Can we add another level of security to send OTP to the same external email once someone tries to u...

Currently, the workflow testing log displays plain-text action names. When debugging, you have to navigate through the workflow canvas in order to find the corresponding action that has a error. This can be cumbersome when the workflow is fairly l...

Currently, the Workflow Testing log is displayed as a window that covers the workflow canvas. You cannot view the workflow and the workflow testing window at the same time - you have to close the testing window in order to see and navigate through...

I have a use case now, and have occasionally had them in the past, where it would be helpful if drafted changes to an existing workflow could be set to be automatically published to Production on a future date. I have one now that I have been aske...

It would be useful to be able to save/apply changes to a form that is not fully configured, similarly to how we can save a workflow with unconfigured actions. Having to export and re-import the form is less than optimal.

One of the top feature of K2 is SmartObjects. There is a need for something similar is Nintex to organise workflow data including startforms and taskforms variables, into some relational data and able to expose it via odata service for reporting p...

At the moment, we can only see start variables via startData api endpoint. There should be an endpoint that would expose all the variables in the workflow including task form variables and workflow variables with their latest values.