1. Release Notes 5.2.3
Release date: 2019-03-08
1.1 New features in eSignatures 5.2.3
eSignatures 5.2.3 is a hotfix version and doesn't contain new features.
1.2 Handled issues
Jira code | Issue code | Description |
---|---|---|
CEP-5529 | / | Sequential and complex signing mails received |
CEP-5528 | 29151 | Size check on signing fields configurable in web.config |
CEP-5521 | / | Audit proofs can be downloaded using the document correlationid |
CEP-5500 | / | Can’t download audit proofs when using a dss with a tenant setup and the main node has no default tenant. |
CEP-5536 | 29524 | Callbacks are triggered on status changes |
CEP-5489 | / | Revoking a package while the last signer is finishing his signing process no longer gives package status discrepancies. |
1.3 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 |
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. |
/ | / | German installation of Chrome can generate errors during signing. |
1.4 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.3, consult the Connective - eSignatures 5.2.3 - Installation Documentation to learn how to upgrade it to version 5.2.3.