Archive: eSign Knowledge Articles

eSign can recognize and use Microsoft Word documents (doc, docx) to create new Templates and Documents. All Microsoft Word documents are converted to the PDF format.Compatibility IssuesUnfortunately, the conversion to PDF does not always produce results identical to those seen in Word. However, a few tweaks can help with the process:Page Wrapping and Line Breaks Often, a document needs certain content to show on certain pages. For instance, the terms of a contract are on the first page, and the signature is on the second page. If the terms of the contract only take up half of the first page, it's possible to "push" content to the second page by pressing "Enter" repeatedly and creating many empty lines. This practice can cause issues with the conversion process. Instead, the document should use Page Breaks to separate the content into multiple pages. Font Embedding Documents that use unconventional fonts should always embed those fonts within the document. This allows the conversion pro

After, the signer has completed the signing process, the signer is receiving notifications (follow-up/reminder) to complete the signing of the documents. Typically, what is happening when a signer says they are receiving pre-expiration warning emails when they've already completed the documents, is that they were sent more than one envelope. The best way to check this is to navigate to "View Reports" and then click on "Envelope Search". You will want to select "Switch to Advanced View". Adjust the dates as needed, and then fill in the "Signatory Name" field before submitting the search. This will pull up the envelopes that were sent to that signer within the dates selected.  You may cancel any additional envelopes submitted.

Envelope addendums (also known as envelope attachments) are non-signable files attached to an envelope. These items do not have to be documents; they can be images, short videos, compressed files or anything else. Valid file types include: doc, docx, htm, html, jpeg, jpg, odt, pdf, png, rtf, tif, and tiff. Signers are able to download & view the addendums during the signing process. SetupWeb SetupEnvelope addendums can be created when you are using the new document envelope interface by clicking "Review and Send", navigating to the Envelope Addendums section and attaching the addendum files. APIEnvelope addendums can be created when using the DocumentNOW V2 CreateEnvelope operation (SOAP method).   They may be created when using the DocumentNOW V3 /submit and /submit/prepare methods.

The ListEnvelopeTemplates operation makes it possible to provide a menu or list of available envelope templates available for integration to the AssureSign user who is querying. In this way, it will not be necessary to have knowledge of the AssureSign envelope template ID in order to pre-configure an envelope to make use of envelope notifications defined in an envelope template. The ListEnvelopeTemplates operation will return a list of envelope template IDs (and descriptions) from which an appropriate envelope template ID can be selected and used to automate the creation of envelope notifications when creating a new envelope using an envelope creation operation.It is also possible to enter information into a Tag field when creating envelope templates for integration purposes from within the AssureSign administrative application; the value of the Tag on a particular envelope template will be returned and could possibly be used to help create a mapping or filtering mechanism in a CRM or

The ListEnvelopeDocuments operation may be used to retrievea list of all the documents contained ina document envelope. This operation can be useful for retrieving the Documentid and AuthToken for all documents in an envelope for use in subsequent DocumentNOW calls.The ListEnvelopeDocuments operation requires knowledge of the following:The Envelopeld of the envelope to cancel (this is returned as an element in the returned XML from an enveloper creation operation)The AuthToken of the envelope to cancel (this is returned as an element in the returned XML from enveloper creation operation)The AssureSign account Contextldentifier (this is exposed in the AssureSign administrative application account settings and serves to provide some security to the transaction)Sample XMLThe SOAP Action header isThe returned result will include the Envelopeld along with a Documents element that contains an array of all the documents in the envelope.Sample response XML is presented here: The ListEnvelopeDo

Continuous polling of open envelope status via calls to CheckEnvelopeStatus is not scalable, and is considered poor design.  Appropriate handling for ensuring you have the most up to date status is to perform a DocumentTRAK  web hook operation on envelope life cycle events. The CheckEnvelopeStatus operation is used to query the current status of an envelope (for example, whether or not the envelope is completed). The returned status information will include the current status of the envelope and the complete history of the envelope. In addition, the response will also include the status and history of each document contained within the envelope.The CheckEnvelopeStatus operation requires knowledge of the following:The EnvelopeId of the envelope to cancel (this is returned as an element in the returned XML from an envelope creation operation) The AuthToken of the envelope to cancel (this is returned as an element in the returned XML from an envelope creation operation) The AssureSign acc

