I have worked with other workflow engines and found one important features missing in Nintex. We should have one admin console to view all the running ,closed and error workflows and should be an option to restart the error workflow from any stage.This will be very grateful for admin.

Would love to see the Create an AD User action have advanced options (just like the Query LDAP action) to specify the authentication types such as None, Secure, Encryption, SecureSocketsLayer, ReadonlyServer, Anonymous, FastBind, ServerBind. The most crucial one would be SecureSocketsLayer as more and more organisations are using LDAPS to enhance security on their environment.

We have a lot of executives who complain about seeing approved by "LazyApporval" in workflow history. This looks really bad and unprofessional. Can you please change the wording in history to "EmailApporval" rather than "LazyApproval" or allow it to be customized?

It would be great if actionable messages in task actions were customizable. We require the ability to swap out the Nintex logo with our own corporate logo.

We would also like the ability to include additional fields in the task email beyond "description and due date" and change the order fields as required.

In a nutshell, we're looking for greater flexibility. Thanks!

It would be useful to add a check box in the action for Delete item or Delete multiple items action to skip the recycle bin and deleted permanently

It would be very helpful if workflows can run a PowerShell script that is ran on a server and pass on workflow constant and variable values as well. We have in the past used a custom solution that has the same ability on multiple client projects and have proven it to be very useful, I believe it's about time for Nintex to add this as one of their supported workflow actions.

An 'Update AD Group' action similar to the existing 'Update AD User' action, which would allow the workflow to update the properties of AD groups.

Current only have set single action variable, if we need to set more variable need to add 1 by 1, and current Nintex always asks for the workflow size need to be smaller, if we have this action, we can save a lot of the workflow size.

Nintex Workflow works well with Lync 2013 however it would be great to see the product to work with Skype for Business 2015.

Some of the expected features would be to see:
- Instant message notification
- Functional Lazy Approval

please bring the new Actionable items feature to sharepoint on Prem

https://community.nintex.com/view-blog-post.jspa?blogPost=2485&utm_source=Connect&utm_medium=social-post&utm_campaign=Sep2017-ActionableMsgs&mktosrc=Social_media

Please support the SharePoint features to claim and release claim for tasks that have been assigned to a group.

Please allow the ability to specify a dynamic template location through the use of a path variable. At present, in the Document Generation workflow action, you must select a specific file as the template.

I need the ability to append random documents (from a location only known at runtime) to a generated document.

Improving the functionality of the OneDrive Upload file to work with OneDrive for Business. As seeing that business and corporations are moving out to the cloud and Office 365 spaces and use Office/OneDrive for Business being able to uploading files to OneDrive to Business would make sense versus a personal OneDrive. Especially when dealing with business documents that are being generated or created.

Need a custom action to run a powershell script

When using Update Document actions with Multiple line - Rich text. it wont generate a document with the HTML mark up. such as numbering, bullet point, bold, italic, underline etc.
Will be great if this feature applied to the Update Document action

It would be useful to be able to specify the target content type, and set metadata such as Title on the output of Document Generation.

Using the Update Item action for populating metadata after the fact has drawbacks; such as unwanted version incrementation, and its asynchronous nature causes issues when fetching propertie values immediately after update.