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

Clear

Ideas

    Showing 239 of 2948

    Process Owner and Expert

    Currently you can only have 1 expert and owner. You should be able to have at least 2 experts, as some processes are cross functional so it's useful to know who to ask. Additionally you should be able to have a 'department' or group as the owner a...
    Guest almost 4 years ago in Nintex Process Manager (formerly Promapp) / Process Creation & Editing 3 Open for voting

    Support for AssureSign Child Accounts in Salesforce DocGen Integration

    In our organization, we use AssureSign child accounts to represent our different business entities under a single parent account. Each child account is used by a distinct Salesforce org. Current limitation: The Nintex DocGen integration in Salesfo...
    Boris THOMAS 8 months ago in Nintex eSign (formerly Nintex AssureSign) / Integrations (Salesforce, Dynamics 365 & more) 0

    Make filling in Inputs/Outputs mandatory

    A lot of the time processes are published without any Input/Triggers and Outputs/Targets being specified. The Promaster should be able to enforce that (e.g. through an admin setting) for at least 1 Input and at least 1 Output to be specified for a...
    Evgenios Efthymiou over 1 year ago in Nintex Process Manager (formerly Promapp) / Process Creation & Editing 2 Open for voting

    Move Triggers and Inputs section on Procedure to the top

    Wouldn't it make sense for the 'Triggers and Inputs' section to be at the top rather than at the end of the procedure. They are supposed to support the user experience by providing information on what triggers the process yet most users would not ...
    Guest about 4 years ago in Nintex Process Manager (formerly Promapp) / Process Creation & Editing 5 Open for voting

    Case sensitive glossary

    It would be good to have a Glossary that is case sensitive. Currently IT (Information Technology) is being tagged every time we use the word 'it'.
    Guest almost 6 years ago in Nintex Process Manager (formerly Promapp) / Process Creation & Editing 5 Not Planned

    Saving Processes and changes

    It would be great if there was an autosave function OR a prompt to save in the event that a user inadvertently went to close Promapp while there was a process underway
    Janine Branson over 3 years ago in Nintex Process Manager (formerly Promapp) / Process Creation & Editing 3 Open for voting

    Save signature for reuse

    Save signature for subsequent envelope signature. the business process results in hundreds of envelopes directed to executive for signature monthly, each requires creating and saving signature (time and clicks). Making signature saved to a profile...
    Renee Gonzalez’ Fong almost 2 years ago in Nintex eSign (formerly Nintex AssureSign) / Signing Experience 0

    Feedback on 10th December Update moving info to Process Attributes dropdown

    Re release 4.12.5.0 - December 10 2024. The Change Log now only displays about 3 items, previously it displayed up to 20, this has created a LOT more work when trying to find an item in the change log. Previously we could also search in the change...
    Guest about 1 year ago in Nintex Process Manager (formerly Promapp) / Process Creation & Editing 0 Not Planned

    Control which users/roles/privileges can see cost information on processes

    Is it possible to make some processes private or restricted so only certain people can view it. Our users are concerned that if they add the financial details to specific roles, especially roles where only one person is employed such as a COO, tho...
    Guest over 2 years ago in Nintex Process Manager (formerly Promapp) / Process Creation & Editing / User Management 0 Open for voting

    Allow "Step Completion Date" and "Signing Step" to be available in Webhook merge fields

    The merge fields exist, but do not populate in web hooks. This causes confusion, and they would be useful to allow customers to track state. Support ticket: 00730027
    James Tyzack 2 months ago in Nintex eSign (formerly Nintex AssureSign) / API 0