To have a Pause action that executes based on the action configuration rather than relies on the SharePoint Timer Service (at least 5 minutes)

We have C-level employees approving workflows via LazyApproval. Unfortunately this has a negative context and we are getting pushback by our workflow implementers to see if we can adjust this label.

I see that the emails can be modified, but we are still seeing remnants of that verbage in our approval history.

Is there a way I can modify this? Thank you.

In Office 365 - Start a task process It would be nice to the ability to set the Importance of an email notification. For example, when I send a reminder that a task is overdue I would like to set the Importance to High vs normal.

Please correct the XML Parser in Nintex actions.

When you have double spaces in a XML tag, the XML is not valid and crashes (betwen "FFB_RestaurantRoomLkp" and />) :

<Eq><FieldRef Name="FFB_RestaurantRoomLkp" /><Value Type="Lookup">RDC du 33 Kléber</Value></Eq>

Note : Uservoice trims the double space in the comment.
Tested : I used this XML in a Web Service Call and also to filter a view on a form.
Instead of parsing the XML correctly, an exception is raised :
Name cannot begin with the ' ' character, hexadecimal value 0xA0. Line 1, position 43.

Call Web Service and Web Request actions should have built in support for mixed authentication including Windows ADFS Claims auth. Due to how ADFS Claims requires tokens for authentication, the current out of the box action does not support this.

The option to allow delegation in flexi tasks is one which developers spend time thinking about. When they choose not to allow delegation there is a reason for it. Long term delegation overrides this decision and delegates these tasks even though they should not allow delegation.
Please update long term delegation to only do so where the flexi task (or other action) specifically allows this.

Include the ability to upload multiple documents to an envelope.

Scenario: The signer wants to see all supporting documents before applying their signature to the cover sheet.

The CRM actions included with Nintex Workflow and available through the Nintex Live Catalog should be able to support Single Sign-On authentication through systems such as ADFS.

When configuring a Task action within a State Machine branch, you should be able to place Change State actions within the Approve or Reject branches of the Flexi Task action while the task behavior is configured for "All must agree on a specific outcome".

Currently this causes a looping of task action, and the Change State actions must be moved outside of the task outcome branches to accomplish the expected behavior.

Currently the store data action only allows one value to be stored. If want to store multiple values to later retrieve need to use the action multiple times. Can Store data action be updated to allow multiple values?

Due to the negative connotation of "lazy" approval, I recommend either renaming the feature, "Easy Approval," or allowing the static text in email notifications to be modified.

Thank you for considering this idea.

Update an item in another site collection action, similiar to Create an item in another site

Can use in the "LookUp - Runtime Function - Calculated Valuel" with list in other site O365 - Sharepoint 365 - Ninitex form and workflow 365

With the recently release Nintex Forms enterprise feature to print to PDF, it would be great to access this functionality via a Nintex Workflow.
As an example a Nintex Workflow could take a Nintex Form and generate a PDF file to be created in a library.

The DocuSign Download Document Workflow action only downloads the first template in Envelope. The action should download all documents within Envelope.

From documents in document libraries, to documents that are attached to list items and other scenarios, the need to read the contents of a document into Base64 format seems to come up fairly regularly.

The data could then be used to call the Lists.asmx web service, specifically, the AddAttachment and attach it to another item.

It would also be used to send to any number of other Line of Business systems, as Base64 seems to be the standard.

An action that does that in Nintex Workflow would be ideal for this.

First of all, Exchange Connector for Nintex Workflow requires .Net 2.0 which is long overdue in replacement.

It should be recompiled using a newer .net Version.

That is before mentioning the support for Exchange 2016, which also lacks. Exchange 2016 has been out since 1. Oct 2015, which is 1,5 years ago, and still no support?

Get support for Exchange 2016 and a newer Connector, which does not depend on .Net 2.0 and old versions.

Nintex Workflow can not set a date column to a blank or NULL value. Please make this avaialble for consistency reasons.

When you are having issues with workflows like we are currently it would be helpful if the workflow errored subject had the site and/or workflow title appended to the end.. that way you can focus attention on certain sites with most issues, and spot trends in failures simply by keeping the emails..