Ideas

Showing 115 of 2849

Copy trigger and inputs and outputs and targets automatically for all variations

Would be great if the systems would copy trigger and inputs and outputs and targets automatically for all variations as they are unlikely to change.

Sonja Burghardt over 3 years ago in Nintex Process Manager (formerly Promapp) / Process Variations 0 Open for voting

2 VOTE

Mobile Application

Before the merge of AssureSign & Nintex, AssureSign had a mobile application that was useful for mobile e-signing. Several clients have expressed the usefulness of having access to a mobile application. AssureSign is one of the larger e-sign c...

Guest over 3 years ago in Nintex eSign (formerly Nintex AssureSign) / Signing Experience 0

2 VOTE

API/Process for promoting from sandbox to prod

When Nintex AssureSign is integrated with another enterprise application, it is sometimes necessary to coordinate configuration updates between AssureSign and the enterprise application. It would be helpful to have a set of APIs for deploying conf...

Guest over 3 years ago in Nintex eSign (formerly Nintex AssureSign) / API 0

1 VOTE

Filter Available Variations by Process Group

Jonathan Butler over 1 year ago in Nintex Process Manager (formerly Promapp) / Process Variations 0 Open for voting

3 VOTE

Variations should be viewed by how they are entered

I have a process for Purchase of Goods and Services and there are different variations for the $ value required for said goods or service. When I entered the variation (and go to modify my variations), they are listed as in attachment 1 by d...

Alison about 5 years ago in Nintex Process Manager (formerly Promapp) / Process Variations 1 Open for voting

2 VOTE

Release Notes should be more in-depth

Every time there is an update to AssureSign, the Nintex AssureSign Status page (https://assuresign.status.io/) says to refer to the Release Notes page for details (https://help.nintex.com/en-US/platform/ReleaseNotes/NintexAssureSign.htm). However,...

Jenna Jentges over 3 years ago in Nintex eSign (formerly Nintex AssureSign) / Signing Experience 2 Planned

1 VOTE

Enhance HTML Formatting Options For Email Designs

When modifying Email Designs, the default syntax is Markdown. If you want to use HTML to format, you cannot also use Markdown within the HTML tags. The current workaround is to close out of HTML tags, insert Markdown formatting, then re-open HTML ...

Jenna Jentges almost 2 years ago in Nintex eSign (formerly Nintex AssureSign) / Templates 0

2 VOTE

Rest API for Resending an App

Just as there is an API to initiate an eSignature ceremony from our App, so also there should be an API to resend an email with the link for the signer to sign it. This is a requirement because either the email in the original API request was a ty...

Bhoga Pappu almost 4 years ago in Nintex eSign (formerly Nintex AssureSign) / API 0 Open for voting

2 VOTE

Clarify the digital signature terms and agreement step. I though i was agreeing to the form with out having seen it.

Several people tested the form and had the same impression that i had. on the first page where you check the box to agree to the terms and services. I thought I was agreeing to the full form for which i had not seen or read yet. It was confusing, ...

Guest almost 4 years ago in Nintex eSign (formerly Nintex AssureSign) / Signing Experience 0 Open for voting

1 VOTE

Prevent the auto-publication of all variations when global process title is changed.

This can be exploited as a means to bypass the approval workflow, any unpublished changes will be published when this change is made.

Tim C about 2 years ago in Nintex Process Manager (formerly Promapp) / Process Variations 0 Open for voting

Please enter your email address

FILTER BY CATEGORY