528 results found
-
Document.value variable for Bulk Send
Currently, the document.value variable is not able to be utilized for bulk send. This would allow for higher usage and efficiency.
11 votes -
Enable Smart Content from Fields as well as Variables
I know that Smart Content can be autopopulated based upon the value of a variable token within a document, but I would love to see the same Smart Content effect based upon the value of a field as well. Almost a mix between Smart Content and Conditional Rules combined where I would like to be able to have the value of a field in document actually trigger the Smart Content. An example in a document is a simple checkbox that pops open Smart Content if checked, versus only being able to enable the Smart Content from a variable token.
68 votesHi. We aren’t planning on building this into our feature set at this point in time since it doesn’t fit into our current product roadmap. Please keep upvoting this idea so we can keep considering it every time we work on our roadmap.
Should you come across any other ideas that suit your business needs, don’t hesitate to give them an upvote!
-
If a recipient chooses one specific field, remove the ability for them to sign other associated fields
If a recipient chooses one specific field, such as initials one field on the document, then they would no longer be able to fill in other fields that are associated. Maybe the other fields would then be grayed out. Basically, they would have to choose between signing one field or the other field, and the one they do not choose will no longer be accessible. This can technically be done with radio buttons and drop-down, however, we would like to see this capability with other fields such as the initial field.
3 votes -
Ability to pick/change colors of fillable fields (customization, branding, etc.)
This idea is for use cases not addressed by the new color palette for fillable fields (distinct colors for each recipient and distinguishability for individuals with color blindness).
5 votes -
Ability to send a document twice to the same email (signing order)
For example, one signer has to take action twice (separately) within the same document. To demonstrate this example, here is the signing order: Signer 1 > Signer 2 > Signer 1 > Signer 3.
Info/signatures are required from Signer 1 and 2 prior to Signer 1 being able to fill out their second portion of the document before Signer 3 receives it. I haven't had success in developing this yet, as I have been unable to successfully have one signer able to receive the document twice in the workflow.7 votes -
Add clickwrap, click-accept agreement functionality
Within the Signature Block, add a type property, with a new option of click-wrap, that would simply be a checkbox control vs the legacy signature control. If the click-wrap signature type is selected, have two additional options (a) click-wrap-text, defaults to "I Agree", and (b) click-wrap-url. If the click-wrap-url is not empty then the url is displayed above and must be clicked on to enable the "I Agree" checkbox control. Clicking on the url should show the url content in a separate window or tab, as to not disrupt the originating signing page, taking into considerations both desktop and…
9 votes -
Mass Update Fields - Required/Optional and Font Size
Apply field properties to all selected fields including:
- required/optional
- font size
Align all selected fields (left, middle right).
22 votes -
Add a new Document-level Variable for Documented-Completed-Date
When a Document is Signed/Completed, it would be great to have a Document-level variable that represents the signed/completed Date, that could be used in our new TItles by Variables feature. Similarly, when payment gateways are involved, the paid date may be a valuable option as well. Currently, these dates are listed as available Document variables. also, add them to the get document details API endpoint and Webhook payloads to promote automations
3 votes -
Footer/Header - Ability to add signature fields, text fields.
The ability to add fields on footer such as text field or signature fields.
5 votes -
Variable for Template.Name
A system variable that will automatically populate the template name, useful when creating documents via CRM integrations
5 votes -
variable for current date
variable for current date
5 votes -
Card details field - option to add more fields to fill in additional card information
Card details field - option to add more fields to fill in additional card information
2 votes -
Field - Lock position / anchor
Option to anchor/lock fields position in order for it not be drag accidentally or misplaced it on a contact/documents ETC.
5 votes -
Link fields from different documents
The ability to link fields from different documents together.
2 votes -
an option to make the document sequence numbering on per client basis
Make the document auto-numbering on per client basis.
2 votes -
Multiple layers of conditional fields
We need multiple levels of conditional fields, but currently there is only one. Meaning if a set of radio buttons is required based on a selection of radio buttons, those secondary radio buttons cannot themselves require additional fields. There are many documents with this kind of layering so it's important. For example, many financial institutions have complicated forms where we have to select one option and then within that option we have to select one option and within that option we have to enter information into fields.
4 votes -
Multiple Users in a Field
Ability to assign multiple users in 1 field
3 votes -
copy and paste fields/variables from one template to a new template
copy and paste fields/variables from one template to a new template
3 votes -
Document completion date variable
Document completion date variable
2 votes -
hide/conceal information in variables
hide/conceal information in variables if recipients have not yet signed
2 votes
- Don't see your idea?