HomeGuides :: SignatureBridge for DocuSignPrinter Friendly Version

Guides :: SignatureBridge for DocuSign

1. SignatureBridge Setup in DocuSign and NetDocuments

1.1. How to create an account and link it to DocuSign

Configuration:

Step 1: Navigate to SignatureBridge and click Sign Up: https://signaturebridge.trumpetinc.com

Step 2: Select the button to login to DocuSign. Input Admin DocuSign credentials in the provided log in fields, or select Company Login if you have one and follow the steps to log in.

  • Note 1: If you input credentials that are NOT admin creds then you will encounter an error. You will need to open a new tab, log in to DocuSign as the creds you attempted to use and then immediately log out. Go back to SignatureBridge Signup page and start again, it should be reset.
  • Note 2: To ensure a consistent experience for your company and end-users, use a company-wide DocuSign account in which your end-users are members of versus an individual/personal DocuSign account. See System Requirements


Step 3: Now you need to Configure SignatureBridge to your NetDocuments account.

Subscription Number status: When you create this account, you will automatically be granted access for 30 days through a trial license. Functionality will expire at that time unless a yearly subscription is purchased through the Trumpet Sales team. If you purchase SignatureBridge, please allow 1-2 business days for your account to represent your subscription correctly. 

...

1.2. How to Configure SignatureBridge within NetDocuments

Now that your SignatureBridge account is created and linked with your DocuSign account, you'll need to enable the Send To integration within your NetDocuments account.  Here's a video showing the steps:  Signature Bridge - Connect NetDocuments to SignatureBridge

Note: You will need admin credentials for your NetDocuments account to proceed. You must use the admin credentials in order for all users to have access to the SignatureBridge integration.

Step 1: Navigate to NetDocuments and log in using your admin credentials.

 

Step 2: Click “Admin” in the top right hand corner of NetDocuments.


 

Step 3: Click on the cabinet link (each cabinet will have to be configured separately).
Note: if the cabinet name is not a hyperlink then you probably do not have cabinet administration privileges.

 

 

 

Step 4: In the top left corner click on the link that says “Integrate external applications”.

 

 

Step 5: Check the box for Trumpet SignatureBridge, then “Save”, found at the bottom of the screen. Note: The default application is set for the United States NetDocuments Vault and a standard Docusign Account.  If you need to send documents to a DocuSign Demo account or an international account, please scroll below to the "Special Instructions" section for additional information.

 

Special Instructions: If you do not see the Send To command in your list OR if you need to send your documents to a DocuSign Demo account, click on the link in the top right corner that says “Add unpublished app” and enter the appropriate code:

NetDocuments VaultDocuSign TypeApp ID
US  United StatesDocusign AP-FHJNVBJ7
US  United States Docusign Demo AP-K5BW5JM4
AU  AustraliaDocusign AP-LCI18TSI
AU  Australia Docusign Demo AP-DZO0GZF1 
EU  EuropeanDocusign AP-PHGEQSQN
EU  EuropeanDocusign Demo AP-6UXO7EK4


Step 6:
Repeat steps 1-5 with all cabinets that will need access to SignatureBridge.

After these steps have been completed, SignatureBridge will be available to ALL* NetDocuments users within the cabinets you configured.

*At this time, we are not aware of any method for restricting users to Send To commands. That would be controlled by permissions settings within NetDocuments. Reach out to their support for information or to submit feature requests.

...

1.3. Settings - How to Receive Final Copies of Signed Documents

Background

There are fours settings that determine how SignatureBridge will upload your signed documents into NetDocuments once they are completed. Settings can be found within your SignatureBridge portal. You must be a DocuSign Admin in order to make these changes.

Once in your portal, click on the name in the upper right-hand corner and select "Account Info".


You'll see ON/OFF switched for four different settings:



You must have at LEAST one of these two settings enabled:

Save Envelope PDF
Save Versions

You may have both enabled if desired. Here are description of what each setting does:

Save Envelope PDF

For a video describing this functionality, see:  SignatureBridge Settings

When the Save Envelope PDF setting is enabled it means that SignatureBridge will create and file (within NetDocuments) a PDF containing the full contents of the DocuSign Envelope. It will be filed in the same location as the document you sent to DocuSign. If you send multiple documents from different locations, it will choose the first document that is contained in the package and file in that location. This Envelope PDF will also use NetDocuments "Linking" feature to link itself to each of the included documents requiring signature (it will NOT link to documents that did not receive a signature field in DocuSign). This PDF will contain all documents that you sent from NetDocuments and any additional that were uploaded separately from your desktop or network.

The Envelope PDF will be saved into NetDocuments as soon as your DocuSign Envelope is sent to its recipients (in other words, it happens on the very first sync) and it will be marked as “Checked Out”. Original documents containing signature fields will also be marked as checked out within NetDocuments. The Envelope PDF will be updated each time the DocuSign Envelope is changed or signed.

When all signatures have been received and the Envelope is completed is DocuSign, the PDF will be "Checked In" and it will have the Signature Certificate appended to the end of the document.

The Envelope PDF is named after the DocuSign Envelope Subject and is also identified with the tag [DocuSign — Signed].



Save Versions

For a video describing these settings see:  SignatureBridge Settings

When the Save Versions is enabled it means that SignatureBridge will save the completed/signed copy of the original document, in PDF format, as a new version of the original document that was sent to DocuSign.

So if you send a single Word document for signature then the final, signed, copy will check back in to NetDocuments as a new version and it will be in PDF version. This PDF document will become the new official version for that file.

*This will NOT capture any documents that were uploaded manually into the Envelope from your desktop or network.

If you send multiple documents from NetDocuments into a single Envelope, then any document containing a signature field in the Envelope will receive a new version once the full Envelope is signed. Each document will receive it's own version, which contains only that documents and it's signatures. It will not contain the other documents in the Envelope.

The Signature Certificate generated by DocuSign will be attached to the PDF via NetDocuments "Attachments".



Version Lock Signed Documents

When the Version Lock Signed Documents is enabled it means that SignatureBridge will save the completed/signed copy of the original document, in PDF format, as a Locked Version of the PDF file in NetDocuments.




Show Envelope Confirmation

This setting opens a dialog within SignatureBridge after you send your envelope within DocuSign to confirm that it was sent successfully.


...

1.4. Sending Your First Document - Approve Integration

Approve Integration with NetDocuments and DocuSign

Now that you've a) created a SignatureBridge account, and configured your NetDocuments account to allow the SignatureBridge Send To application you're ready to send your first document. There are still a couple one-time steps to complete your setup.

1) Right click on a document in NetDocs and select Send To Application

2) You will pass through the SignatureBridge portal as it directs you to DocuSign. Select DocuSign to proceed to log in and integrate the application.

Input your DocuSign Username and Password then, on the next frame hit Accept to allow Trumpet SignatureBridge to integrate. (Note: you may not be prompted to enter a username and password if you've already logged in to DocuSign in your browser in another tab)

3) Once you accept the DocuSign integration you'll need to do the same for NetDocuments. You should now see this one time prompt. Select Allow:

Now it will navigate you all the way in to DocuSign and you can send your document! Proceed to the next chapter in this guide for more information!

Tip: If you ever want or need to revoke these accesses, our FAQs have articles for revoking access in NetDocuments and DocuSign.

...

2. How to Use SignatureBridge with NetDocuments

2.1. How to Send a Document for Signature

Using SignatureBridge is as easy as knocking on the front door to a house. SignatureBridge walks you to DocuShare and knocks on their door. DocuShare opens the door and lets you in. Once your document is sent through DocuSign, SignatureBridge walks you back to Netdocuments and the exchange is complete.  Here's a video showing you how it works:

