Skip to Main Content
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 2577

Create alert when a problem occurs in a Published workflow

I ran into a bug where the Then/Else options in some of the Rules in my published workflow (multiple forms) were removed. I only happened to run across the error when I went to make a couple of minor changes to wording in the forms. I opened a cas...

Don't leave the form when 'Apply Changes' is clicked and change name of 'Cancel' button

Saving a form frequently is good practice. I save the form I am working on quite often because I don't want to lose the work I put into it in case I get pulled away during the form creation process. It is annoying and a waste of time close the for...

Automatically populate Process Experts and Process Owners from processes in system

It would be really handy (and really easy to manage) if Promapp was able to automatically populate the roles of Process Experts and Process Owners from the processes where they are referenced. For example, if I'm the Process Owner for Process X, I...
Guest over 3 years ago in Nintex Process Manager (formerly Promapp) / General / User Management 2 Open for voting

Process Acknowledgement - wording - "published" rather than "changed" when published by Promaster

As Promaster when publishing processes, process changes to acknowledge states "process has been changed by [promaster name]", it would be preferable to state "process has been published by [promaster name]", I find employees think I am changing th...
Jocelyn Wallace over 4 years ago in Nintex Process Manager (formerly Promapp) / Process Review & Approval 2 Open for voting

Improved content of BPMN diagrams

The current level of detail/content contained within the BPMN diagrams exported from Process Discovery is not fit for purpose as it does not contain any details around what a user has actually done i.e. left mouse click on 'View Claim' button. Thi...
Daniel Orman almost 2 years ago in Nintex Process Discovery / Output (BPMN, CSV, Word) 1

Able to run a report for a particular champion, detailing all the Groups and processes linked to the individual for ease of updating

Able to run a report for a particular champion, detailing all the Groups and Processes linked to the individual for ease of updating individuals when they change roles/teams or no longer in the business
Guest almost 5 years ago in Nintex Process Manager (formerly Promapp) / Reporting 2 Under Review

Add a View Only Privilege Type

It would be good to have a 4th privilege option added to make the limiting of process creation easier to manage. Currently to have a view only user type you need to switch on the "limit process creation to PM, BA and PC" option in config which the...
Sam about 3 years ago in Nintex Process Manager (formerly Promapp) / User Management 1 Open for voting

Generate proper Documents (Word etc.)

Generate proper Documents like Word, PDF etc. based on a Template. (Like the DocGen but for K2 Five)
Lavinia Mogin almost 2 years ago in Nintex Automation On-Prem (formerly K2 Five) / Other 0

User Feedback

Our users need a way to submit feedback about wizards they run with Nintex Kryon Attended Automation. If there was simply a button that can be accessed from the tool that launches a google form - and pulls in the name of the wizard - and the user ...
Guest about 1 year ago in Nintex RPA (formerly Nintex Kryon RPA) / Attended bots 0 Open for voting

Task Form Link Variable

It would be great to have a default variable in the workflow the workflow that stores the link to a task form. Right now I grab these through the API connections but it would be much more intuitive and clean on the developer end if we didn't need ...