All ideas

In the NAC-Workflow-Design, editing the form of a "Assign a task to multiple users"-Action, we currently cannot translate outcomes. We can translate all other controls on the form but not the outcomes. This is a problem in a multi language environ...

It would be great to be able to test individual actions in the workflow designer without needing to run the workflow test. An example of this would be if you build an API call using the Call a Web Service action, it would be good to be able to tes...

All Fields have the possiblity to add a default value. But not for Data Lookup. Please insert here also a Default Value Field.

When building large, complicated workflows, it would be handy to have a comments option displayed on the workflow designer page, without the need to open the right-hand context panel. Use case for this would be to use as a reminder of what a step ...

Now that run status 'pause' exists, please add a Pause total box along with the other total boxes (Running, Completed, Failed...) in Workflow Tracking.

A right hand panel in the workflow designer than opens up with a large markdown text editor. This could be used to store any kind of documentation. I have seen customer workflows, and done so myself, use the workflow description, but this is not t...

Currently, you can only hard code text using the editor; however, the business requires the ability to use variables within the header and footer.

File attachments should be able to be renamed prior to saving file to SharePoint. To save the file then query the file and then rename the file is very inefficient. Even pushing the file rename to an in-form variable.

We would like to see an ability for authenticated Nintex users to go to a form that is active and be able to write a comment that can be seen by all parties involved with the request. This comment should then be included in all subsequent forms do...

We expect to have many connections in our tenant and need the ability to sort and filter by URL/Connection information. Having to look at connections individually one-by-one is not efficient/practical.