SignatureBridge- How to Use

 

Step 1: Select the document(s) you wish to send for signature, RIGHT click and select “Send to application”. Alternatively, in the document details, you can select More/Group Options > Send to application.

 

Step 2: NetDocuments will pop up a window (keep an eye out to make sure your browser lets the pop up open). The documents you selected will appear in the “Marked Documents”. Now click on the blue hyperlink “Trumpet SignatureBridge”.

  • Note: If you realize you’ve selected the wrong document then you will need to hit “Clear List” then “Close” and reselect your documents.

 

Step 3: SignatureBridge will launch and ask you how you will be logging in to DocuSign. Choose the appropriate selection and proceed to log in to DocuSign with your regular credentials (as opposed to earlier having to use admin logins). Now you are in DocuSign and an Envelope has been prepared with the documents you’ve selected.

ALERT: If you upload additional documents through this screen, then they will NOT be individually filed or tracked in your NetDocuments, however, they will be combined in the final Envelope, which will be filed. 

 

Step 4: Add recipients, their role in the signature process (needs to sign, receive copy, etc) and any personal notes that you may want. Once complete, go to the very top right corner and select Next >.

 

Step 5: Now the documents have been sent! SignatureBridge will display the Envelope details. Select “View in NetDocuments” to take you back to NetDocuments and view all related documents to that Envelope. Or if you’d like to navigate to DocuSign then you can select “View in DocuSign”. “Synchronize” allows you to manually tell SigBridge to check to see if there were any changes made to the document.

 

What happens now?

Within NetDocuments you can now see that the documents are checked out and [Awaiting Signature]. This status will change as signers sign the document. You will also see that there is a new document which holds the entire Envelope, including any additional documents you added through DocuSign. This will also appear as checked out, and this is where the signed documents will be saved. You will find that your original documents are Related to this Envelope document.

Once all required signatures have been fulfilled, SignatureBridge will check the document back in as signed and you will receive an email from Docusign alerting you. Note that SignatureBridge synchronizes automatically every 30 minutes, or manually at any time through the portal. As the documents are checked in, you will find that their label will change to say [Signed], but you will need to open the Envelope document to see the signed copies.

Note: If you need to access the SignatureBridge portal to manually synchronize your docs or view pending documents in general you can access your portal by returning to your SignatureBridge portal: https://signaturebridge.trumpetinc.com

...

2.2. I've Sent My Documents, Now What?

So you've sent some documents to DocuSign using SignatureBridge. Essentially, all we have to do now is wait for the designated people to sign, but maybe you have some questions about how this is going to work. If so then read on!


Waiting for Signature

When one or more documents are sent to DocuSign, and signature fields have been applied, they will be marked as "Checked Out" within NetDocuments, and you'll see a tab in the description that says "Awaiting X Signature", X being the number of signatures it's waiting on. That number will decrease as people sign, until ultimately all signatures are fulfilled.

