Nintex Automation Cloud (formerly Nintex Workflow Cloud)

We want to register all users(about 20,000+) to be able to use NWC before release, but it takes so much time to do this individually from NWC dashboard. It would be great if we can do it in bulk, and if we can import/export into CSV for the checki...

Currently there are no options in NAC Start Event Forms for cascading dropdowns (distinct feature in 365 forms) when adding data list lookup controls. We have to replicate this concept by using multiple choice fields which is not ideal for more co...

Currently files that are uploaded into a Task Form within NWC cannot be added to a File variable within the workflow designer as they're held as 'Collections' vs. 'Files'. Would be great if files from Task Forms acted as files throughout the rest ...

We came across an issue I noticed while building task forms. Scenario : We have a long text field dedicated to a "history" log in a SPO list we use for a specific process. This supports the end-user with seeing a log in real-time as the reques...

It would be good if we could automatically populate a single choice Form control (in my case it would be a drop-down list) using JSON objects obtained from a custom API (maybe populate the list by using an on Form load Rule?), and have it submit t...

The Nintex gateway has been updated to include support for SQL On-premises. There is a current data type limitation where file variables in a NWC workflow are not supported to binary, image, varbinary datatype fields.It would be great to be able t...

When filtering through instances it would be helpful to filter based on workflow (ability to include or exclude) or through an instance name containing x. Would also help if you could save a filtering list view so you almost have a report

Often times, we can have very rich and full Forms that trigger a workflow. Sometimes after a flow has been submitted it may have incorrect data (this is not something that can be validated correctly or handled with rules). Example we have an onboa...

We have users accessing task forms from IOS device browsers. HTML is not rendering there as it does on desktop browsers.

In the resulting object of a Retrieve an item action, there no "Item URL" property. It's possible to recreate it with the rest of the properties but it leads to more character string actions (possible to use a component workflow for that though).