We are migrating to SharePoint 2019 on-prem and the modern layout seems to be the future.

I've attempted to use the Modern interface on some sites, but there are no Nintex modern webparts available to work with Workflows, workflow tasks, or forms, and no way to 'work around' their absence in an on-prem installation (thought there are reportedly ways around it in SPOnline).

Could Nintex please provide some Modern webparts to enable the same functionality as classic layout, in the Modern interface in on-prem SharePoint.

Nintex workflows for O365 does not have error handling feature for many actions. The typical behavior at SP2013 is that user can choose to handle errors for certain actions. In office 365, Nintex provide a flag for subset of actions. This flag determines weather action succeeded or not.

Such actions are:
1. Web Request
2. Query XML
3. Update XML
4. Create item in another site
5. Delete multiple items
6. Update multiple items

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&utmsource=Connect&utmmedium=social-post&utmcampaign=Sep2017-ActionableMsgs&mktosrc=Socialmedia

Currently there is not audit logs for track workflow changes. It would be helpful to have a functionality that would allow Administrators to monitor activities in SharePoint, Nintex Forms and Nintex Workflows. Essentially something like the Audit logs for SharePoint.

Please provide a feature to track all administrator changes like create, update, delete and publish Nintex forms and workflow.

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.

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?

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.

As start workflow option to start a workflow you can set the "value differs from the old value" option. Nintex Workflow obviously has access to this information. Within the workflow you can not load the previous value into a variable or something else. That would be nice.

Actually you have to use multiple hidden fields storing the previous value to use in for workflow porposes.

It would be great to choose whether to send a notification or not when a workflow is cancelled. Indeed, sometimes we need to cancel a workflow by using the "Terminate workflow" action or via the Nintex seb service and it is part of the normal process, it isn't an error or an unexpected behavior. That's why it could be useful to not send a notification in this case.

Currently available in a Request Approval action but not in a Flexi Task.

Auto-save while working on a Nintex Workflow would be such a good thing. Not only myself, but other developers I know have backed out of the designer before just by some random key presses and have lost his/her work. Right now the only solution is clicking "save" often, which isn't terrible, but sometimes when you are focused on the work it can easily slip one's mind.

A Workflow Action to easily select the columns to export to CSV (attach to an email notification for example) including data in Repeating Sections.

Currently I can do this manually, but very cumbersome and time consuming.

Hi there

For a long time XML was the de facto standard input notation for web service calls but there have clearly been changes to, and developments in, the available notations.

It would be really good to see some of these new input methods being supported in the web service actions in the workflow product such as JSON.

Thanks 

Some of our document approvals require a group of people to vote on a number of options (if they disagree, it goes on to another level). It would be very useful to be able to assign people to a single task with a number of options, wait for them all to respond, then have the number of votes for each option assigned to a variable.