1. Release Notes - eSignatures 6.1.0
Release date: 2020-07-31
1.1 New features
Download Audit Trail
Prior eSignatures versions already supported the Audit Proof, an XML that can be downloaded through the API that keeps track of all actions taken on a package. With eSignatures v6.1.0, we added the notion of the Audit Trail. The Audit Trail is a pdf that can be downloaded from within the Document Portal or through the API. The Audit Trail contains the actions taken for that package and can be downloaded when the package is in a final state.
Note:
- The Audit Trail feature must have been enabled in the Config Index by your system administrator
- The 'Download Audit Trail' is a user permission that must be granted to your document group by your system administrator
Below an example of the Audit Trail
1.2 Improvements
Audit Proofs / Trails added to the counters
For improved granularity in the counters, Audit Proofs and Audit Trails have been added as a separate counter.
1.3 Handled issues
Jira code |
Issue code |
Description |
CEP-7046 |
/ |
Changed the not mandated to sign error message |
CEP-8086 |
/ |
Fixed issue where sms/mail OTP codes were doubled in the signature |
CEP-8123 |
/ |
Theme code numbering incorrect |
1.4 Known issues
eSignatures 6.0.1
Jira code |
Issue code |
Description |
CEP-8064 |
/ |
Preview button is not displayed on WYSIWYS tab in Theme section of the Config Index. |
CEP-8056 |
/ |
When IsAutomaticMembershipEnabled is disabled and a user who has been invited to log in, clicks the invitation link while already being logged in with another account in the same browser (for instance as initiator who sent the invitation link), they will not be able to log in, and the login of the other account will no longer work either. |
CEP-6409 |
30654 |
Error message when uploading a corrupt PDF should be improved. |
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.2
Jira code |
Issue code |
Description |
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.6 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.
- Adding multiple initiators within a single package is not supported.
- 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.
- 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.
- When using itsme signing, the document and package names must only contain characters that are part of ISO 8859-15. This character set supports most usual characters, but some software-generated characters like curly apostrophes and long dashes are not supported.
- Itsme signing is currently not supported on macOS Mojave v10.14 combined with Safari v12.0.
Mandated signing
- When using API v4, mandated signing based on matchid can only be used with group stakeholders, not with person stakeholders.
Mandated signing based on nameandbirthdate can be used with all types of stakeholders in API v4.
- The mandated signing settings that have been configured on environment level in the Config Index cannot be overwritten using API v4 calls.
So, if your environment requires mandated signing based on matchid and you're using our API, it's strongly recommended to use version 3.
If you have a version of eSignatures installed prior to version 6.1, consult the Connective - eSignatures 6.1 - Installation Documentation to learn how to upgrade it to version 6.1.