The documents marked as checked out will also be "Related" to a new document that SignatureBridge will create and file into NetDocuments. We call this new document the Envelope Document, and it contains ALL of the documents from that DocuSign Envelope that you created (even if something was added to the Envelope that isn't in NetDocs). This Envelope Document will be checked out as well and will received the signed copies once pending signatures are fulfilled. If you'd like to learn more about this document then review the article called: How Does The SignatureBridge Envelope Document Work?

Notice above how I specified "and signature fields have been applied". Well, let's say you have a cover sheet that is technically it's own document which you included in the Envelope, but you don't put a signature field on it. In a case like that, the original document living in NetDocs will NOT be marked as checked out, because it's not waiting on a signature. It will also not be related to the Envelope document. This keeps things clean for your coversheet document so it doesn't get related 1,000 times as you continue to use it.

Documents Are Signed!

Now that everyone has signed the DocuSign Envelope will be completed. SignatureBridge checks in with DocuSign every 30 minutes to look for any changes. When it sees that the Envelope is complete it will grab the signed documents and save them as Version 2 of the Envelope document. While it does that, it will also check in all documents related to the Envelope, change the description tag to say "Signed", and the audit trail on the documents will indicate the new history.

DocuSign will also send you its email to notify you that the signatures have all been received.

If you'd like to speed up the syncronization to get your documents checked back in, then you can also manually sync from your SignatureBridge portal by opening your Envelope's details.

...

3. FAQs

3.1. System Requirements

SignatureBridge Requirements (for company setup)

  1. End users have access to a modern Web browser with JavaScript enabled:
    • Firefox
    • Chrome
    • Internet Explorer 11 or above
    • Edge
    • Safari
  2. Active company-wide DocuSign account
    • This refers to company-wide DocuSign account configured in which your end-users are members of and not individual/personal DocuSign accounts per user(s).
  3. Active NetDocuments account


SignatureBridge Requirements (for End-Users)

  1. Modern Web browser with JavaScript enabled:
    • Firefox
    • Chrome
    • Internet Explorer 11 or above
    • Edge
    • Safari
  2. Active DocuSign account (linked to parent/company-wide account)
  3. Active NetDocuments account

 

SignatureBridge Server Requirements (for on-premise installations)

If your company is going to host their own server for SignatureBridge, the following minimum requirements apply:

  • Windows Server 2008 or above (SignatureBridge will also run on Linux servers, please email support@trumpetinc.com for more information)
  • 1 GB free disk space
  • 4 GB RAM
  • Fully patched Java 8 or above runtime installed
  • Dedicated host name registered with DNS
  • SSL certificate

In addition, your system administrator must be familiar with networking configuration, DNS and SSL

...

3.2. What is a SignatureBridge Admin?

A SignatureBridge Admin is someone who has DocuSign Admin rights.

SignatureBridge Admins have access to account information (licensing details) and user access rights (enabling/disabling user access) within their SignatureBridge Portal. They can also see and interact with envelope details from all users.

This permission is only granted through your DocuSign account and there may be more than one admin. Refer to DocuSign user permissions to see who in your DocuSign account has these rights.

...

3.3. What is a SignatureBridge Background Sync User and How To Change


The SignatureBridge Background Sync User (aka sync user) is the person whose DocuSign credentials/account SignatureBridge uses to access and sync your company's Envelopes.Yes, this means ALL envelopes regardless of if they were sent by the sync user. This means that is the sync user's DocuSign password changes (as an example) then they must log into SignatureBridge at some point to refresh the connection in order to ensure the background syncing continues to function. If this does happen to occur, then the sync user should receive an email notification reminding them to do so.

If you need to reset your connection as the background sync user then go to https://signaturebridge.trumpetinc.com/welcome to log in.

How to Change the Background Sync User

Note that the Background Sync User must be a DocuSign Admin. Any other user with DocuSign Admin privileges may sign in to SignatureBridge, go to Account Info and click the button to the right of the sync user's name to change the sync user over to them.



...

3.4. How do I Activate/Deactivate Users on my SignatureBridge Account?

Background

SignatureBridge Active User Count Licensing allows you to purchase a certain number of 'seats' for your SignatureBridge users. This means that you can quickly deactivate users who no longer need access.

If your license code starts with a "U" then you are on Active User Count Licensing. The number of allowable active profiles is the number directly after the U in the license. See the Account Info tab in your portal for the license number.

If a users account is deactivated they will receive the following error message when they try to log in:


Activating/Deactivating

SignatureBridge Admins (what's this?) are the only users who can activate or deactivate SignatureBridge profiles. To do this, the admin will log in to their SignatureBridge portal by using their DocuSign credentials. Once logged in to their portal, they will click on their name in the top right-hand corner and select Account Info.

Navigate to the Account Users tab and then you'll see a list of users who have created SignatureBridge profiles. Use the toggle buttons on the right to enable or disable their access to SignatureBridge. Changes will be saved automatically.


Note: To create a new user, simply have the new user log in to SignatureBridge (either through the portal, or by way of sending a document via NetDocuments) with their DocuSign credentials. This will create their profile automatically, and enable them if there are enough Active User seats on your SignatureBridge license. If there are no more open seats then the user's SignatureBridge account will still be created but it will be marked as disabled and unusable. To resolve, purchase additional seats and then have the admin log in to their SignatureBridge portal and enable their profile.

If an admin attempts to activate a user but they do not have any more open seats, then they will encounter an error message.

Contact operations@trumpetinc.com to order additional Active User seats.

...

3.5. DMS Connections

Background

A "DMS Connection" is established and stored within your SignatureBridge user profile when you initiate SignatureBridge through your document management system (DMS). When doing so for the first time, your document management system will ask for you to approve this connection. See here for more information on using SignatureBridge for the first time: Sending Your First Document  Approve Integration

This connection is created so that SignatureBridge knows who sent the document to DocuSign and to update the document on your behalf within your DMS as your documents are being signed.


View your DMS Connection(s)

The DMS Connections screen shows what NetDocuments account(s) have allowed Access for a Trumpet SignatureBridge user. You can view this by clicking on your name in the top right hand corner and selecting "DMS Connections". 


Disable or Refresh your DMS Connection

If you need to disconnect your personal DMS connection for testing/troubleshooting purposes, or because the NetDocuments profile linked is no longer in use, simply click on the "Disconnect" button of the connection you want to remove.  

If you had a previous connection that has since gone 'stale' due to lack of use, you can try to re-connect it by using the "re-connect" button. 




Note: If you're trying to remove SignatureBridge features or access for your entire firm, see here: How Do I Revoke SignatureBridge's Application Access to my NetDocuments Account?

...

3.6. I have two DocuSign accounts - which do I use?

Background

Some users may find that they have TWO DocuSign accounts associated with their email address. If this happens with your work email (which is already associated with your organization's parent DocuSign account) then it was probably accidental. This can happen accidentally if sign a document and then follow DocuSign's prompts to "create an account". 

Regardless of how it was created, SignatureBridge will recognize if you have two different DocuSign accounts for your credentials, and it will ask you to select the one you'd like to sign in to SignatureBridge as. Always select your parent organization's account, and not the one that is personal to you. 

Logging in to SignatureBridge with a personal DocuSign account will create a trial account, as it will not be linked with your organization's SignatureBridge or DocuSign account. One way you'll know if you're in a trial account versus your organizations SignatureBridge account is that you can go to your name > Account Info and see a trial key entry listed inside the "Subscription Number" field. 

Solution

Log out of both SignatureBridge AND DocuSign (open a new tab to do this), and then log back in to SignatureBridge using the correct DocuSign account. 

We recommend reaching out to DocuSign for additional support in managing your two accounts and possibly deactivating any unwanted accounts. 

...

3.7. Can I see user activity?

There is a filtering tool that lets Admin users see and interact with Envelopes send by other users. While there is no report you can run per user, you can use the filtering tool to see envelopes sent by user or by date and what their statuses are.

In order to see user activity you must be a DocuSign Admin (which in turn means you are a SignatureBridge admin). Click on your name in the top right hand corner and select "Account Info". Then go to "User Envelopes".

Click on "Filter" to open the filter options and interact with them as desired to find the envelopes you're interested in. You can also sort by certain columns. At this time, this is the only tool that functions as a reporting tool for usage.



...

3.8. I can't access the SignatureBridge Website

Problem

Depending on the message your browser provides, you may get something similar to "This page can't be displayed" with various explanations as to why. Unfortunately, those explanations often don't indicate that your firewall may indeed be the cause of the blockage.

Resolution

You'll want to make sure that your security and firewalls for local and main internet connections allow communication over port 4243 for the TLS protocol and then try connecting again.


...

3.9. The SignatureBridge Envelope Document : How Does It Work?

The SignatureBridge Envelope document is where your Pending AND Signed DocuSign Envelope is stored and saved after you send Documents through SignatureBridge. In a single PDF it holds the UNsigned copies of your documents until all signatures are received by DocuSign. Only once all signatures are received, the final copy of the Envelope will be checked in as Version 2. Since it's checking in the content of the DocuSign Envelope, all of the expected Signatures and documents will be included:

  1. All completed Fields and Signtaures that you designed in DocuSign.
  2. All of the documents that you selected and sent through NetDocuments, whether they contained Signature fields or not.
  3. Any additional documents you added to the Envelope that are NOT filed in NetDocuments, whether they contained Signature fields or not.
  4. The DocuSign Certificate of Completion (appended to the end of the PDF).

Here are a few other tidbits about how this document works:

It will be named after the name of your Envelope which is declared in DocuSign.

This document will be "Checked Out" while signatures are pending.

The pending signature status (including number of signatures pending) will be shown within the Description.

Don't Delete it! If you delete the document, it will be recreated in the same spot.

You can Move it. If you need to change the location of it then you can edit it just like you normally would (More Options>Move) and then SignatureBridge will see the change, and honor the new location. (If you try and delete it after you move it, then SB will recreate it in it's original location and not the new location)

Your original documents will be "related" to this document. This document will in turn be related to each of the original documents.

It will be saved in the same location as ONE of the documents you send to DocuSign. If you only send one document, then it will save in that location. If you send multiple documents filed in multiple placed in NDs, then it will pick one of the documents and file in it's location. (We can't say exactly which document that could be, because behind the scenes DocuSign can rearrange the order in which it holds them). Use the Relationship, or the SB portal, to quickly and easily navigate to the Envelope document.


...

3.10. What is a Signature Certificate?

Background

SignatureBridge includes a copy of the dnvelope's signature certificate (aka Certificate of Completion) with each signed and filed version or envelope PDF that it returns to NetDocuments. It is a ONE PAGE document (or a couple if you had many people sign). It is a certificate of completion and validity. For more information please review DocuSign's website:

https://www.docusign.com/esignature/electronic-signature-certification

When you save your signed results as a Version then the certificate will be attached to the new version as a NetDocuments Attachment. If you use the Envelope PDF to save your signed files then it will be included as the LAST page of the Envelope PDF within NetDocuments.

Can I turn this feature off?

No it is built in to SignatureBridge functionality. If it becomes a widely requested thing then we would consider making this a setting. Email support@trumpetinc.com if you'd like to submit a feature/change request.


There are multiple pages showing up AFTER my certificate, what are the extra pages for?

If you're finding extra pages (about 4) after your Signature Certificate page then what you're looking at is DocuSign's Legal Disclosure. It is not being added by SignatureBridge intentionally, and can be turned off. To disable this then have a DocuSign Admin follow the instructions found here:

https://support.docusign.com/en/guides/ndse-admin-guide-legal-disclosure



...

3.11. What does Save Envelope PDF do?

Save Envelope PDF

For a video describing this functionality, see:  SignatureBridge Settings

When the Save Envelope PDF setting is enabled it means that SignatureBridge will create and file (within NetDocuments) a PDF containing the full contents of the DocuSign Envelope. It will be filed in the same location as the document you sent to DocuSign. If you send multiple documents from different locations, it will choose the first document that is contained in the package and file in that location. This Envelope PDF will also use NetDocuments "Linking" feature to link itself to each of the included documents requiring signature (it will NOT link to documents that did not receive a signature field in DocuSign). This PDF will contain all documents that you sent from NetDocuments and any additional that were uploaded separately from your desktop or network.

The Envelope PDF will be saved into NetDocuments as soon as your DocuSign Envelope is sent to its recipients (in other words, it happens on the very first sync) and it will be marked as “Checked Out”. Original documents containing signature fields will also be marked as checked out within NetDocuments. The Envelope PDF will be updated each time the DocuSign Envelope is changed or signed.

When all signatures have been received and the Envelope is completed is DocuSign, the PDF will be "Checked In" and it will have the Signature Certificate appended to the end of the document.

The Envelope PDF is named after the DocuSign Envelope Subject and is also identified with the tag [DocuSign — Signed].


...

3.12. What does Save Versions do?

Save Versions

For a video describing these settings see:  SignatureBridge Settings

When the Save Versions is enabled it means that SignatureBridge will save the completed/signed copy of the original document, in PDF format, as a new version of the original document that was sent to DocuSign.

So if you send a single Word document for signature then the final, signed, copy will check back in to NetDocuments as a new version and it will be in PDF version. This PDF document will become the new official version for that file.

*This will NOT capture any documents that were uploaded manually into the Envelope from your desktop or network.

If you send multiple documents from NetDocuments into a single Envelope, then any document containing a signature field in the Envelope will receive a new version once the full Envelope is signed. Each document will receive it's own version, which contains only that documents and it's signatures. It will not contain the other documents in the Envelope.

The Signature Certificate generated by DocuSign will be attached to the PDF via NetDocuments "Attachments".


...

3.13. What does Version Lock Signed Documents Do?

Version Lock Signed Documents

When the Version Lock Signed Documents is enabled it means that SignatureBridge will save the completed/signed copy of the original document, in PDF format, as a Locked Version of the PDF file in NetDocuments.



...

3.14. What does Show Envelope Confirmation Sent Do?

Show Envelope Confirmation

This setting opens a dialog within SignatureBridge after you send your envelope within DocuSign to confirm that it was sent successfully.

...

3.15. SignatureBridge 75 Document Limit

An improvement has been made to SignatureBridge – you can now send more documents in a single NetDocuments “Send To” command!

Prior to this change, you were only allowed to send 10 documents at a time.  This was due to variables within the NetDocuments API and Internet Explorer’s URL limitation of 2,048 characters.  Because NetDocuments will stop supporting Internet Explorer as of August 31st, 2020 (see here for their notification), Trumpet has adjusted the document limit from 10 to 75 documents when using the Send-To Command in NetDocuments. 

If you’re still utilizing Internet Explorer, you will want to limit the number of documents in the Send-To Command to be 10.

We think you’re going to like this change!


...

3.16. How To Send Multiple Docs from Different Locations within NetDocs

Background

SignatureBridge is designed to be able to send multiple documents to DocuSign. It's really easy to run a search, select multiple docs and send them off! However, if you want to send docs from different folders/locations in NetDocs then we've got a special trick for that. Read below!

Resolution

  1. Run a search to locate your first document. Highlight or select it then hit the "Send to application" command. 
  2. A window will pop up asking where you'd like to send it. You should see a field where your document is listed. CLOSE this window using the X.
  3. Now, go find your second document, hit the "Send To" button again.
  4. The pop up dialog should now have both documents listed.
  5. Click SignatureBridge to send. Both docs will be sent in the same Envelope.

Repeat those steps if you need to add even more docs.


...

3.17. How do I cancel a DocuSign Envelope in Drafts which I haven't sent yet?

Background

Sometimes after you've sent a document to DocuSign, you'll find that you have selected the wrong document, or the document has an error and you need to restart. You'll need to cancel the whole Envelope and start fresh from NetDocuments. So, how do you cancel the Envelope, you ask? ...

Resolution

If you're still in the DocuSign draft created by SignatureBridge then follow the steps below. If you closed out of the draft already then simply log in to DocuSign, go to "Documents" and "Continue" or "Correct" the draft you need to discard.

Do NOT delete the draft from the Documents page, you must continue the draft first and delete from there).

  1. Locate the button for "Other Actions" in the top right hand corner. Just next to the yellow "Next" button.
  2. Click Other Actions and select "Discard" or "Discard Changes" .
  3. You'll be returned to SignatureBridge and the Envelope details will now say that it was cancelled.
  4. Hit the "Synchronize" button
  5. "View in NetDocuments" to ensure that the document has been checked back in.
Image for Step 2:
cid:a076ae9b821a4f10f17535177a49c80f@sup


NOTE: If for any reason your document wasn't checked back in after the Envelope was deleted then you may manually check it back in to revert to its original state prior to sending.
...

3.18. How do I cancel or change a DocuSign Envelope AFTER I've sent it already?

Background

You've sent an Envelope via SignatureBridge but you've realized you need to either change it in some way or cancel it altogether.

Resolution

Log in to your DocuSign account, go to the "in process" envelope and modify the envelope however you need whether that's adding a recipient or a signature field, or cancelling/voiding the envelope altogether.

Here are a couple links to DocuSign's support articles that might apply to this:

How to Correct an Envelope

How to Void or Cancel an Envelope

Once DocuSign has applied your changes, SignatureBridge will sync them automatically within the next 30 minutes. Or, if you'd like to speed that up, you can log into your SignatureBridge portal and open the Envelope Details. Use the "Refresh Status" button to sync your change.


...

3.19. How Do I Revoke SignatureBridge's Application Access to my NetDocuments Account?

In the event that you need to remove or reset application access to your NetDocuments account, or even confirm that it has permissions, you can do that through your NetDocuments Settings:

1) Click Settings


2) Manage App Access


