1. Release Notes 5.5.1
Release date: 2020-01-31
1.1 New features
eSignatures 5.5.1 is a hotfix version and doesn't contain new features.
1.2 Improvements
Security improvement: configurable expiration of OTUs
As an additional security measure, you can now configure after how many days the one-time URLs (OTUs) must expire if they are not used. This way, OTUs no longer remain valid indefinitely or until the package expires when they are not used.
Administrators can configure the default expiration behavior on environment level in the Config Index, but WebPortal users and API users can also override it on package level.
1.3 Handled issues
Jira code |
Issue code |
Description |
CEP-7287 |
/ |
Server sign no longer possible with contact groups or approvers. |
CEP-7270 |
/ |
Issue when person group and contact group contained a contact with the same email address has been solved. |
CEP-7258 |
/ |
Mailing language issue has been solved. |
CEP-7279 |
/ |
Issue when loading a one-page document in the WYSIWYS has been solved. |
CEP-7239 |
32264 |
API doc error about phone number validation has been fixed. |
CEP-7226 |
/ |
Complex/sequential signing issue when Eid and manual + Eid were offered as choice of signing has been solved. |
CEP-7225 |
/ |
Complex signing issue with SMS OTP has been solved. |
CEP-7222 |
32234 |
Contacts selection issue over multiple pages has been solved. |
CEP-7215 |
/ |
Disabling OpenID Connect issue has been solved. |
CEP-7198 |
/ |
Approvers icon display issue in Internet Explorer has been fixed. |
CEP-7194 |
/ |
Incorrect scaling of signing field images has been fixed. |
CEP-7183 |
/ |
Parallel adding of documents issue has been fixed. |
CEP-7175 |
/ |
Performance issues have been solved. |
CEP-7170 |
/ |
Signers are now displayed in alphabetical order in the face to face signing modal. |
CEP-7166 |
/ |
Document count issue has been solved. |
CEP-7164 |
/ |
Notification translation placeholders are no longer case-insensitive. |
CEP-7163 |
/ |
Reject button issue in mobile WYSIWYS has been fixed. |
CEP-7153 |
/ |
Canceling contact when uploading a package issue has been fixed. |
CEP-7138, CEP-7137 |
/ |
User management display issues have been solved. |
CEP-7136 |
/ |
Theming issue has been solved. |
CEP-7131 |
/ |
Mandated BeLawyer signing issue has been solved. |
CEP-7122 |
/ |
Theming accessibility issue has been solved. |
CEP-7116 |
/ |
OpenID Connect creation issue has been solved. |
CEP-7109 |
/ |
Phone number country issue has been fiexed. |
CEP-7062 |
/ |
Cloud contact could not be added as approvers. |
CEP-6852 |
/ |
Invalid mail OTP code issue has been solved. |
CEP-6422 |
/ |
Missing mail OTP error message has been added. |
1.4 Known issues
eSignatures 5.5.0
Jira code |
Issue code |
Description |
CEP-7078 |
/ |
It’s currently not possible to sign with FranceConnect using eIDAS3 |
CEP-6352 |
/ |
Translation migration issue. |
eSignatures 5.4.3
Jira code |
Issue code |
Description |
CEP-6897 |
/ |
When using Audit proofs, a Worker issue occurred when packages were set to finished. |
eSignatures 5.4.2
Jira code |
Issue code |
Description |
CEP-6874 |
/ |
Inconsistent casing of query parameter “SessionId” in case of invalidToken. |
CEP-6288 |
/ |
Branding issue: saving a change in one of the subtabs navigates to 1 tab above. |
CEP-6865 |
/ |
When upgrading from 5.0.7 the Environment settings page prompts to save without having made a change. |
Signatures 5.3.0
Jira code |
Issue code |
Description |
CEP-5944 |
/ |
Itsme scrolling is not as smooth as expected on Safari on iPhone. |
eSignatures 5.2.4
Jira code |
Issue code |
Description |
CEP-5564 |
/ |
When a package contains both an asynchronous and synchronous signing method, and the asynchronous signing fails, the signing session cannot be recovered. |
eSignatures 5.2.0
Jira code |
Issue code |
Description |
CEP-4817 |
/ |
Display bugs when using complex signing on Safari and Chrome |
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 |
/ |
/ |
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 single document must not contain more than 30 signing fields.
- 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.
- PDF portfolios are not supported. This is because a PDF portfolio may contain a wide range of file types that are not supported by eSignatures. A PDF portfolio may for instance contain e-mail messages, spreadsheets, CAD drawings, PowerPoint presentations, etc. As a result, a signer will only be able to view and sign the PDF cover sheet, and not the actual files the Portfolio contains, which renders the entire Portfolio invalid.
- 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
(Note that these limitations do not apply when using itsme through OpenID Connect)
- 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, each document within the package must be signed individually, which means QuickSigning is not supported.
- 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 storage drive (repository) on which the data will be hosted. The bigger the documents, the more 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.
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.5.1, consult the Connective - eSignatures 5.5.1 - Installation Documentation to learn how to upgrade it to version 5.5.