eSign

I need some assistance determining if we are Title II compliant with disabilities such as hearing impaired, etc. Is AssureSign capable of reading the document which we send to students?

We have been successfully retrieving a list of templates using the DocumentNOW endpoint below for quite some time:https://www.assuresign.net/api/documentnow/v3.7/templatesHowever, starting this morning the request is returning the following error:Forbidden exception: “The current user is not authorized to perform the requested action.”Nothing has changed on our end with respect to authentication, permissions, or the integration configuration.Have there been any recent API updates, permission changes, or other changes to the DocumentNOW API that could cause this behavior?Any guidance you can provide would be appreciated. 

In AssureSign, is there a setting for envelope expiry notifications to be sent to the signer when an envelope was sent via SMS?

Is it possible to delete documents to remove them entirely instead of cancelling and having notifications flow to the signatories that have declined to sign the document?

Starting two days ago, in the AssureSign Date input field, when selecting the Date Format "Date in YYYY/MM/DD format with current date prefill, and after sending for signature, then the actual date input screen displays "Invalid Value" even when entering the date in the specified format, preventing me from proceeding. Even if I populate MM/DD/YYYY and others for this case, all showed “Invalid value”.If I chouse other formats such as “Date in MM/DD/YYYY format with current date prefill” and others work without issues.Only format YYYY/MM/DD style doesn’t work. However, in Japan, the YYYY/MM/DD format is standard, and using other formats causes confusion with dates, making the YYYY/MM/DD format essential for our use. 

Dear all,I am working on integrating Nintex AssureSign with Power Apps with a flow in the CA1 environment and have run into a persistent authentication issue.Environment / Setup Environment: https://ca1.assuresign.net API endpoint: POST /api/documentnow/v3.7/authentication/credentials Account Context: acb8d12c-3389-447e-a6b8-620cf18f9e5c API User created in account.assuresign.net, scoped to Specific Environment → https://ca1.assuresign.net/ API Key active, not expired CA1 Settings → DocumentNOW® Integration → Default File Retrieval Credential set to the same API user What I’ve Tried Body variations:   { "username": "don.wang@elections.ca_Lqq4s0Ue", "key": "************", "sessionLength": 60 } Added accountContext in body (and also tested removing it) Added header:   x-assuresign-account-context: acb8d12c-3389-447e-a6b8-620cf18f9e5c Headers:   Content-Type: application/json Accept: application/json Tested with Power Automate HTTP action and PowerShell (Invoke-RestMe

Dear all,I was able to create an API User in account.assuresign.com but the API User cannot be used at ca1.assuresign.com. I spent a lot time to figure this out. However, it seems we cannot create the API Users in ca1.assuresign.com. I loggged in ca1.assuresign.com as an administrator with my regular email. I then tried to create a new user, but it failed with this message:ErrorWe are currently experiencing technical difficulties and were unable to complete the requested action. Technical support has been notified and will investigate this problem shortly. We apologize for any inconvenience this may cause.Error Code: VTP33This may be unstandable, but I cannot find we can create an API user at ca1.assuresing.com. Could you share some lights here.Thanks,Don

I have a AssureSign template going out to customers to complete. It has several jotblocks worth of information that I would like to use elsewhere in a workflow (for example, Address). While I can get the completed form as a pdf, I’m not seeing how to get the jotblock’s information. 

I notice  when using the “Signer Verification Required”  option within “ Static Links” while using “ Enable Static Link “ only the second signer   is being sent a verification code.  Does anyone know a work around to fixing this?

When I open a document to sign in AssureSign. The header and footer each takes a significant amount of space/real estate.  This left little real estate for the actual document to be viewed.  How can I expand this document viewer part. The document viewer has a style/class but I’m not sure if and how I can update this style/class? or is there a setting that I can change in AssureSign which will allow me to have a full-page view of a document to be signed?

Good afternoon  everyone,I notice  when using the “Signer Verification Required”  option within “ Static Links” while using “ Enable Static Link “ only the second signer   is being sent a verification code.  Does anyone know a work around to fixing this?  

Hello,In my environment, I have eSign/AssureSign connected to SALESFORCE. It works very well and the Nintex AssureSign Envelope is connected to the Quote (In SALESFORCE) and in eSign environment, I have the Envelope and the eSign Document. I want to allow the cancellation of the already launched eSign process. The Nintex AssureSign Envelope have a status “In Progress”. I imagine that I can create a button to order to change the status of the Nintex AssureSign Envelope (in SALESFORCE). But I want also the inform the eSign Environment (the eSign Document and/or the eSign Envelope). Do you have any ideas for this Business Process ?

I am attempting to reuse a simple template more than once with different values for a Fixed Text JotBlock via the Submit API.  I would like to have multiple pages of the template attached to the root template with different input data per attachment via the template.  When I attempt to send a second new version of the template all of the send input values from the initial template are displayed in every subsequent use of the template even thought the sent values are different from the initial use of the template.  I am including a simple version of the JSON data that is being sent below as an example.Basically, I am attempting to include the same template multiple times with varying values for the fixed text JotBlock to show as additional pages.I am also including a sample of the C# code that is sending the request.The end result is that the values from the first use of the template are used for all additional uses regardless of what is sent.