3) You'll now see your integrated apps and can Revoke if needed. Click Revoke Access and then OK.


...

3.20. How Do I Revoke SignatureBridge's Application Access to my DocuSign Account?

In the event that you need to remove or reset application access to your DocuSign account, or even confirm that it has permissions, you can do that through your DocuSign Settings.

Note: So far we've only found the ability to do this through the Classic DocuSign view. So, switch to Classic view to follow along with the steps below:

1) Go to Preferences


2) Under Member Profile select "Connected Apps"

3) You'll see Trumpet Inc under the Connected Application name. Hit Revoke if you need to remove it.





...

4. SignatureBridge Troubleshooting

4.1. Send To SignatureBridge doesn't work in Chrome browser

Steps to recreate

User selects a document in NetDocuments, right clicks, Send To Application, Trumpet SignatureBridge

At this point, the NetDocuments Send To Application dialog closes, but SignatureBridge does not display

Cause

The Chrome browser sometimes blocks pop-ups from nested dialogs

Solution

To resolve this issue, add a Pop-up blocking exception to Chrome for the NetDocuments site.  Here's how:

  1. In Chrome, click the More menu, then Settings
  2. At the bottom, click Advanced. Then under "Privacy and security," click Content settings
  3. Scroll down to "Pop-ups"
  4. Under the Pop-ups heading, click Manage Exceptions
  5. Under the Allow section use Add to add exceptions using the URL you use for Netdocuments, such as:
  6. Click Done

Now repeat the Send To operation, and it should work.

...

4.2. Error: The requested resource could not be located. [404]

Background

When sending a document from NetDocuments to SignatureBridge, this error is shown:

This can be caused by having restricted IP addresses. 


Resolution

If your site has configured IP Address Restrictions, you'll need to add the SignatureBridge IP address to the list of allowed IP addresses.  To do so:

  • Log into NetDocuments as a user with Admin Credentials
  • Select "Users and Groups"
  • Choose "Configure advanced authentication options"
  • In the "Requirement Type" choose the IP Address
  • Add in the IP address for SignatureBridge. 





...

Release Notes

1. Release Summary 1.2

Summary 1.2

- Bug fix - if envelope syncing failed and an envelope PDF didn't already exist in the DMS, a new envelope PDF would get created every time a sync runs

- Display an error message on the Envelope if the last sync was unsuccessful

