User - eSignature
New IP Range
DocuSign has added a new IP range for European Union-based accounts: 184.108.40.206 through 220.127.116.11. If your account uses whitelisting for email or Connect please add the new IP range. DocuSign's current ranges remain valid. For a full list of DocuSign IP ranges, please visit theTrust site.
DocuSign eWitness allows organizations to enable signers to identify up to two witnesses to sign an agreement in a legal and confidential manner. eWitness captures the witness information in the Certificate of Completion to support any legal disputes. This means many of the typically paperbased deeds can be digitized in the future, saving organization significant time and money. This feature is currently only available for Enterprise Pro customers. If you are not an Enterprise Pro customer, please ask your Account Manager to enable this feature.
21 CFR Part 11
The Specify Recipient role will no longer be blocked from specifying "account-less" recipients. If the recipient specified is account-less, DocuSign will auto-activate an account to ensure proper authentication during signing as required by DocuSign's Part 11 module.
PowerForms CSV download can now handle data that includes special characters in document fields.
Publish New Windows Installer
DocuSign PKI (Public Key Infrastucture ) update enhancments include:
- Allows log of proxy details (if enabled)
- Allows use of Windows SSL truststore (default config)
Conditional fields are enabled for witness recipient for both EWitnessSignerModal signers and WitnessModal.
Enterprise Pro customer, please ask your Account Manager to enable this feature.
21 CFR Part 11
- The Specify Recipient role will no longer be blocked from specifying "account-less" recipients. If the recipient specified is account-less, DocuSign will auto-activate an account to ensure authentication during signing as required by DocuSign's Part 11 module.
- Alternative Signing Option The Alternative Signing Option for Part 11 will streamline the signing experience for Part 11 signers. With this new option, Part 11 signers will authenticate (with a minimum of email and password) at the point of accessing the envelope, which is the start of the individual’s signing session, and again before completing the envelope. The Alternative Signing Option is turned on by request. If you’re interested in turning on this experience for your account, please contact your account manager or one of DocuSign 's support representatives.
- Sending Settings: Admins can now enable the feature found within Sending Settings named: "Allow senders to add recipients from this account's User Directory." When enabled, senders on the account will be able to access and search the User Directory found within their Address Book during sending. The User Directory contains a list of active DocuSign users that are members of the sender's DocuSign account.
- Previously DocuSign did not allow users to select branding languages and default within the selected branding languages. DocuSign now offers improvements on the branding language experience considering product end-to-end scenarios (Admin - Sending - Signing). DocuSign has implemented this and made this possible via XML for a few large multinational companies and this feature will be available to all making the experience easier.
- Administrator can select a subset of languages for a brand:
- Add a setting to allow admin to choose branding languages from the 43 pre populated signing languages
- Admin can set as many languages as possible
- Admin can edit and save the the setting or cancel the operation
- Administrator can select a default brand language:
- Allow admin to indicate which languages from the selected is the default branding language ( if signer does not have any languages listed as branding languages, the signer can receive the default language instead).
New administration options for ID Evidence in the ID Verification menu in eSignature Admin:
- Administrators can select to store optional data extracted from a user’s ID, passport, or eID after identity verification. This data is attached to the envelope and will be deleted if an envelope is purged.
- Administrators can also maintain the default configuration where no additional personal information is stored after identity verification.
- ID Evidence data is stored on the same site as the DocuSign account. For example, European accounts have their data stored in Europe.
- Only senders can access ID Evidence data of their envelopes.
- Availability: Requires the DocuSign Identify Add-On; Now available in Production
- Enhancements for Appliance Pools in DocuSign Admin:
- Added ability to delete the last appliance in a pool for Display Appliance Pools.
- Accounts linked to a Display Appliance Pool are now listed in Alphabetical order.
- Added option to Edit a Security Appliance Pool to use DocuSign’s internal keys to encrypt future envelopes while maintaining access to existing envelopes.
- Validator for Life Sciences Enhancement – Administrators of DocuSign’s Validator for Life Sciences will now be able to see a list of past Validation Reports that have been sent to the subscribing account. This will be found in the same location where Administrators can manage Validation Report recipients.
- New Sending Setting in eSignature Admin: Allow senders to add recipients from this account's User Directory
- This setting is unchecked (disabled) by default.
- When checked, senders on the account will be able to access and search the User Directory found within their Address Book during sending. The User Directory contains a list of active DocuSign users that are members of the sender's DocuSign account.
- Availability: Demo only. Available to Commercial and Enterprise customers.
User - eSignature
- Fixed error message "Error! Filename not specified." showing up on DocuSign's emails forwarded from Outlook.
- The first stamp in CoC 2nd page is now in the correct position.
- Initials field was not appearing for altered Collaborative field; Finish was giving a "Not all tags are signed" error. Initial field now appears for Signers to agree with the change.
- Responsive Signing feature was not triggering for envelopes in Demo. Documents now appear as responsive in the signing ceremony.
- Required checkboxes did not honor the setting in "DocuSign_TabRequiredBorderColor", now they appear as expected.
- Symbols < and > in dropdown appeared to signer as < and > and they can select either as valid option. This was fixed and both appear as expected.
- Not all responsive conversion paths check page/byte limits were being honored. This is a new setting through which enforces a 75 page limit for responsive conversions at a per-document level.
- Checkbox Groups were not behaving as expected on Mobile if Responsive Signing is enabled. This has been rectified and now when selecting Checkbox from group, boxes are marked as checked.
- Reassigning signing responsibility was producing a blank document. Now when the user receives the reassigned envelope, the entirety of the documents and any associated tabs are available to the reassigned signer.
- Administrators can now save Signing Settings after modifying only the Supplemental Documents settings.
- When inviting an external account to link to an organization, the account list no longer includes closed accounts.
- Phone Authentication value supplied by Agent was not saved if envelope was created via API CreateEnvelope. Now the Phone value supplied by Agent for Signer is retained.
PowerForms with ARR Conditional Routing
PowerForms with Conditional Recipient is available to allowed (previously whitelisted) customers. This gives senders the ability to create a PowerForm open to a wide audience, then route dynamically to the correct signers depending on how the form is filled out. The form can automatically route to different departments based on a dropdown. Please contact your Account Manager if you would like to try this feature.
Connect failure queues previously kept errors for >30 days. Majority of customers would either have fixed and republished in the first few days or the queue tends sit and build up. In order to preserve performance for all customers, the failure queues will now be kept for 15 days. This is scheduled to occur in July.
Templates List Performance Improvements for IE
DocuSign will be updating the template list to be in line with the envelope list. Updates will be made to the menu for the folder items andstructure.
21 CFR Part 11- Improving Activation of Federated Users
DocuSign will be releasing a fix that will no longer block senders from sending to federated users without an active DocuSign account. This will only impact recipients with an email domain that is claimed on DocuSign. This improvement has been rolled out to a few select customers and will be rolling out over the next few months.
21 CFR Part 11 Enhancement
When signing a Part 11 envelope and authenticating your signature through a third party identity provider (IdP), you will now be directed straight to you your IdP for authentication and will bypass the DocuSign landing page. This only applies to domains that have been claimed on DocuSign and have been configured as "required" for log in to relevant CFR customers over the next few months.
Download Email Improvements
Users will be taken to a download section upon clicking the Download link from an email. From the link, users are immediately taken to the download section inside Reporting. Users can see up to 90 days worth of scheduled reports. Once the View button is clicked, the CSV file downloads.
Enable clients to enforce uploading a signature
During January, DocuSign began releasing a new feature to enable clients to enforce uploading a signature (instead of allowing the selection option of the default or to draw a signature). It will be enabled from a checkbox ("Allow senders to require signers to upload a new image to sign or initial") in the Sending Settings. The checkbox will be OFF by default, so clients will not see it. The feature will be activated during the Prepare phase under the Advanced Settings tab. For more information please see the NDSE user guide.
Create Recipient View
This change is to the URL returned by the following API endpoint:
Create Recipient View ([https://developers.docusign.com/esign-rest-api/reference/Envelopes/EnvelopeViews/ createRecipient])
What will change?
- Customers can expect to see the length of the URL to be longer. Customers can expect to be redirected through a different subdomain depending on region of the account sending the envelope.Please verify your domain whitelist per the following documentation: [https://www.docusign.com/trust/security/whitelists]
What will not change?
- DocuSign has designed this change such that your existing functionality should not change. Why are we making this change?
- These changes are part of an effort to standardize and further secure links that redirect into Signing Ceremony. DocuSign is working to centralize the system used for authentication across all its products. These new links provide improved security compared to the current system. Ability to expire, revoke, or modify an existing link without changing it. Make secret links harder to brute force or to guess. Provide improved auditing on redemption. Provides better ability to enforce authentication policies such as two-step verification.
When can you expect these changes?
- Changes started rolling out the week of Feb 18th. If you will not be ready by the Prod rollout, you can request an extension for your Production accounts by working with support or your Account Manager. If you are ready to see the change in Production and would like to request early access, please reach out to support or your Account Manager.