1. Release Notes 5.5.5
Release date: 2020-06-24
1.1 New features
eSignatures 5.5.5 is a hotfix version and doesn't contain new features.
1.2 Improvements
Legal notices are now added to the signature when using server signing
When using server signing in the eSignatures API, you can now pass a LegalNoticeCode or LegalNoticeText parameter in the InstantPackage Creation call and its value will be added to the signature.
Important: The legal notices should not contain placeholders that must be filled in manually, since there is no user interaction with server signing. If a legal notice does contain a placeholder, the initial value of the variable will be added to the signature.
Additional data is saved when using mandated signing
Additional data is stored in the database during mandated signing, whether it fails or succeed: Id, PackageId, SignerFieldId, TimeStamp, Source and Rules (containing, IsSuccess, ValidationType, ExpectedMatchLevel, ActualMatchLevel, InternalData and ExternalData).
This data is removed from the database when the corresponding package is deleted.
1.3 Handled issues
Jira code |
Issue code |
Description |
CEP-7754 |
32921 |
Distorted username issue in LDAP integration has been fixed. |
CEP-7854 |
33043 |
When editing a contact group it was impossible to go to the second page of the contact list. |
CEP-7954 |
33185 |
Reassign with SendNotifications false no longer sends mails to stakeholders |
CEP-7951 |
33136 |
Download button issue in Signer Portal has been fixed. |
CEP-7719 |
/ |
PDF versioning has been improved |
CEP-7884 |
/ |
Azure file storage token expiration issue has been fixed. |
CEP-7944 |
/ |
Error message when unsupported language is used with itsme has been improved. |
CEP-7073 |
/ |
Office 365 account linking issue has been fixed. |
CEP-7458 |
/ |
Modal background types issue in Theming has been fixed. |
CEP-7619 |
/ |
Ending a signing flow sent out the wrong email message. |
CEP-7683 |
/ |
Hyphen (-) was not supported in email address. |
CEP-7728 |
/ |
Contact group creation issue has been fixed. |
CEP-7895 |
/ |
Get Enabled Languages call has now been documented. |
1.4 Known issues
eSignatures 5.5.3
Jira code |
Issue code |
Description |
CEP-7554 |
/ |
Internet Explorer: Wrong color for signing method when choosing it for a Contact Group. |
eSignatures 5.5.2
Jira code |
Issue code |
Description |
CEP-7428 |
/ |
DOC: notificationCallback information needs to be updated to also include approvers. |
eSignatures 5.5.0
Jira code |
Issue code |
Description |
CEP-7078 |
/ |
It’s currently not possible to sign with FranceConnect using eIDAS3. |
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.
Server signing
- If a LegalNoticeCode or LegalNoticeText parameter in a Set Process Information call or InstantPackage Creation call contains placeholders, the original value of the legal notice and its placeholders will be added to the signature. Users cannot enter a value for the placeholder(s) since there is no user interaction with server signing.
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.5, consult the Connective - eSignatures 5.5.5 - Installation Documentation to learn how to upgrade it to version 5.5.