Archive: eSign Knowledge Articles

IssueDocument fails to transmit document, as listed in the history of the envelope/document. Error CodeNintex AssureSign servers will report all errors, from all locations, including as shared from your servers in the document history. Because it's relevant to the final document and the correctness of the history of collecting the signatures and the full interactions of the document for legal reasons, you may see something that references your servers as a failure in the document history, as in the error listed as example below:ResolutionWe suggest that you reach out to your IT team to take a look at the server logs to discover what was going on so they can help you resolve this issue. Nintex AssureSign does not have access to these, so it must be done by them.

TopicThis video details user management within eSign, as effectively managing users is a crucial responsibility of an eSign administrator. 

It is possible to perform some operations on data for use inrendering of fixed text JotBlocks passing of data in DocumentTRAK designs application of data in email designsSimple ConcatenationSimple concatenation is supported when merge fields are used alone or with some fixed text. In this case, merge fields are delimited by square brackets. For example[UserFullName] sent [Document Name]could output something likeJohn Doe sent Contract 1467859Advanced Data ManipulationAdvanced formatting and data manipulation requires the use of javascript. Basic javascript operations are supported, as well as the use of some added libraries and AssureSign specific objects and functions.Javascript must be contained within code delimiting blocks[{ }]Single statements that return a value implicitly may be included. For example, the following javascript will print the current year from the server to the document:[{new Date().getFullYear()}]when implemented in fixed text: Simple concatenation may also be co

TopicThis video details how non-signable addendums in Simple Setup work within eSign. This can be useful in specific scenarios where you would like to include additional files or supplementary materials in digital form. 

The built-in DocumentTRAK web hook for SharePoint onliune is available starting with version 6.33 of AssureSign.When the DocumentTRAK hook fires, the hook authenticates with your SharePoint credentials and saves the document being passed in the library you specify. This can be configured based on special classic template parameters passed from a Submit of a document through our solution for Dynamics CRM, but this hook may be configured on any other AssureSign template you design.To configure the hook, from the Administration and Settings page, select DocumentTRAK and continue to Notification Administration.  Select the Document Transmission tab and click the "Add Document Transmission" button.  Select to "Embed in a WebHook" and pick the SharePoint design.Enter:a unique name for your webhook. the Username and Password for a user of your SharePoint online instance that has rights to save files in the library you specify. the SharePoint site URL, which may resolve to a specific subsite,

If a DocumentTRAK web notification is detected as not having been successful based on standard http status codes, it will be reattempted up to 4 times for no longer than 24 hours.  Each re-attempt will be progressively delayed.   Notifications that fail based on your endpoint returning a response that does not match the expected result you have set in the "Webhook Response Validation Tests" section of your notification will not be re-attempted.  Such results that otherwise result in a 200 success status code are not eligible for automated re-attempts.Multiple failures of the same design will cause all re-attempts of the design to be paused, but the first attempt of a given DocumentTRAK design on any new envelope will not be delayed.  When any new instance of a given DocumentTRAK design that is failing repeatedly is determined to have been successfully sent, any queued re-attempts will be released to be tried again.You may configure emails to be sent upon notification failure to the ema

TopicExport a Simple Setup template InstructionsGo to Simple Setup templates Click the name of the template Click Export Additional Information  Related Links  

To cancel a document, you may log into your AssureSign instance and find the document that should no longer be signed by using Envelope Search in the Reports section.  Once you open the detail report view of the envelope you may select "Delete this envelope" under the "Envelope Tasks" section of the report. This option will only be available if the document is in a state that allows cancellation.  A DocumentNOW Cancel method (SOAP method) is also available for cancelling documents via API using the DocumentNOW V2 APIs.  A REST method /envelopes/{envelopeID}/cancel is available using the DocumentNOW V3 APIs.

The Help page will provide you with access to:  This knowledge base DocumentNOW Integration Help: Provides help with the DocumentNOW interface, and provides quick access to WSDL AssureSign policies and Terms of Use It is possible to customize the Help page using the Custom Help and Support setting in order to hide or display some custom information on a per-account basis.

TopicWhen using the AssureSign delivery option for Nintex Drawloop, after making changes to an AssureSign template, such as updating the notifications or making changes to Webhooks, the changes are not reflected when sending a document out for signing. InstructionsDrawloop currently caches the template settings at the time the delivery option was configured. By editing the delivery option and reselecting the template from AssureSign, the new template configuration will be reflected when documents are sent for signing from Drawloop. Additional Information  Related Links  

TopicCan the next steps in a workflow be based on the outcome of the ‘Get a Signature’ action?  InstructionsYes. The outcome of the signing process is stored in the returned workflow object variable. Inside of this object the ‘Envelope Status’ value can be used with actions like ‘Branch by Condition’ to help direct the flow of the workflow.  Additional Information  Related Links  

TopicWhen configuring a template in AssureSign, what webhooks are needed for use with Nintex Workflow Cloud?  InstructionsYou do not need to configure any webhooks to use a template with the ‘Get a Signature’ action. Webhooks will be created automatically by the workflow as needed.  Additional Information  Related Links  

Reports can be accessed by users that have permission to view document reports. To access reports, click on the “View Reports” button after login to your AssureSign account. 

