1. Release Notes - eSignatures 6.2.0
Release date: 2020-09-11
1.1 New features
Configurable signing behaviors and signing methods
In eSignatures 6.2 the concept of fixed signing types has been replaced by configurable signing behaviors, which each may contain multiple signing methods.
The signing behavior Smartcard signing, for instance, may contain the signing methods BeID signing and BeLawyer signing. The signing behavior OpenID Connect may contain the signing methods France Connect and Itsme login, etc.
In future versions, more Smartcard signing methods, such as LuxID, will be supported.
Configurable mandated signing rules
In eSignatures 6.2, the concept of configurable mandated signing rules is introduced.
In previous versions mandated signing could only be done based on matchid or based on nameandbirthdate. In eSignatures 6.2, you can configure custom mandated signing rules and apply them to any contact field of your choice. This may be a default contact field, or an additional contact field you’ve created. Once mandated signing rules have been configured, you can choose which ones must be applied to a certain signing method. Notice that you can apply multiple rules to a single signing method.
Delayed deletion of Audit Proofs
In eSignatures 6.2, the audit proofs of a package are no longer automatically deleted when the package is deleted. Instead, you can configure a Delayed Deletion Time in the Config Index and determine after how many days the audit proofs must be deleted once the package is deleted.
In API v4 you also have two new audit proofs calls:
- Get Audit Proof Info, to retrieve the audit proofs info of a (deleted package)
- Deleted Audit Proofs, to manually delete audit proofs (and override the delayed deletion configured in the Config Index)
1.2 Improvements
N/A.
1.3 Handled issues
Jira code | Issue code | Description |
---|---|---|
CEP-8358 | / | iDIN redirect from bank site resulted in an expired token page. |
CEP-8262 | / | Error when retrieving the audit trail in a non-existent language. |
CEP-8064 | / | Preview button is now displayed on WYSIWYS tab in Theme section of the Config Index. |
CEP-8085 | / | Package stuck in pending status issue has been solved. |
CEP-8192 | / | Signature audit trail overlapping issue has been fixed. |
CEP-8209 | / | Reassign issue with missing eID mandated firstname has been fixed. |
CEP-8213 | / | Incorrect username issue has been fixed. |
CEP-8316 | / | Signing issues fixed for IE |
CEP-8240 CEP-8239 CEP-8238 CEP-8237 CEP-8236 CEP-8235 CEP-8234 CEP-8233 CEP-8232 CEP-8231 CEP-8230 CEP-8227 |
/ | Error code corrections in API v3 |
CEP-8199 | / | Incorrect Swagger redirect has been fixed. |
CEP-8057 | / | iDIN date inconsistency has been fixed. |
CEP-7994 | / | Merge issue with empty contact properties has been fixed. |
CEP-7080 | / | Creating many OIDC profiles slowed down the creation of signing fields. |
CEP-6865 | / | Upgrade issue from versions prior to 5.4.2 has been fixed. |
1.4 Known issues
eSignatures 6.2.0
Jira code | Issue code | Description |
---|---|---|
CEP-8322 | / | iDIN signing issues with long legal notice. |
CEP-8367, CEP-8370 | / | Mandated signing rules issue with OpenID Connect |
CEP-8371 | / | SMS OTP throttling error |
CEP-8372 | / | Incorrect naming of old SigningTypes when retrieving all signing methods through the API. |
CEP-8077 | / | Incorrect error message when mandated signing with eid is set to 'nameandbirthdate' and the birthdate is missing for the members. |
CEP-8288 | / | Users are not automatically added to the default user group. |
eSignatures 6.1.1
Jira code | Issue code | Description |
---|---|---|
CEP-8252 | / | Validation issues with Api V3 |
eSignatures 6.1.0
Jira code | Issue code | Description |
---|---|---|
CEP-8219 | / | Reassign error |
eSignatures 6.0.1
Jira code | Issue code | Description |
---|---|---|
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.
iDIN signing
- Avoid using long legal notices combined with iDIN signing, especially when sending packages through the API. If long legal notices are used, the MerchantUrl exceeds its maximum number of 512 characters.
Mandated signing rules
- The mandated signing rules that have been configured in the Config Index cannot be overwritten using API v4 calls.
2. Upgrade Information
If you have a version of eSignatures installed prior to version 6.2, consult the Connective - eSignatures 6.2 - Installation Documentation to learn how to upgrade it to version 6.2.