Nintex Ideas

đź‘‹ Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!


If you have questions about Nintex Ideas, please contact ideas@nintex.com

If you require support, please visit Nintex Customer Central

If you have a sales inquiry, please contact sales@nintex.com

ADD A NEW IDEA

All ideas

Showing 2453 of 2453

Google Maps API; Allow restricting search results by country

Allow designers to limit the restrictions of the Google Maps API in the Address field form to a specific country.Google Maps API allows this with the "components=country:<code>" parameter in the URL. https://developers.google.com/maps/docume...
Guest 6 months ago in Nintex Automation Cloud (formerly Nintex Workflow Cloud) / Form Designer 0

Add support for Disabled/Deleted users for the ADFS Legacy Provider via SyncEngine

Currently the LegacyProvider which handles ADFS/LDAP only supports adding users as 'enabled'. The SyncEngine does not react to users in the LegacyProvider who set to 'disabled' or 'deleted' thus disabled users do not get disabled in the SyncEngine...
Guest about 1 year ago in Nintex Automation On-Prem (formerly K2 Five) / Identity 0

File variable support in Nintex Gateway for SQL On-premises

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...
Gavin Adams about 3 years ago in Nintex Automation Cloud (formerly Nintex Workflow Cloud) / Connectors 1 Under Review

Support non-OK status-code in xtensions

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 ...
Guest over 5 years ago in Nintex Automation Cloud (formerly Nintex Workflow Cloud) / Xtensions 5 Already Exists

Improve error logs

When an error occurs, the description lacks context making it very difficult to troubleshoot the problem. As an example, failing to convert to int from a string should also include the string that we were expecting it to be an int instead of [Text...
Guest over 1 year ago in Nintex Automation Cloud (formerly Nintex Workflow Cloud) / Workflow Designer 0 Open for voting

Task Responder name in Assign a task to multiple user first response outcome

In the current object output for the Assign a task to multiple users both in the task responses collection and in the first response object there is the 'Task Responder' text variable. This is the email of the user that completed the task. Frequen...
Gavin Adams about 2 years ago in Nintex Automation Cloud (formerly Nintex Workflow Cloud) / Workflow Designer 3 Not Planned

Separate Failed and Terminated in Reports

The workflow instances report includes a column for "unsuccessful instances". This includes workflows that that failed or were terminated. This information should be broken out into two different values since there is a workflow action to terminat...
Guest about 3 years ago in Nintex Insights 0 Open for voting

"Update Password" option in Setup Manager

Currently, in order to update the K2 service account password you must choose the "Configure" option. "Configure" touches many parts of K2 that are unnecessary for a password change and can unintentionally alter various environment settings. Addit...
EmilyK over 2 years ago in Nintex Automation On-Prem (formerly K2 Five) / Other 0

Log Who Manually Started a Published Bot

Currently, the botflow instance details do not contain the Nintex user that manually triggered a botflow to run. This detail is important for audit logging capabilities.
Guest over 2 years ago in Nintex RPA LE 0

It would be nice in NAC to be able to edit previously submitted form data in instances that Fail or Terminate, either in the Table or Code when looking in Instances run or Edit the Form Start Data so that something can be corrected before resubmitting a workflow instance that had failed or needed to be terminated for some reason.

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...
Tye 6 months ago in Nintex Automation Cloud (formerly Nintex Workflow Cloud) / Runtime 1 Already Exists