- Improve error messages when NetDocuments token needs to be refreshed. We now include the NetDocuments username and vault name that needs to be used for the refresh.

- Admin users can now sync other users' envelopes without getting stuck in an infinite authentication loop

- Admin users can now sync other users' envelopes without getting stuck in an infinite authentication loop


To see a full list of changes, visit:  Change Log

...

2. Change Log

0.2.19

- Improved error message if sync fails due to envelope PDF no longer being in NetDocuments
- If the last DMS sync failed, allow the user to manually sync even if the envelope is signed or canceled

0.2.18 -

- BUG FIX - If a user did not have an active SignatureBridge account, the error was not shown and the user was redirected to the welcome page.

0.2.17 -

- BUG FIX- files with semicolons in their name resulted in a 'document element did not contain the encoded document' error message ([NO_DOCUMENT_RECEIVED : 400])
- BUG FIX - account reminder and notification settings weren't being set on envelopes generated by SigBridge


0.2.13 -

- Improve error messages

0.2.12 -

- Admin users can now sync other users' envelopes without getting stuck in an infinite authentication loop
- Display an error message on the Envelope if the last sync was unsuccessful
- Bug fix - gracefully handle the conflict if a one SSID is passed in the URL, while the user is already logged in to another SS
- Improve error messages when NetDocuments token needs to be refreshed. We now include the NetDocuments username and vault name that needs to be used for the refresh.

0.2.10 -

- Display error message if user attempts to send an ND document that is Locked or Official Locked

0.2.8 -

- Added accountId to user info returned by various calls (esp useful in v1/activelogins response)

0.2.7 -

- Bug fix - if envelope syncing failed and an envelope PDF didn't already exist in the DMS, a new envelope PDF would get created every time a sync runs

0.1.213 -

- Bug fix - if envelope syncing failed and an envelope PDF didn't already exist in the DMS, a new envelope PDF would get created every time a sync runs

0.1.211 -

- Improve error message if failure happens during NetDocuments check out so the message includes the ND doc id of the document that failed to check out
- Added SB Account ID to Account Info screen

0.1.207 -

- If user is allowed to sync all envelopes in the account, allow syncing of any envelope on the account

0.1.206 - 

- Error response if DMS credentials aren't valid during a manual envelope sync and the current user is not able to refresh those credentials (i.e. admin user synching another user's envelope and DS credentials are bad), we now return a 403 FORBIDDEN, and a meaningful error message

0.1.204 -

- Bug fix - if the Envelope list loaded before the user list due to a large number of users, there could be an error displaying the users in the envelope list

0.1.203 -


- Better error messages if user sends an envelope, the SB license has errors, and the user isn't a DS admin

0.1.200 -

- Bug fix - Error when sending documents with really long folder paths or workspace names - Value too long for column "LOCATION VARCHAR_IGNORECASE(100) SELECTIVITY 23"

0.1.199 -

- Bug fix - some users getting error when logging in - Value too long for column \"DMSCONNECTIONS BINARY(10000)\"

0.1.198 -

- Bug fix - Show the error dialog when a user logs into an account that doesn't have any available users on the license. Previously it would just reset to the welcome screen.

0.1.197 -

- During account sync, if the license is more than 75 days past due, disable the account

0.1.196 -

- Add toggle to enable and disable accounts from the SysAdmin Account UI

0.1.195 -

- Move to NetDocsAPI-1.0.24 (recompiled to force Java 8 target - for some reason, 1.0.23 didn't work on Ryan's workstation, even though it did work on the SB server and on Kevin's workstation)

0.1.194 -

- Add ability to enable/disable accounts to the REST API (patch_accounts_accountid_update_settings) (requires Sys admin priveleges)

0.1.193 -

- Regression - Bug fix in 0.1.184 ('Bug fix - Envelopes left in drafts overnight were being marked 'deleted' in SigBridge') wasn't correct

0.1.184 -

- Bug fix - Envelopes left in drafts overnight were being marked 'deleted' in SigBridge
- Admin Envelopes screen now has the Refresh Status enabled for all envelopes - if pressed, it will force a sync, even if the envelope is marked as not requiring a sync

0.1.183 - pre release

- Bug fix - Increase overflow allowance for SS Account Buttons for long account names.

0.1.182 - pre release

- Changed default notification address for when a new account is created to be sales@trumpetinc.com instead of jo@trumpetinc.com
- Added accountmanager.newnotificationaddress property to control what email address will be notified when a new account is created (default is sales@trumpetinc.com)

0.1.180 - pre release

- makes it so we can catch NDAPIException and not worry about it being wrapped in a ProcessingException)

0.1.179 - dev release

- Better error handling in cases where the original document is no longer in the DMS (SB was failing to sync when updating bi-directional document links in this situation - we now log the problem and continue on - can't remove links from a document that doesn't exist)

0.1.177 - pre release

- Feature Enhancement - Allow auto-selecting DocuSign as the SignatureService via URL parameter from DMS Send command

0.1.176 - pre release

