Workflow cloud forms have very limited font and style capabilities. It is very much a necessity to have a label/title font size, input font-size on controls and a font size option on the label rather than the existing Heading 1- 6 which is very limiting.

When using "Store a file" in the SharePoint Online connector, it is not possible to assign metadata. The metadata is even required, so the file uploaded is not completed. So you must store them fileID and then update the item with the correct metadata. Would be much more convenient to let us add metadata at once!

Nintex Worklfow Cloud - Salesforce Actions (Get/Attach files) is saving documents into 'Notes and Attachments' section. It would be of more value to provide an option to save them to 'Files' section under a Salesforce Object, since 'Notes and Attachments' section is depreciating.

In the settings of the form (where we can set the title and description), having the possibility to type a category for the form would be really useful. So that the form can appear in a category in Nintex mobile app.

Hi all, the short cut keys to access variables/fields differ between the form designer and the form variable editor.

In the form designer, if I want to access a field/variable, I type [[ (two square brackets).

In the form variable editor, if I want to access a field/variable, I only need to type a single [

I reckon these should be consistent.

New page functionality is great! Wouldn't it be nice to make the pages conditionally appear based on other fields.

Currently if a xtension responds with a code other than 2xx the call is considered to be a failure.

However many APIs legitimately return a status-code other than 2xx. For example if you query a service and no results are found, many APIs return 404 - "Not Found". This is a valid response and I would like to react on this response within the workflow. Many times this would result in either creating a new record (if a query returns 404) or updating an existing record (if a query returns 200).

LOVE the side config panels for Start Event and Form Styles. Would really like the Form Rules to also be a side panel too. Toggling between tabs is time consuming.

Would really like a Time Only field. Currently the only way to obtain a time value is using a date/time field. When working with values such as start and finish times, we only need to capture time. Would be good to be able to use these in variable formulas too (e.g to calculate working hours minus breaks, etc.)

I would love to see enhancements to scheduled start. Scenarios I would like to see are:

• Every x Monday of the month
• Every x workday of the month

Regards,
Daniel

Google Drive connector only supports personal drive access. To use NWC in enterprise environment with Google Drive, Team Drives access is required

It could be useful to have delegation concept also for tasks in NWC, it should be done through the task dashboard or through API.

Delegation could be done by an administrator or by the assignee (it should be possible to disable this capability for the task assignee, like in on-prem version of Nintex Workflow)

The addition of the ServiceNow connector is HUGE for us! However, the major of usage for Nintex forms is with Call records, and/or Incidents.

I'm requesting that you add the Calls and Incidents tables to the available tables options in the ServiceNow connector configuration.

When a task is completed it would be handy to capture the JSON for debugging purposes. Alternatively if there was an action that logged all variables and their values, that would be useful too. It's possible to log all variables now but that means updating the action each time a new variable is created. If there was a "log all" action or something similar to the verbose logging that is available with Nintex on-prem this would help with debugging.

There should be bi-directional linkage between arrays containing items as object and collections in nintex.

Open API v 3.0 should be supported.

I had a workflow that failed from a form start and had no way to restart the workflow or retrieve the information that had been entered into the form. Once I fixed the error in my connections, I couldn't rerun it. I also couldn't access the initial information in the form. The data the user had entered is lost and I can't track down any information about what was submitted.

I would like to be able to take a date variable and find out the day of the week (Mon, Tue, etc.) There are times where I want to take action based on day of the week, but have no ability to do that right now.

Would be awesome to have a select option "Select All" export to CSV button. At the moment I'm having to open a failed instance in a new tab (Because if you click back on normal window you'll have to manually scroll back down to where you were) one by one at the "Instance start data" and pasting it into an Excel spreadsheet to get a better picture of why it failed.

When designing multi-page forms, it would be great to be able to add an image to the Header area for the entire form. Our main use-case for these forms to date has been external, anonymous forms to capture data back into our systems - in that case, we like to include our company logo at the top of the form. With multi-page forms, the only option I see is to add the logo to each page.

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 the supplied 'value' upon submission (in my case it would be a UID relating to records in our bespoke system).

This functionality I am after already exists within the Workflow Designer, via the values defined in the x-ntx-dynamic-values JSON vendor extension, but it does not appear to be possible within the Form Designer.