The GetSigningLinks operation allows you to query for the signing links to present to signatories on a document or envelope. This method should be used if you are presenting links to signing sessions yourself (sometimes referred to as Immediate Presentment  rather than via AssureSign emails.A typical mechanism used to find the correct link for a specific signer is to match either the signer's email address or mobile phone to the SignatoryEmail or SignatoryMobilePhone values of a returned SigningLink element.The GetSigningLinks operation requires knowledge of the following:the AssureSign account ContextIdentifier (this is exposed in the AssureSign administrative application account settings and serves to provide some security to the transaction) Either, document or envelope identifiers: for a document the DocumentId of the document to be signed (this is returned as an element in the returned XML from a document submission operation) the AuthToken of the document to be signed (this is

 Follow these steps to configure the AssureSign for Salesforce Lightning solution to work with any custom object.Adding A Lookup Field For The Custom ObjectTo add a lookup field for the custom object, click the Settings icon, then click Setup.  Next, in the Quick Find menu, search for Objects, then click Object Manager. Click the blue hyperlink of the AssureSign Envelope object. Note: It is critical the relationship is created from AssureSign Envelope rather than from the custom object to AssureSign Envelope.  Click Fields and Relationships in the left hand panel: Click New in the center of the page, next to the Quick Find header.For Data type, select Lookup Relationship: Click Next.For Related To: select the name of your custom object: Click Next.Click into Field Name to prepopulate the field name, and add a Description and Help Text if you wish.  Note the Field API name of the field.  You will need this, and your custom object's API name in the latter half of this help set.Click Next

Sending An EnvelopeIn order to send an envelope through the AssureSign for Salesforce Lightning configuration, first navigate to where the entity the AssureSign configuration has been added. Next, open the record of the client who will be the recipient of the envelope. On the AssureSign for Salesforce Lightning integration, click New:  Populate the values on the Select Template screen and click Next: Select a Template: Select the name of the Simple Setup Template from your AssureSign account you wish to use for the envelopeEnvelope Name: This will pre-populate with the envelope name given to the template in the AssureSign environment, but is editable if needed. Populate the Values on the Provide Data screen and click Next.  Required sender input fields will be denoted by a red star at the beginning of the field name.  Note: These fields will match the Sender Inputs you have setup for your AssureSign template.  Review the values entered on the previous screen on the Review screen.  Clic

Using Built In DocumentTRAK Web Hooks And Document TransmissionsA webhook is a push notification from AssureSign to another system when a specific envelope stage occurs. A DocumentTRAK Document Transmission sends the completed document to another system when a specific envelope stage occurs.  To update records in Salesforce with audit history, collected information from a signer, or a completed document, a webhook is required.  To configure a webhook, from the AssureSign Administration page, in the left hand tree select DocumentTRAK and continue to Notification Administration:  Note the tabs in the top center of the page.  To configure a web hook, follow the instruction for web hooks. To configure a document transmission, follow the instructions for document transmissions.  Note: if you choose to use either of these options, you must also enable this in the global settings of the AssureSign for Lightning object in Salesforce. Configuring a Web Hook for Salesforce LightningTo configure

In order for information entered by signers to pass from jotblocks to Salesforce or from Salesforce to pre-fill signer jotblocks, AssureSign Data Mapping must be configured. AssureSign provides support for bi-directional data mapping. This allows:Use of data from Salesforce entity fields to automatically populate the sender inputs for an AssureSign template. Use of signer provided data from an AssureSign envelope to update fields on a Salesforce entity after signing is complete.Navigating To The Item Data Mapping For AssureSign For Salesforce LightningFirst, regardless of if you want information to pass from Salesforce fields to Assuresign, or from AssureSign jotblocks into Salesforce, or both, you will need to navigate to the AssureSign Data Mapping Object in Salesforce.In Salesforce, click the App Menu and search for "AssureSign Data Mapping".  Then, click AssureSign Data Mapping under Items:  Next, choose if you are Mapping Data from Fields on a Salesforce Entity to Sender Inputs on

Getting StartedAssureSign for Salesforce Lightning uses Simple Setup templates.Installing AssureSign For Salesforce LightningNote: AssureSign for Salesforce Lightning solution can be installed without effecting prior installations.  As a separate object with separate naming conventions, it will not interfere with or modify any existing AssureSign configuration you may have in your Salesforce environment. The package for the current version can be installed from the Salesforce  AppExchange. Select that you want to Install for All Users:  You will then be prompted to approve 3rd party access.  Select to grant access to AssureSign's websites, and continue. You may also selectively choose only account.assuresign.net and the "Site URL" (NA1, WWW, SB, CA1 or EU1) where your organization is hosted:  To determine your Site URL in the AssureSign portal you can go to Administration and then Settings and it will be located under the Account Information heading on the row titled "Site URL".    Onc

Adding An Additional ConfigurationTo add an additional configuration, from the AssureSign Lightning Setup object, click New under AssureSign Configuration List: Next, fill in the required information for the Configuration prompt:  Login Base URL:  For most accounts, this will be https://account.assuresign.netAPI Username: The API Username created by following the Creating API Users processAPI Key: The API Key created by following the Creating API Users processMapping user method: Choose "Use Salesforce Email" if the email address the user will be logging in with will match their AssureSign username.  Choose "Use AssureSign Email" to specify an AssureSign user that all users using the configuration will authenticate as, such as a service account. Once the above fields are populated, click Authenticate If multiple accounts are available to the API user/username, you may be prompted to choose an environment.  Select the applicable environment from the drop down menu, and click Next:  On t

In this video, learn the basics of starting with JotBlocks in Nintex eSign, which allows you to create data capture fields in your documents for e-signature processing and handling. 

TopicIn this video, learn the basics of getting started with DocumentTRAK webhooks in eSign, which allows you to send communications using triggered events within your template.  

IssueI'm not able to delete my own envelopes; how do I do this? ResolutionIn your Administration Configuration Settings area of the AssureSign Portal, you will need to ensure that the "Allow Users to Delete Documents?" setting is set to Yes.   Once that's been set, you will then see Delete this Envelope? option in the Envelope History: Once you click that link, you will then be prompted once more to ensure that you're certain you want this envelope deleted: 

TopicThis video explores administrator permissions and their functions within eSign. As an administrator, you can edit or change administrative permissions for you and your users within your account. 

TopicIn this video, learn how to create a basic Template and send an envelope for signing. These are the core functions of eSign and will become familiar processes to all users.

TopicThis video mini-series looks at Nintex eSign from start to finish. This article contains the following videos to get you working in the system, sending documents, and signing. These videos offer a basic overview of logging in, password recovery, home screen, basic navigation, template creation, sending an envelope, and administrator permissions. Videos  

TopicIn this video, learn how to log into Nintex eSign. This allows you to access your account, select your Nintex eSign environment, and change accounts if you have multiple accounts. 

API Users are managed in your account settings on account.assuresign.net. You must be an administrator for all your AssureSign environments in order to create and edit these settings.To create an API User you enter:a unique Username: this is not an AssureSign user or email address (although you may enter the username in the form of an email).  When the username is saved it will be validated to ensure it is unique. API user scope: choices are User: you will select a user from AssureSign users in your account Environment: you will select from your environments. If you do not have a sandbox account, you will have only one environment. Organization: the API user may operate on behalf of all your users in all your AssureSign environments. an Expiration date for the user When you save the API user you will be shown the API Key.It is important you copy this information and keep it secure. AssureSign does not save the API Key and it will not be displayed after the interface is closed.You ma

STEPS FOR SENDING WITH A TEMPLATEEnsure you have an API user and are able to get the token. In your REST coding interface, use endpoint, ensuring you've altered the items in italics to match your organization's settings:  yourASdomainhere/api/documentnow/versionnumberhere/submit/ An example would be: sb.assuresign.net/api/documentnow/v3.7/submit/   Set up your template in the Simple Setup User Interface. Anything you want to pass into the template should be created as a Sender Input AND mapped to the correct locations (Edit Envelope/Edit Document). Take note of the names of the Sender Inputs you’ve created, as that will be the name part of the name/value pair in the API call. Example Sender Inputs:  Example mapping into location for Envelope:  Example for mapping into location for Signatory:  Collect your Template ID:    Now that the Sender Inputs have been mapped to the correct locations in the template and you have your Template ID, we’re ready to populate this into the API call.

IssueI have a large task that needs to be completed, like multiple documents or users being moved into or out of a subaccount, special reporting requests, or other large data moving requests.ResolutionThis is typically a Statement of Work (SOW) and you will need to work with your Account Manager to assist with this process.  There may be a charge involved, but you should work closely with your Account Manager to determine this!