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

Other

Showing 84

Workflow settings, Workflow deletion

Is there a feature on the roadmap (e.g., under Workflow settings > Workflow publishing) that would allow specific roles or groups to have permission to delete a workflow? Background: In our current support structure, workflow stewardship falls ...
Guest 1 day ago in Nintex Automation Cloud (formerly Nintex Workflow Cloud) / Other 0

Add option to allow Alert on Failure to goes Form initiator

From a troubleshooting perspective, it would be ideal for users with Workflow Owner permissions to receive failure alerts. However, in large organizations, the form initiator is often the one most invested in the outcome of their request. It would...
Guest 1 day ago in Nintex Automation Cloud (formerly Nintex Workflow Cloud) / Other 0

Email original submitter or other user when instance fails.

When an instance fails or pauses it is currently set to only email the admin or developers. This means when someone submits a form they'll never know that it actually failed and we'd have to always keep an eye on the email and restart it. If we co...
Guest 10 days ago in Nintex Automation Cloud (formerly Nintex Workflow Cloud) / Other 0

API to pull out completed tasks

Many times, customers would like to use their own landing page for various reasons. Sometimes, it’s to incorporate the feature within their intranet portal or to use Nintex within Teams or Slack. Today, all other actions can be completed using the...
Ranjit Ramachandran 2 months ago in Nintex Automation Cloud (formerly Nintex Workflow Cloud) / Other 0 Open for voting

Rename workflow without publishing a new version

We can rename workflows by publishing a new version. It would be great if we could rename workflows without having to re-publish the workflow. Perhaps, include a Rename option in the ellipses menu on the NAC dashboard.
Kopantsho Mathafa 8 days ago in Nintex Automation Cloud (formerly Nintex Workflow Cloud) / Other 0 Open for voting

Ability to delete Instance Start Data

Currently NAC allows purging of workflow instance as a whole at workflow level. We want a way to purge (delete) Instance Start Data but still keep the Instance activities data. This allows a way to delete any business data to be stored in NAC for ...
Guest 6 months ago in Nintex Automation Cloud (formerly Nintex Workflow Cloud) / Other 0 Open for voting

Align NAC API with NAC features

NAC is being constantly improved (which is great!), nevertheless the API is not following the upgrade pace and is not really up-to-date. For example : The form Access feature that enable to filter who can trigger a form is not available from the A...
Alexandre 7 months ago in Nintex Automation Cloud (formerly Nintex Workflow Cloud) / Other 1 Started

Application tokens should not have global admin permissions by default.

any app client credential is able to access all workflows and all tasks. There should be an option to restrict this access to allow app token to access only selected workflows and action its tasks along with delegates.
Guest 15 days ago in Nintex Automation Cloud (formerly Nintex Workflow Cloud) / Other 0

Add NAC tenant ID to an email header for outgoing emails from NAC

Currently emails coming from our NAC tenant do not contain any unique identifiers that they originated form our NAC tenant. Adding the tenant ID that is unique to the customer to an email header would enhance email security on the customers side t...
Guest 2 months ago in Nintex Automation Cloud (formerly Nintex Workflow Cloud) / Other 0 Open for voting

APP client secret value should be masked after creation

after create an App under Apps and Tokens, the Client Secret value should not be viewed except for immediately after creation. Also it should have expiration data and notification prior to expiry date.
Guest about 1 month ago in Nintex Automation Cloud (formerly Nintex Workflow Cloud) / Other 0