When you send an email in Nintex Workflow Cloud, all the emails will be delivered by <nintex@workflowcloud.com> and we are looking to change this email with one of our own email addresses/domains < noreply@mydomain.com>.

While we can see Instance Start Data, it is almost impossible to relate fields on a Start Form back to the start instance data as the naming convention for Instance Start Data from the form just shows the control type. Would be great if the controls variable name was used in the Start Data to make it easier to review that data.

Add Access to Deployment Type from with in the workflow

In a cloud based Nintex Start form make the user context of an authenticated user available in the form designer.

Currently the user context is only available in the workflow not in the form. With the user context available in the form designer we can use the user context in form rules or primarily as a filter in the new data lookup control.

Please consider purchasing a static ip for your cloud service.

see https://azure.microsoft.com/en-in/updates/static-public-ip-addresses-available-for-azure-virtual-machines/

To open up our databases/api's to Nintex to access we will need to add the full Dynamic Azure Ip range. ( The list is very long ).

see
https://community.nintex.com/t5/How-To-s/Nintex-Online-Services-IP-Addresses-to-Whitelist/ta-p/83587

It would be very difficult to enter and maintain as the list changes in most instances.

Thanks

Could you add connections to monday.com?

It would be nice to be able to create a shorten URL for the Forms in Workflow Cloud just like your able to do with Live Forms on SharePoint on Prem. We have already had a few request from stakeholders of some Forms and Workflows we have already created on this.

Would be great if there was some sort of off-the-shelf payment gateway setup to allow for online payments within a Nintex Form. Would be even more awesome if we could manipulate variables such as cost price via form rules.

Hey guys, could we have a few more options in the Format date action? e.g. ddd mmm yyyy. i.e. combinations that have full names of days and months both in dd mm order and mm dd order. Cheers

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.

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!

I lost a more than a day of work, hours!
and no automatic save feature....

This alone will cause me not to go with Nintex as a solution. I can't afford this.
I've testes over 8 solutions this month, and all offer auto save.
The mighty Nintex does not....

Please add the ability to add an image link when drafting the email body of send the email. We have a need to incorporate into the email signature the organisation's Logo and link to the organisation's web site but the functionality is not there on Nintex Workflow Cloud whilst Nintex Workflow O365 and On Premise has this ability

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

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.

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).

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

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.