I’m looking for a way to mask the value entered into a text jotblock but only to the signer. The options for masking JotBlocks make it to where the completed documents show up with the mask, but that means that in the instance of a credit card number our accounting department can’t run the credit card.I was pointed in the direction of dynamic JotBlocks but I’m new to them so I’m not even sure where to begin. Is there a way to have the document be sent to our company without the mask but the signer be sent the document with the mask?

In this blog I am going to go through how to set a character limit for a text jotblock in Nintex eSign.  By limiting the amount if text you allow the user to input into the jotblock you can assure that when the document is generated after signing all the text that the signer input into that jotblock will be visible in the document.Let take a look at how to configure this.  Open up the template in Nintex eSign you wish to configure this for, find the jotblock and open up the settings for that jotblock by clicking on the gear icon. After opening the settings window, click on the display tab and then under the validators dropdown select custom.    Now we need to enter the regular expression that will be used to set the character limit in the jotblock and the validation message when that limit is reached.  In this example the regular expression that is being applied will limit the characters in the jotblock to 10 or less.  When that limit is reached the user will receive the validation mes

I have a webhook that is called upon Envelop Completion.  This webhook simply calls an endpoint on a service that I am hosting.  I am successfully receiving the calls but the base64 coming from the Binary Data fields ([Completed Document], [Original Document], etc) are always blank.If I manually test the webhook then I successfully receive a generic AssureSign document (yeah!).  But I am unable to figure out why this does not work on completed envelops and their signed documents are not transferring.Does anyone have any ideas or suggestions?

I need the ability to split section on a quote into multiple docs. Would anyone know if this can be done? When creating a document via Salesforce?

Hello,I’m facing a problem with custom settings and API user for the sending of emails from AssureSign.I use these settings :In the AssureSign Configuration :   On AssureSign, the API users are created :   The Custom Settings, in Salesforce, are set this way. There is my own user account, the System Administrator and the Commercial Profiles.   The “system administrator” profile field “AssureSign_Context_User” is empty.The “commercial” profile field “AssureSign_Context_User” is the email address of the Integration User. My User’s field “AssureSign_Context_user” is the email address of the Integration User.With my account which has an Admin profile, when I try to send the document to AssureSign, it works.With a standard “commercial” account, when clicking on the “Send to AssureSign” button, I get this error :The error says: “An error has occurred. (InternalError)Include this Error Id if you contact support: e2e731b0-b6fc-461e-bfa0-55e9b67ccc2” Can you help ?Best RegardsMarc

we tried the below code on the dynamic jotblock {{!##{Name:"SignerDate",SignatoryEmail:“Signer1”,InputType:“signatory”,SignatoryInputType:“Prefill”,ValidationType:“DateDDMMYYYY_CurrentDatePrefill”,FontName:“TimesNewRoman”,FontSize:“Twelve”,FieldType:“Typed”,Height:“0.025”,Width:“0.25”}##!}}this is working fine. Whenever we change the date format “MMDDYYY” its failed. {{!##{Name:"SignerDate",SignatoryEmail:“Signer1”,InputType:“signatory”,SignatoryInputType:“Prefill”,ValidationType:“DateMMDDYYYY_CurrentDatePrefill”,FontName:“TimesNewRoman”,FontSize:“Twelve”,FieldType:“Typed”,Height:“0.025”,Width:“0.25”}##!}} Did anyone face the same issue?

Hello Everyone,We have a usecase where after a user signs a nintex document, we send an email with a document link that the user can click on to view the signed document. Is there any api available in assureSign that could provide a link to the signed document?I attempted to utilise envelope/envelopeId/signingLinks, but it appears that after the document is signed, the signing url cannot be obtained again.Error Message :{"details": "The specified envelope 'xxxxxxxxxxx' was previously completed so signing is no longer available.","messageType": "error"}

Hi, how do I resend for signature if the taxpayer passed the KBA and the Souse did not?

We have a legacy on-premise AssureSign Server installation.  We are using the 2.0.0.24 version of the AssureSign solution for CRM installed on a CRM 9.1.7 on-premise server.  I am in the process of converting from Web Classic forms to the Unified Interface and was hoping to find information regarding compatibility and any known issues with that version running on Unified Client Interface (UCI). Any related information would be most appreciated! 

The number of recipients needed for esign varies from document to document.  I am using rows to represent the recipient(s) and they populate as expected.  Issue I have is that the eSign tag, {{_es_signer_1__signature}}, doesn’t coincide with the recipient if I have more than 3.  Adding only Signer _1 and Signer_2 results in signer 2 being prompted to sign for the 3rd recipient.  Adding Signer _3 and _4, as shown on the attached, repeats the signature for each recipient.I am looking to have the proper signature line show up IF I have a 3rd (or 4th, or 5th) recipient. Thanks for any help.

I am trying to successfully submit an envelope via the API and correctly add webhooks that ping my service for any sort of updates.Problems I am having:Not sure if I should use webhookNotifications or adhocWebHooks Documentation & Schema for adhocWebHooks missing in the AssureSign API docs, I am shooting in the dark by trying properties and hoping one will match I want a workflow where I can send emails to multiple singers and they can sign in parallel, however, I want to receive a webhook notification every time one of the signers signs, including their name, email and any arbitrary value I want to put for reference purposes (where can I get these values?) What is step index? The order that I create steps on? I’ve been trying all day to properly set up a REST call to the AS API for setting up my workflow but it seems possible. Any help is appreciated. This is one of the errors I receive, the model isn’t specified anywhere in the documentation. 

Does Nintex allowed 2 signers on the same documents? If so, how to go about it?