Would be very useful to have the ability to publish a workflow to both Dev and Prod, or ideally publish to Dev -> Promote to Prod.

Right now when publishing to Dev when a Prod exists overwrites the Prod with the Dev, which is far from ideal, and makes testing changes to existing workflows harder than they need to be.

Hi! Could we please have a custom confirmation once a WFC form is submitted? Thank you!

It would be great to have a more collaborative designer space within NWC, where multiple individuals could work within the same workflow at the same time and see in real-time, changes someone else makes.

Think Google Sheets or Google Docs. Not critical to have, but would be a convenient capability.

With the multi-user task, please add an ability for a user to claim the task so the other users do not need to action it.

Please add actions to the Box group that allows you to Get Folder Metadata and Set Folder metadata. We can do it for files but we cannot do it for folders without building a custom Xtension.

Please add Date Completed to the list of filter options on the instances tab. It is hard to find failed instances of long running workflows when the only filter option is started date. Please make Date Completed a filter option.

When viewing the Instances tab we cannot sort by the various fields displayed on the page. Please enable sorting for all fields (Instance name, Workflow name, Status, Date initiated, Date completed).

Allow setting of default value(s) for a Person Control in a Task Form, or allow the dynamic setting of Person Control values by Form Rule. This would be useful in cases where the Task performer needs to adjust an existing list of people. Unfortunately the old trick of using a Form Rule doesn't work here because the Value of the Person control is not available to set. Nintex Support (Case #00430175) confirms that this functionality does not yet exist and there is no current workaround.

Please do not crash my workflow in the action "Remove user from a SharePoint Group".
It is absolutely wonderful that you return an object that tells me if the removal was successful or not. That is exactly how it should be for every action.
BUT (crying sounds in the background) still the workflow crashes if the user cannot be found! See screenshot.
Please please never let workflows fail for things like this. I am sure you're going to fix this... ;-)

When I add a member to a team in MS Teams and it cannot be added for whatever reason currently the workflow bluntly crashes.
Please don't do that to us ;-) That is sooo 2020.
Can you please return an object that tells me if it was successful or not?

This is not just the case for this MS Teams connector action but it still happens in more actions. Golden rule is to never ever crash a workflow for such a reason but always return a 'success' object. Thanks!

A lot of our European form users are complaining on the Decimal and Currency fields not allowing comma as a decimal separator (the form control completely blocks entering anything but numbers and dot).

This escalates quickly from a UX issue to a process error issue when someone submits a x100 value in the field (it's really easy to not notice the comma being 'eaten' by the field, especially for users of the numeric part of standard keyboards).

It would help greatly if we could set cultureInfo or field format for value parsing on the decimal and currency fields.

Automatically place cursor in search box after clicking the X to clear the search box. This applies to the workflow and forms designers, in all search boxes.

PDF support for Image link in NWC

Could you please provide a 'Edit' link as well as a 'View all instances' link with the workflow details?
When troubleshooting a failed workflow I now have to copy the workflow name, go to the workflows list, then Ctrl-f the browser page to find the workflow in the long list of workflows and then choose 'edit' . A bit of a detour actually. See attached mockup. Thanks again!

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

in my company, we have a lot of workflows published in production with built-in nintex forms.

We need to group forms by permissions so that only specific people to access them.

For example, let's say we have HR forms, IT forms, and FINANCIAL forms. we want to publish the HR forms for HR users, IT for IT people and FINANCIAL for the accountants.

I've tried playing around with the permissions field, but it doesn't seem to impact the mobile app.

Please develop this feature

When confirming a "Delete workflow" please mention the workflow name I am about to delete.
It is so scary now to delete a workflow as the three dots on the right are veeeery far away from the workflow name on the left.
Sorry but this feels almost too simple to ask.