- Bug fix - account sync error message incorrectly stated "Unable to connect to Docusign with current credentials. Cannot verify license." - we now display an error message that includes the underlying true cause of the issue (typically that the sync user isn't a DS account admin)

0.1.175 - pre release
- Bug fix - some users saw a 'For input string: "2showConfirm=false"' error when sending documents to DocuSign

0.1.174 - pre release

- Bug fix - some users experienced 'Value too long for column' error after establishing NetDocuments connection

0.1.169 -

Final updates for NetDocus oAuth changes

0.1.162 -

- Deactivating a DS user no longer auto-deactivates the SB user (this was causing problems when the site's sync user was deactivated in DS then re-activated later)
- bug fix - New ND behavior broke how SignatureBridge authenticates to NetDocuments

0.1.159 -

- Update links to new Terms of Use agreement.

0.1.158 -

- If DMS sync fails for more than 10 days past the last DocuSign change, we now discontinue further automated DMS sync attempts unless there is an additional DocuSign change or user manually initiates a sync

0.1.157

- Purge dead envelopes: Was: 10 minutes, Now: 6 hours
- Send Heartbeats: Was: 5 minutes, Now: 30 minutes
- Update licenses: Was: 5 minutes, Now: 30 minutes
- Purge expired tokens: Was: 2 minutes, Now: 10 minutes
- Backup databases: Was: 30 seconds, Now: 4 hours


0.1.155

- Changes to NetDocuments OAuth token handling to support upcoming NetDocuments OAuth changes

0.1.154

- Bug fix - User info wasn't being properly checked for isActive/enabled state if a single DS user had multiple DS accounts
- Inactive users who attempt to log in now fail with a 403
- Update UI to handle 403 for inactive users

0.1.153

- Refactor patch_user_update_settings() so it doesn't attempt to sync the user's state when users are activated/deactivated via API call - this isn't necessary and prevents sys admins from adjusting active/inactive state of other accounts

0.1.152

- SB users are now marked as Admin if the associated DocuSign user is both Active and Admin (regardless of whether the user is active in SB or not) - original behavior was to only set SB admin if the SB user was active.

0.1.151

- Bug fix - Clicking View In NetDocuments at the enveloper level did not work (ND changed their behavior on 4/19/2018)

0.1.149

- Sync DS user with the SB user every time the user logs in

0.1.147

- Added ability to filter Envelope list by user

0.1.140

- Fixed bug when creating new account after redirect login workflow.
- Fixed display bug of account setup steps on Internet Explorer.

0.1.139

- Updated UI to handle multiple accounts with new redirect login workflow.

0.1.138

- Changed DocuSign login to redirect instead of a popup window.
0.1.137

- Refactored recent changes to prevent passing devMode flag through the code

0.1.136

- Moved to NetDocsAPI 1.0.6 to fix issue with Profile date fields
- Added a devMode flag to ServerProperties
- Prevented sync user cred emails from being sent if in development mode

0.1.134

- Made date selector UI more intuitive with pre-selected date range

0.1.133

- Fixed bug in filtering with multiple fields - needed to urlEncode & between fields.
- Added unit test for filtering

0.1.131

- Bug fix - remove toUpperCase from sorting/filtering keys, now requiring case sensitive json property names
- Bug fix - when paging, the nextStart was 1 more than what it should have been

0.1.128 -

- Changes to comply with Accellis penetration testing 2017Q3 - Added exclusions for cipher suites and https protocols, set minimum DH key size to 2048

0.1.127 -

- Made the logging work from a log4j2.xml file in devapphome if the app is in dev mode, else from the packaged config file

0.1.126 -

- Restricted the new DELETE /accounts/{accountId} call to also only work if the account license is in ERROR

0.1.125 -

- Added DELETE /accounts/{accountId} to the available api calls. This call is only available to sysadmins, and will, without
confirmation, delete an account, including all user, envelopes, documents, license, status, and recipients
- Added methods to all of the DAO classes to delete their records associated with the given foreign key (accountid, envelopeid)
- Added a method to AccountManager to delete an account and all associated records
- Added a method to EnvelopeManager to delete an envelope and all associated documents and recipients
- Added assertAllAccountAccess() to AccountAccessInfo to support sync user validation

0.1.124 -

- Modified log4j2.xml to decrease the size of the individual account log files and the number retained

0.1.123 -

- Added a background database backup process that backs up the database every 3 hours.
- Database backup interval is customizable with server.properties setting "dbBackup.intervalminutes"
- Added the database backup status to heartbeats
- Modified the envelope details jsp to synchronize if an envelope redirect has a state of "saved"

0.1.122 -
- Add search capability to Admin page

0.1.121 -

- Added new folder specific methods to DSApiWrapper
- Added SSInfo and DSSSInfo to support storage of SS specific additional info
- Modified the OAuth scope for NetDocuments to allow file deletion
- Updated database to v8. Added SSINFO column to SBENVELOPE, to contain SS information. Currently only contains recycle folder.
- DocuSign recycle bin folder id is now stored in the envelope record (ssinfo) when a new envelope is created
- Fixed a bug in the envelope sync that was causing draft envelopes to never be purged
- Removed the "created" state handler in the envelope creation redirect method, as the envelope sync now handles this use case
- Modified SBEnvelope to contain an SSInfo object. Updated SBEnvelopeDAO to read and store SSInfo
- Modified EnvelopeManager::cancelEnvelope to store envelope description changes as it cancels the envelope
- Made changes to EnvelopesAPI cancelEnvelope() api call (currently unused) to flesh it out a bit more

0.1.119-

- Added Mixpanel to UI to track how users are using SB.

0.1.118 -

- Modified the user settings api call to rename "active" to "enabled" in the json body
- Reevaluated the license status after a user is disabled

0.1.117 -

- Modified Sync User background failed email to be less hostile
- Added support for a "U" Active User license feature, that bases licensing on the number of active
SignatureBridge users, rather than the DocuSign seats in use
- Added a new API call to patch user settings. /v1/accounts/{accountId}/users/{userId}/settings. The call requires
a body that contains "active" : "true/false"
- Modified TokensAPI accessTokens method to check licensed seats when creating a new user
- Added a new builder method to SBAccountUser that handles active and admin settings for existing users
- If a user is set to not active, it is also set to not an account admin
- If a user is set to active, it is only made active if it is a) active in DocuSign and b) there is a seat available
on the license
- Account sync was modified to only set a user to active if they are active in SignatureBridge and in DocuSign

0.1.114 -

- Replaced the background thread executor with a new version that handles timeouts and errors
- New background thread executor will restart a thread that has failed, and will interrupt hung threads
- Modified /systemstatus and /threadstates to work with the new background thread executor

0.1.113 -

- Added create_systems_table_v7 for schema changes to support sync user problem emailing
- Updated the database to V7
- Added firstSyncEmailSent and numSyncEmailsSent columns to the SBAccountStatus table. By
default, firstSyncEmailSent is null and numSyncEmailsSent is 0.
- Modified AccountSyncService and EnvelopeSyncService to send the sync user an email when a sync
fails due to invalid sync user credentials
- Added SyncEmailServices to provide common methods for sending emails related to synchronization
- Set the sync user email From address to support@trumpetinc.com

0.1.112 -

- Refactored envelope creation portion of DMS synchronizer to separate it from document management
- Committed envelope dmsId to database immediately after envelope creation {tpt73000}
- Added deleteDocument(id) to NDApiWrapper
- Modified the background thread buffer time to be 10 minutes, to account for api call lags and help
prevent false indications of hung threads
- Made the /systemstatus call dump all threads to threadDump.log if the overall background thread state isn't OK

0.1.111 -

- Modified /systemstatus to throw an error if the background threads are not all in a good state.

0.1.110 -

- Modified /syncinfo to return AccountInfoContainerDTO so the interface will update after they sync user is modified
- Added button to Account Info page so users could make themselves the sync user for their account
- Modified SBLicenseDAO to replace a default date with an expired date for a license with a default date (legacy FREE_TRIAL) licenses)
- Modified LicenseInfoDTO to replace a default date with an expired date for a license with a default date (legacy FREE_TRIAL) licenses)
- Changed background account sync to catch issues with DocuSign connection, and upon having such, set the license to
an ERROR state.
- Modified the error message returned from the envelope creation call if the sync user creds are invalid, to provide instructions
on how to fix the issue.
- Added version.html to easily see the installed version.

0.1.109 -

- Modified license error text when too many DocuSign seats are in use to be less confusing
- If license is in error when attempting to create an envelope, we now check for an updated license before failing out
- Added /threadstates to RootAPI (/v1/threadstates) to return the current states of all SigBridge background threads as Json text
- Added /systemstatus to RootAPI (/v1/systemstatus) to return the current overall state of all SigBridge background threads as
a single text string ("OK", "ERROR")

0.1.108 -

- No longer update the save PDF setting on existing envelopes when the account level settings change
- Prevented update to save PDF settings if one of them isn't set to true. We require either envelope or document pdf to be saved.
- Modified DMS sync to only create an envelope PDF in the DMS if the saveEnvelopePDF flag is true for the envelope.
- Modified DMS sync to now download the individual document PDF files as new versions of the documents, and attach the
signature certificate to the documents, upon signature completion of an envelope, if the saveDocumentPDF setting is
true for the envelope.
- Updated UI to add saveEnvelopePDF and saveDocumentPDF settings

0.1.107 -

- Modified envelope creation method slightly to ensure DS envelope doc is only downloaded once.
- Updated envelope creation method to only download the envelope certificate if the envelope is completed (signed)
- Updated DB schema to version 6, including the addition of saveEnvelopePDF and saveDocumentPDF columns to SBAccount and SBEnvelope.
Both fields are booleans. SaveEnvelopePDF defaults to true and saveDocumentPDF defaults to false
- Upon envelope creation, the owning account values for saveEnvelopePDF and saveDocumentPDF are copied to the new envelope
- The AccountAPI /settings call now support changing the account saveEnvelopePDF and saveDocumentPDF settings.
- Changes to the account saveEnvelopePDF and saveDocumentPDF settings are propagated to all envelopes owned by the account
- AccountInfoDTO no longer has a settings block for the requireUserForDocSync variable. The variable is now it's own field
- AccountInfoDTO was updated to have saveEnvelopePDF and saveDocumentPDF fields
- EnvelopeInfoDTO and SummaryEnvelopeInfoDTO were updated to have saveEnvelopePDF and saveDocumentPDF fields
- SBAccountsDAO calls were updated to retrieve and store saveEnvelopePDF and saveDocumentPDF fields
- SBEnvelopeDAO calls were updated to retrieve and store saveEnvelopePDF and saveDocumentPDF fields
- Plugged small hole in the DMS sync email notification logic which allowed it to fail on pre-env doc envelopes
- Moved ND login prompt for testing into TestUtils