To update your billing information, you can contact your account representative by sending an email to support@nintex.com  

Using AssureSign Electronic Signature Technology, you have the ability to have documents securely signed electronically. How do I get a document signed?The easiest way to try it out is to use our Simple Setup tool.  Upload your Word or PDF document that needs to be signed, give us contact information for your signers, and drag and drop JotBlocks where you need the document signed.  When you are done telling us the details about your document, your signatory will be emailed easy-to-follow directions about how to sign the document using a computer mouse and keyboard, or a mobile device. You will receive an email notifying you that the document has been signed. A digitized copy is maintained on file with AssureSign for a period of time.  More advanced operations are possible through integration of your systems with our DocumentNOW services, through designing Templates, through configuring AssureSign to send secure communications to remote services with updates and documents via Documen

Yes, conditional logic is supported within the Simple Setup template. Learn more about using conditional logic here.

Document senders can allow someone else to sign on a signer's behalf with configuration options in Simple Setup.  For a full walkthrough of how to configure an envelope which will allow signers to delegate signing responsibilities, please see our article on Signer Delegation.

Signer attachments are a feature that allows signers to upload their own documents and images to be attached to the final completed document. For example, a signer can use their cell phone to take a picture of their ID if a document requires photo ID, or a signer can upload a digital copy of their utility bill to provide proof of residence. SetupSigner attachments can be created either in a template or a document. They can also be created dynamically when using the API or embedded into text tags in the document.To create a signer attachment in a template or in classic document setup, first create all of your normal JotBlocks and define all of your signatories. When you are at the JotBlock assignment step in the workflow setup, a section appears for each signatory to create signer attachments. Once all of your signer attachments have been created, you must assign them to a signing step along with your other JotBlocks.  In the new Simple Setup envelope, you specify attachments to be uplo

Your AssureSign account comes with certain built in “Roles” that help to assign security restrictions and grant rights based on common patterns. A good place to start is to review the restrictions placed on each of the default system roles provided to your account, and build your own roles as needed to allow fast creation of users without compromising security. Note: If at all possible, do not assign all users to the Administrator role. This should be a reserved role just as in your organization’s IT Department. Depending on the size of your AssureSign user group, you may in fact only need one Administrator. In particular, the following user settings are important to consider:Document management - account documentsWhen enabled, a user will have administrative rights over other’s documents within their account as if they were the creator. This can be beneficial for supervisors or managers who may need to access and administer documents owned by their staff, but consider setting to “Deny

In many cases email addresses work well to uniquely identify users or signers because only a single person actually uses that email address. However, there are cases where more than one person may use a shared email address.  The challenge in these cases is that AssureSign - like many web services - requires users and signers to use unique email addresses. Here is a simple workaround:Instead of directly entering the email address (e.g. name@domain), an email address "comment" may be added to uniquely identify the signer (e.g. name(comment)@domain). We strip this extra comment portion out of the email address when sending email.For example: If John and Jane Doe share the email address jdoe@example.com, you can distinguish between them by using something like the following: jdoe(John)@example.com and jdoe(Jane)@example.com. For best results we recommend including only letters and numbers (no symbols) in the comment portion of the email address.

Accounts are a mechanism for bundling users and settings into discrete units. Accounts may be configured to mirror your corporate structure, or accounts may be configured to delineate sales units that should be branded uniquely. Each sub-account in the accounts section may inherit your own account's settings (the parent account), or you may select which specific settings may be uniquely configured. Users are assigned to an account and they will operate under the permissions that that account allows.Create a new account Click on New and enter the account name Assign an Account Group (created in Account Groups) If you would like to populate the account settings from a template, select an account template beneath "Automatically copy account settings from an account template?" Configure an administrator user account, which will be the first active user within the account Save the accountNote: As an administrator creating a sub-account, you may configure the settings and users. However, in

Account – Accounts are set up to allow you to manage your AssureSign settings and documents. An account provides you with the ability to set up users, configure branding, and manage your document and template workflow. An administrator of an account can setup up sub-accounts for various departments within a company. Sub-account – is a child account from the parent account. The sub-account can copy the same branding and configuration from the parent account or could have a different configuration and branding. 

A number of downloadable tools for desktop, mobile devices, or plug-ins for various platforms are available here.*Link to be updated

Yes, AssureSign supports sending SMS text messages to signers.  SMS for document and envelope communications is an add-on feature.  Please contact support if you are interested in finding out more. AssureSign SMS message content may not be altered, due to the constraints of the length of SMS messages and the need to include a URL in the content.   An invitation to sign will include the following content: Document to sign from [Company Name]: [Link - Document Signing]. Reply STOP to unsubscribe.[Company Name] is replaced with the name of your company as defined in your account settings. The SMS message sent for document or envelope complete events isSigned document from [Company Name]: [Link - Final Document]. Reply STOP to unsubscribe.Click here to see how SMS is configured on one time document submissions.Click here to see how SMS is configured on document templates.Click here to see how SMS is configured on envelope templates. AssureSign customers using SMS services are responsible f

An administrator role can be changed under the user settings within your account. Change the role from administrator to one of the two.