1. Release Notes 5.2.0
Release date: 2019-02-06
1.1 New features in eSignatures 5.2.0
New supported input file format: .xml
In eSignatures 5.2 you can upload .xml documents through the API. Signers are able to verify the content of the .xml files they are asked to sign, just like with other supported file types. This way, signers can effectively see what they sign. If necessary, a .pdf representation of the .xml file can also be uploaded through the API, for signers to view their document in a more easily readable format.
New API call: Get Enabled Signing Types
This new API call returns the signing types that have been enabled in the eSignatures Configuration Index. This call is useful for integrators who need to know which signing types are currently enabled in a given eSignatures installation, and prevents them from needing to duplicate the entire list of signing types in their configuration database.
Mandated signing on itsme
In eSignatures 5.2, the mandated signing feature is also available for itsme signing. You are able to determine who exactly is mandated to sign during a particular session, based on their name and birth date.
Asynchronous signing
In eSignatures 5.2, asynchronous signing is supported. Thanks to asynchronous signing, signers no longer have to wait until all documents are signed before they may close the signing session. This comes in handy especially when signing high volumes of (large) documents. As soon as the signing has started, signers may click Close to close the signing session and continue working on other things. The signing will simply run in the background.
Asynchronous signing is available for the following signing types: manual, SMS OTP, Mail OTP, iDIN, pincode (through OpenID Connect) and Biometric.
Attention: when documents are sent through the eSignatures API and a RedirectUrl has been configured for the signer, the signer will still have to wait until the signing has finished. The purpose of a RedirectUrl after all is that the signer is redirected to another URL after signing. Therefore, the Close button will be unavailable, and the signer will be informed they will be redirected.
New interface language: Spanish
The eSignatures WebPortal interface is now available in Spanish.
Configurable back button
The URL to which the back-button points when using a mobile device can now be configured in the Configuration Index. This URL used to be hardcoded to https://www.esignatures.eu/.
Phone number confirmation and Email address confirmation can be disabled or enabled
In the Configuration Index you can choose to disable or enable the phone number confirmation and email address confirmation.
When phone number confirmation is disabled, signers won’t need to complete their phone number. Instead, they receive the sms code directly.
When email address confirmation is disabled, signers won’t need to complete their email address. Instead they receive the email code directly.
Terms of use, Privacy policy and cookie policy added to the signing session
Clients can integrate their terms of use, privacy policy and cookie policy through the Configuration Index. Note that on-premise clients are required to do so. The default Connective terms and policies are void for on-premise clients.
Signers can consult the applicable terms of use, privacy policy and cookie policy in their signing session.
1.2 Improvements
New supported regions for SMS OTP signing
A new series of countries and regions such as Mayotte and Reunion are supported for SMS OTP signing.
1.3 Handled issues
Jira code | Issue code | Description |
---|---|---|
CEP-2578 | / | Users who only have view rights on a document group can no longer use the Notify button. |
CEP-3334 | / | The test PKI tool now shows the correct message when loading eid_valid_none.xml. |
CEP-3374 | / | It is no longer possible to send multiple reminders immediately. |
CEP-4242 | 26971 | Fully signed documents no longer remain in Pending state after switching to the All tabs view. |
CEP-4233 | / | When removing signature fields defined by markers, eSignatures sometimes considered the removed fields as still requiring a signature. |
CEP-4473 | / | Terminology inconsistencies between WebPortal and API have been resolved. |
CEP-4581 | / | WYSIWYS language was not always displayed in default user language |
CEP-4690 | / | When canceling the OpenID Connect signing session, the signing sometimes continued to run in the background, while the package had the status ‘pending’ and its documents had the status ‘signed’. |
CEP-4691 | / | When signing with OpenID Connect, eSignatures always tried to quicksign. |
CEP-4698 | 27886 | In CallbackURI with https://* the requests were not sent to https://* due to the fact that text/json was used instead of application/json |
CEP-4765 | / | Complex signing combined with itsme used to throw legal notice errors. |
CEP-4828 | / | OpenID Connect and iDIN signing could not finish face to face signing when there is a single signer on the document |
CEP-4889 | / | When the system logged you off automatically, the login page was shown without buttons or text. |
CEP-4908 | / | Corrected SMTP parameters in Installation Guide |
CEP-4933 | / | Zooming issues while manual signing are fixed in Firefox |
CEP-5005 | / | When using API V2 to create a package and adding a document to the package with a targetType, the document was not added and an error was thrown. |
CEP-5067 | / | An Unsupported Media Type error was thrown when trying to use OpenID Connect signing type |
CEP-5127 | / | It is no longer possible to add a legal notice in the WebPortal or in the API when the legal notice setting is set to disabled in the Configuration Index. |
CEP-5130 | / | Legal notices on package level were not always saved on signer level |
CEP-5184 | 28820 | Some signed documents did not contain all signatures after downloading them. This was caused by the fact dots were used in text field or signature field names, which is currently not supported. |
CEP-5185, CEP-5332 | / | Special characters were not blocked in phone number fields. |
CEP-5186 | / | Error message when signing with an expired certificate has been improved. |
CEP-5217 | 28938 | Incorrect/incomplete download routes were mentioned in the External API v3 Swagger. |
CEP-5238 | 29018 | Some non-unique OperationIDs were used in the External API v3 Swagger. |
CEP-5276 | / | The language of the WYSIWYS on mobile could not be changed. |
CEP-5289 | / | When a DefaultTargetFormat is set in the Configuration Index and you add a document to a package in API v3 or create an instant package, both without using the TargetType parameter, an error used to be thrown. |
CEP-5293 | / | Callback URL didn’t work in V2 templates |
CEP-5325 | / | There used to be a signing field multiplication issue in the WebPortal when adding multiple signing fields for the same signer. |
CEP-5361 | / | API v2 "Single" Document Status call returned "Signed" for some documents but the documents couldn't be. |
CEP-5375 | / | Packages containing templates with user groups could not be created. |
1.4 Known issues
eSignatures 5.2.0
Jira code | Issue code | Description |
---|---|---|
CEP-5370 | / | When you set the MandatedSigningType parameter to matchid for eID signing in the Configuration Index, it is currently not possible to upload templates. |
CEP-4396 | / | Rebranding improvements |
CEP-4817 | / | Display bugs when using complex signing on Safari and Chrome |
/ | / | Itsme signing is currently not supported on macOS Mojave v10.14 combined with Safari v12.0 |
eSignatures 5.1.1
Jira code | Issue code | Description |
---|---|---|
CEP-4719 | / | The timeout of the session is currently absolute. Users are logged out even if they have been active. |
Older known issues
Jira code | Issue code | Description |
---|---|---|
CEP-3467 | / | eID field with name+birthday validation & belaywer field (regardless of validation) incompatible |
RFC-520 | / | When a package contains multiple documents that must each be signed by a different user, and User A rejects the documents assigned to him, while User B accepts the documents assigned to him, the rejection details are not visible on Package level, nor on Document level for the user who accepted the documents. The rejection details are only visible on Document level to the user who rejected the documents. These details will be completed in a future version of eSignatures. |
CEP-2230 | / | You can place a signing field partially outside the page, but the signature will still be valid. |
CEP-3779 | / | Signing method is not selectable |
/ | / | German installation of Chrome can generate errors during signing. |
1.5 Known limitations
General
- A package must not exceed 150 MB.
- A single document inside a package must not exceed 30 MB.
- A package may contain a maximum of 15 documents.
- An .xml files must not contain more than 2 million characters per file. A package must not contain more than 15 .xml files.
- Large files might affect signing performance depending on the user's Internet connection.
- Documents whose physical dimensions exceed 3.99 m by 3.99 m are not supported.
- Uploading PDF/A documents is only allowed if the format is PDF/A_2A or PDF/A_1A.
- When uploading PDF documents that already contain signature fields - which you created in a PDF solution such as Adobe Acrobat Pro DC - make sure the signature field names only contain letters and numbers, or a combination of both. Any special characters such as accented letters, slashes, dots, etc. are not supported and must not be used. The same limitations apply when uploading PDF documents that contain text fields.
- Adding multiple initiators within a single package is not supported.
- Combining eID signing and BeLawyer signing as choice of signing is not always supported: when the MandatedSigningType is set to nameandbirthdate in the Configuration Index, these two signing methods cannot be combined.
- Packages currently can’t contain both XML documents and PDF documents on which signatures will be placed. The type of package is determined by the first uploaded document.
- The default groups ‘administrators and default user group’ can’t be used as a signer in templates.
- Inserting a tab in front of a Text Marker in Word is not supported. Instead of using tabs, use tables, columns or text boxes. If you still want to use tabs, convert your Word document to PDF before uploading it.
- When using Safari: after you upgrade from an older version, you will be prompted to quit your browser. When reopening your browser and your previous tabs don’t open automatically, do not reuse your original link to the signing page. Instead, go to History > Reopen All Windows From Last Session.
- Native design applications for DTP, CAD, etc. can generate documents with a high level of complexity (very high number of elements, vectors, images, …). This may result in the fact that the application cannot prepare the document in a reasonable timeframe. Consequently, it will be impossible to add these files to the Signing environment (not through the API nor in the DocumentPortal) due to timeout. It is not possible to know in advance if a complex document will generate a timeout or not as it depends on too many factors. The applications generating these kinds of PDFs usually have a setting to create a PDF that is suitable for online usage. We strongly recommend using this setting to reduce the complexity of the document before upload.
Itsme signing
- When using itsme as signing method, the target type of your documents must be PDF/A-1 or PDF/A-2. It’s the administrator’s responsibility to make sure these output formats are available in the user’s eSignatures solution, and it’s the user’s responsibility to select the correct output format. Connective does not perform any checks whether the right output format has been selected combined with itsme.
- When using itsme signing in packages through the WebPortal, each document within the package must be signed individually.
- Itsme signing is currently not supported on macOS Mojave v10.14 combined with Safari v12.0.
Audit Proofs
- The Audit proof feature has a significant impact on the eSignatures database. The bigger the documents, the more database space will be used. The impact grows exponentially with bigger documents.
- The Audit proof feature also has an impact on the signing speed of eSignatures. The bigger the documents, the longer the signing time will be. Small documents (<1MB) do not seem to impact the signing speed.
API v2 to v3 migration
Legacy Mode
If clients are not able to upgrade to API v3, because they’re not ready to support one-time URLs or access tokens, they can use the Legacy mode setting combined with version 2 of the API. Legacy mode is a transitional measure that supports ‘old’ URLs and allows you to complete unfinished documents. Please be aware that this is a deprecated feature and will be removed in version 4 of the API.
The following limitations apply:
When legacy mode is set to disabled in an environment, and you decide to enable it later on, the API flows that have been created when legacy mode was disabled will no longer work.
When Legacy mode is set to disabled, the download URLs retrieved from API v2 can only be used once. These URLs should not be sent directly to the end user in an email, as the second time the URL is opened, a non-user-friendly error message will be show. To avoid this, clients can take the following actions:
- Either they email an URL to their application so that they always redirect from their application to the newest download URL retrieved from API v2 just before redirecting.
- They append ?fromEmail=true to the URL retrieved from API v2 so that we can show an error screen asking the end user to enter their email address. If that email address corresponds with a signer or receiver and the package / document exists they should get an email from Connective with a new, working URL.
2. Upgrade Information
For customers signing with physical tokens (eID, biometric using Wacom, etc.), the Connective Browser Package must be upgraded to version 2.0.6. The upgrade should be prompted automatically when trying to sign a document.
If you have a version of eSignatures installed prior to version 5.2.0, consult the Connective - eSignatures 5.2.0 - Installation Documentation to learn how to upgrade it to version 5.2.0.