0.1.106 -

- Modified NDApiWrapper create doc in same location method to first attempt to store the new doc in the same folder
as the existing doc, and upon failure, still just store the doc in the cabinet. This adds support for folder-only cabinets.
- Modifications to NDApiWrapper will automatically cause the DMSSynchronizer to support folder-only cabinets

0.1.105 DevRelease -

- Modified unit tests to prompt for DMS credentials, should the stored ones not exist or are found invalid
- Now we store the new or refreshed unit test DMS credentials back to the test connection file, so they stay updated

0.1.104 -

- Modified NDApiWrapper to add methods for refreshing the ND token and returning the results

0.1.103 -

-UI Changes to account for API changes in 0.1.102

0.1.102 -

- Created TokensAPI to contain token related api calls
- Refactored token API calls from RootAPI and AccountsAPI into TokensAPI, including modification of paths
- Refactored AccountsAPI configuration and initial authentication into a method in RootAPI
- Added a new UNKNOWN SignatureServiceId type
- Added a static NO_ACCESS AccountAccessInfo object, for cases where we don't have valid auth tokens
- Added several assertion methods to AccountAccessInfo, to centralize authentication checks
- Added a new allowsAllEnvelopesAccess() method to AccountAccessInfo to provide more concise authentication check capability
- Added a static NO_ACCESS SignatureServiceAccessInfo object, for cases where we don't have valid auth tokens
- Added several assertion methods to SignatureServiceAccessInfo, to centralize authentication checks
- Added the ability to create an unknown SBId, to help with creation of empty/unknown auth cases
- Reworked api method level authentication to use the new helper methods, and reduce repetitive code
- Created TokensAPITest to unit test new TokensAPI

0.1.101 -

- Added api call to cancel envelopes. This call does not check that the envelope be in a valid state for canceling, and does
not sync the sigbridge envelope/docs afterward.
- https:{rooturl}/accounts/{accountId}/envelopes/{envId}/cancelrequests?ssToken={ssToken} to cancel an envelope in DocuSign
- Modified envelope creation to not create an envelope document in NetDocuments until the envelope has been sent
- Envelope creation in NetDocuments will place the envelope in the location of the first document that contains signature requirements.
In the event none of the docs have signature requirements, or the signature requirements fail to be retrieved, or the
envelope fails to be created in one of these locations, the envelope will be created in the location of the first document with no
signature requirements.
- Added new SBSignatureState, EXT_NOSIGREQ, to represent external documents that don't require a signature
- Modified the envelope and document sync logic to use the new EXT_NOSIGREQ state
- Modified the document state message for external documents that don't require signature to be "Added via DocuSign - No Signature Required"
- Modified the document state message for external documents that require signature, once signed, to be "Added via DocuSign - Signed"

0.1.100 -

- Added logging to troubleshoot issues with empty DMSConnection data

0.1.99 -

- Added support for sorting to the envelope api calls.
- Added a SortFactory to parse incoming sort strings from the api calls, validate them, and create database "order by"
where clauses with them. Sorting is currently only supported for the same columns supported by filtering, and isn't implemented
in the client ui at this time. If no sort filter is provided in the api call, the existing default sort by sorttime descending
is used.
- The format for the sort query item in the api call is "sort=[-][key]|[-][key]... where [-] is an optional indication of a descending sort,
and key is the column description to sort by
- Renamed SBEnvelopeFilter enum to SBEnvelopeColumn
- Created a Sortable interface for use by the SortFactory and required by enums to be used for sorting column definitions
- Fixed minor bug with string wildcard filters

0.1.98 -

- Modified licensing-related unit tests so they don't fail after the license period expires

0.1.97 -

- Added support for paging to the envelope api calls.
- Using offset and limit, the envelopes record retrieval can be further controlled, allowing for paging of results.
For example, 'offset=5' will start retrieving results with the 5th record (0 based). 'limit=20' will limit the returned
results to 20 records. The returned json will now include a Pagination block that will include the start index, the limit requested,
whether more results exist, and the next start index after the returned set. Offset and length are both optional. Not including
either will return all results. Not including offset will result in the results starting with the first record. Not including
limit will result in all remaining records being returned.

0.1.96 -

- Added a FilterFactory and many supporting classes/enums in order to parse incoming filter strings, validate them, and create database
where clauses from them. Filtering currently is only supported for a handful of SBEnvelope columns, and isn't implemented in the client ui
at this time. To use filtering, the existing envelopes api call now accepts a query param of the format "filter=[key][operator][value]&[key][operator][value]...
For example, 'filter=name::*Rebecca*&state::signed' will return all envelopes for the current user that have a description containing "Rebecca" and
which are in a Signed state.
- Added SummaryEnvelopeInfoDTO to support summary envelope information returns
- Modified the envelope details returned from the envelopes api call to return a summary of information, rather than near-full envelope contents
- Added filtering to the envelope retrieval api call
- Added filtering to the all envelopes retrieval api call (sysadmin level call)
- Added many unit tests to ensure filtering works, and updated others for the changes to the envelope return json

0.1.95 -


- Fixed bug in envelope creation that allowed a failure if a document cabinet isn't writable

0.1.94 -

- Bug fix - 'Illegal character in query at index' error when sending some documents from NetDocuments (|1 at the end)

0.1.90 -

- When an envelope is signed, the contained documents will no longer be renamed to have "[Signed]" appended
to their names. Instead, their filenames will be reverted back to their original name.

0.1.82 -


- If the DocuSign call to determine which documents in an envelope require signatures fails, all NetDocuments documents contained
in the envelope will be treated as if they require signature. This will include checking them out, renaming them, and
linking them to the envelope document. An email will be sent to Trumpet, informing them of the problem.

0.1.81 -

- The envelope pdf file in NetDocuments is now named "<envelope subject> [<sigsvc pretty name> - <envelope state>]"


0.1.74 -

- Bug fix - browser caching was preventing new versions of html and js files from being loaded

0.1.73 -

- Removed the View in NetDocuments button for documents when an envelope URL exists
- Disabled the envelope View in NetDocuments button if the envelope URL doesn't exist

0.1.64 -


- Completed the DMS side of syncing, including history changes to documents, and no longer storing the modified documents upon completion
- Deprecated the legacy sync api call that sent an envelope and a document
- Created a new sync api call that just sends the envelope to sync

0.1.63 -

- Modified envelope sync to sync update the envelope document in NetDocuments - name changes to show state, links to/from
contained documents, history updates, checked out/in, update actual doc with signed version


0.1.62 -


- During envelope sync, we will create an envelope pdf in NetDocuments at the path of the first contained document if said pdf doesn't exist

0.1.61 -

- Modified the envelope sync to update the envelope description with any email subject change

0.1.50 -

- Caught DocuSign exceptions during envelope creation, cleaned them up a bit and formatted them in basic html

0.1.46 -

- Bug fix - html in error dialogs was rendering as HTML


0.1.44 -

- Added port redirection on server.sslport - any request on ports other than the primary (the first port) will now be redirected to the primary port

0.1.43 -

- Added server.forcesecure to server.properties. If true, requests to insecure ports will be redirected to the first port in server.sslport. Default is true.


0.1.41 -


- Improved envelope creation error messages to provide details of documents that are preventing envelope creation

0.1.38 -

- Prevented envelope creation if any contained document is already in a SYNCING state
- Set document DMS connection information to Unknown once it enters a signed state
- On envelope sync, set any contained documents that are no longer in the DocuSign envelope to a state of CANCELED
- When an envelope is set to SIGNED, the DocuSign certificate is stored as an attachment to all contained documents in NetDocuments


0.1.36 -

- Added client logging support through new api call

0.1.35 -

- Set envelope state and all contained document states to CANCELED and Deleted in DocuSign if the envelope fails to sync because
DocuSign has purged it.
- Added a daily service that sets any envelopes/documents that are active but are no longer in DocuSign to a
canceled state. Updates "draft" envelopes to a new state if it has changed in DocuSign


0.1.33 -

- Added support for specifying multiple server.port and server.sslport values (separated by commas or semicolons)

0.1.32 -

- Added license update support

0.1.31 -

- Added System Admin support to the product

0.1.30 -

- Added heartbeat support. All enabled accounts will send heartbeats after daily sync occurs.

0.1.29 -

- Prevented duplicate document creation for a single envelope
- Prevented multiple versions of a document to be created for a single envelope
- Prevented envelope creation if any contained documents aren't accessible (perms, checked out, invalid version, etc)

0.1.28 -


- Bug fix - In Envelopes with multiple documents, only one document was being synced
- Bug fix - Internet Explorer users would not see newly created Envelopes in the SB envelopes list
- Bug fix - Internet Explorer users would get "Envelope not found" errors after sending the envelope (IE caching issue)
- Bug fix - Internet Explorer users would get Invalid token error messages if three was a delay of more than 15 minutes between the first envelope send and the second envelope send (IE caching issue)

0.1.27 -
- Added EncryptionKeyUpdater, which will move the db version to 4, and will attempt to fix any encryption
issues caused by the recent changes to encryption

0.1.26 -

- Prevented free trial license generation when not in SaaS mode. Instead, created an invalid license for new accounts

0.1.25


- Removed ssAccountId from GET /signatureservicetokens/{sstoken}

0.1.24 -

- Added SaaS mode, so we can differentiate between installed and cloud servers.
- Prevented envelope creation if license is in an invalid state


0.1.22 -

- Added API call to update an account with a new license string. The license status is updated immediately.
- Fixed bug license start and expiration dates weren't getting updated in the license table


0.1.20 -

- Fixed bug where the Document state wasn't being changed to Canceled or Sent if it had previous been set to Done, but the
envelope status moved from a done state.
- DB Schema Change - v3
Added new tables SBAccountStatus (for account sync info) and SBLicenseInfo (for license info)
Moved license field from SBAccount to SBLicenseInfo, and migrated existing data to new data
Removed status field from SBAccount
Added createdDate field to SBAccount and populated all existing rows with '2016-04-10' (date SB went Beta)
Added a constraint on SBAccount that prevents multiple rows for a SSId/SSAccountID combination
Added a constraint on SBAccountUser that prevents multiple rows for an SSId/SSUserId/SBAccountId combination
- Modified SBAccount creation api to also add a related row to the SBAccountStatus
- Modified SBAccount synchronization to update its account status when it is run
- Fixed bug in account synchronizer, where new users weren't being committed to the database.
- Added SignatureBridge license generation and status support
- Modified SBAccount creation api to also add a new license info row when a new SBAccount is created
- Modified SBAccount synchronization to update the account license with seat and start/expire info when it is run
- Modified account sync to not auto-add missing users, but to update existing users with changes from DocuSign. Set users
not reported by DS to non-admin and not active
- Modified the user token retrieve api method to create the user, if it doesn't already exist in the database.
- Set Free Trial license expiration to 30 days

0.1.19 -

- Added logging if keystore.jks isn't found
- Enhanced KeySetup tool so it now prompts for encryption keys for the database encryption, the keystore manager password and the keystore entry password
- Command line is now: java com.trumpetinc.signaturebridge.KeySetup /setkeys

0.1.18 -

- SQL fix - syncUser info was causing extraneous records to be returned
- Bug fix - prevent multiple AP calls to create SB Account for the same signature service account id
- Bug fix - one of the lookups by signature service account ID didn't include the SSId (could be a problem if two signature services had the same account ids)
- Modified callback from envelope creation to check if the envelope was canceled during creation, and mark it as
such if it was
- Bug fix - changed the authorization check position in the validation request, to prevent possible exception
- Modified the EnvelopeStateSynchronizer to ignore envelopes that have already been canceled
- Added Envelope Canceled dialog to the user.html, to show the user that a new envelope was canceled before being sent
- Database encryption key is now set on a per site basis - the key must be set for any install using "java com.trumpetinc.signaturebridge.KeySetup /setkey <plaintextkey>", or if operating from a true console (not in an IDE), you can use java com.trumpetinc.signaturebridge.KeySetup /setkey and then you will be prompted for the key" - SigBridge will fail to launch until this has been done.

0.1.17 -

- Newer envelopes now display at the top of the user's envelope list
- Documents in envelopes that haven't been sent now are now labeled "In DocuSign drafts" instead of "Awaiting signatures"

0.1.16 -

- Added support for routing log messages to different files, using the ThreadContext->ROUTINGKEY mapping
- Added initial support for routing account specific log messages to log files of the format [accountid].log

0.1.15 -

- Small bug fix related to invalid DS access token corner case
- Bug fix - invalidated DS token workaround from 0.1.14 didn't work in all cases (database commit missing)

0.1.14 -

- Temporary work around for DocuSign invalidating tokens on background services - for now, when sync user logs in, we update the sync token in the database
- Added /accounts/{accountid}/users to retrieve full list of users for the account
- Added the sync user info detail in AccountInfo response (user name in addition to the user id - note that this changed the json format - GUI will need to be adjusted to accommodate!)
- Removed signaturebridge.location from the properties file, and added signaturebridge.rooturi (Which should specify the root of the SB URL - i.e. signaturebridge.rooturi=http://localhost:4242 or signaturebridge.rooturi=https://signaturebridge.trumpetinc.com:4243
- signaturebridge.rooturi is now a required field in server.properties (all sites must set this value explicitly)

0.1.12 -

- SignatureBridge will now accept and sync Word documents. The signed document is stored as a new version that is a PDF. Users can view prior versions in NetDocuments To retrieve the original Word document

0.1.10 -

- Bug fixes for EU and AU NetDocuments datacenters

0.1.9 -

- Added support for EU and AU NetDocuments datacenters

0.1.6 -

- Added server.properties setting to control which signature services will be presented in the UI - e.g. signatureservices=DSDEV,DS - default is signatureservices=DS

0.1.4 -

- Removed call to retrieve envelope information after creating envelope - we now rely on the data returned from the create call



...

3. Release Summary 1.0

Summary 1.0

  • Added support for EU and AU NetDocuments Datacenters
  • Added support for routing log messages to different files.
  • Adjusted the sort so that new envelopes display at the top of the user's envelope list.
  • Adjusted SignatureBridge so that when envelopes are Cancelled, the software ignores them
  • Ensured that duplicate document creation for a single envelope couldn't happen, and prevented multiple versions of a document to be created in a single envelope.
  • If a users is activated / deactivated, you can now adjust the state of the account
  • SignatureBridge users are marked as Admin users if the associated DocuSign user is both Active and an Administrator.
  • Added the ability to filter envelopes by user
  • Made the date selector more intuitive with a pre-selected date range.
  • Added searching capability to the Administrator page

To see a full list of changes, visit:  Change Log


...

© 2012 Trumpet, Inc., All Rights Reserved