1. Release Notes - eSignatures 6.0.1
Release date: 2020-07-15
eSignatures 6.0.1 is the first production version of eSignatures 6.0.
1.1 New features
Single sign-on (SSO)
In our goal of having one account to access and manage all Connective solutions, a single sign-on authentication service has been put in place. eSignatures 6.0 is our first solution to use it.
Administrators can now handle their eSignatures user and user group management in the new Service Configuration Tool (SCT). When SSO is put in place, once a user is logged in to eSignatures, they won't be prompted for credentials when they try to access the WebPortal, the Config Index, the Branding settings, etc. At least, if they have been added to the required user groups that have access to those components.
In more advanced setups, clients can also use their own Identity Provider over OpenID Connect to link existing users and user groups to eSignatures. For more information about such a setup, contact Connective at service@connective.eu.
Connective SignID software
As of eSignatures 6.0, Connective SignID software is introduced to replace the Connective browser package.
In new eSignatures 6.0 installations, the environment settings are by default set to use SignID software. This means users will be prompted to install SignID software (for Windows and macOS) when they try to use any signing method that requires additional hardware.
Currently, the signing methods within eSignatures that require additional hardware are:
- eID and Manual+eID: both require an eID card reader
- BeLawyer: requires a transparent card reader
- Biometric: requires a biometric signing pad
Advantages of SignID software?
- No longer browser-dependent
- New smart cards can be added as signing method much more easily
Note however that the Connective Browser Package is still supported. In environments that were upgraded from a eSignatures version prior to 6.0, the Connective Browser Package (legacy) settings will still be used. So, users who have already installed the Browser Package will not be prompted to install SignID, and can continue using the Browser Package. If the eSignatures admin decides to switch to SignID in the future, the Browser Package plugins and signing extensions do not need to be uninstalled. Both the Browser Package and SignID can run on the same operating system.
API v4
API v4 is introduced as of eSignatures 6.0.
The main goals of API v4 are the following:
- Flexible creation and management of the different resources
- Easier implementation of new features
For a full explanation of the various API v4 calls, see eSignatures 6.0 - API v4 Technical Documentation.
Note that API v3 is still available for use but is considered deprecated. This means no new functionality will be added to API v3 and the routes will be removed once API v5 will be released. We therefore strongly recommend making use of API v4 both for new and existing integrations.
1.2 Improvements
Increased performance
A number of performance increases has been achieved in eSignatures 6.0.
Delete button in Signer Portal
Signers can now delete documents from their Signer Portal once they have been signed by all parties, or rejected by at least one. In previous versions only initiators could delete documents from their Document Portal.
Help buttons
The online user documentation can now be accessed via the Help buttons in the eSignatures WebPortal and WYSIWYS.
1.3 Removed features
The features that were marked as deprecated in previous versions of eSignatures have now been removed:
- API v2 is no longer available
- Template features have been removed and replaced by contact groups
- Deprecated notification callback properties have been removed
1.4 Handled issues
Jira code | Issue code | Description |
---|---|---|
CEP-7891 | / | Error message when signing field is missing has been improved. |
CEP-7890 | / | When adding an element to a document Page 0 was used by default instead of Page 1 when you didn't specify the Page parameter. |
CEP-7889 | / | Worker issue: callbacks were not working because of broken worker bus five. |
CEP-7888 | / | .svg logo of system theme was not correctly displayed. |
CEP-7886 | / | Packages did not reach the 'expired' status. |
CEP-7881 | / | WYSIWYS didn't open correctly in Internet Explorer. |
CEP-7878 | / | Uploading a PDF-a2a document caused a 500 error. |
CEP-7876 | / | Error message when changing a package's status to draft has been improved. |
CEP-7779 | / | Swagger currently used incorrect root URL. |
CEP-7683 | / | Hyphen (-) is now supported in email address. |
CEP-7987 | / | The scope https://connective.eu/claims/esignatures has been renamed to https://connective.eu/scopes/esignatures to match the convention used by our other applications. |
CEP-7983 | / | Users couldn't log in after migrating from eSignatures 5.5.x when IsAutomaticMembershipEnabled was set to false. |
CEP-7939 | / | Cloud contacts issue has been fixed. |
CEP-7936 | / | Document expiry date was not displayed correctly. |
CEP-7931 | / | BeLawyerId regex validation has been corrected. |
CEP-7942 | / | The WYSIWYS Help button did not open in a new tab. |
CEP-7921, CEP-7920, CEP-7906, CEP-7891, | / | Error messages are correctly displayed when incorrect API parameters are used. |
CEP-7910 | / | IDIN signing issue has been solved. |
CEP-7694 | / | WYSIWYS display issue for approvers has been fixed. |
CEP-7217 | / | DSS keypairs for itsme were not pushed automatically after upgrade. |
CEP-6944 | / | Deadlock on instant package creation has been solved. |
CEP-8031 | / | eSignatures used a mixed casing scheme to send out URIs. |
CEP-7988 | / | Runtime error when passing an unknown TenantId in the JWT access token to call the public API has been fixed. |
CEP-7947 | / | MTLS issue has been fixed. |
CEP-7944 | / | itsme signing issue when using an unsupported contact language has been fixed. |
CEP-7941 | / | Invalid TenantId error when upgrading to 6.0.1 has been fixed. |
CEP-7926 | / | The default Help URLs in the Config Index have been corrected. |
CEP-7233 | / | T1T error message issue has been fixed. |
1.5 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. |
eSignatures 6.0.0 (internal release)
Jira code | Issue code | Description |
---|---|---|
CEP-7699 | 32825, 32820, 32874 | Error message during itsme signing flow should be improved. |
CEP-6409 | 30654 | Error message when uploading a corrupt PDF should be improved. |
CEP-7667 | 32782 | Favicon in Internet Explorer and Edge shows Connective favicon instead of the client-specific one. |
CEP-7712 | / | A localization fallback for missing languages is currently not in place in the Notification Hub. |
CEP-7710 | / | No rollback on database call failure when uploading a package via the WebPortal. |
CEP-7046 | / | Mandated signing error message in WYSIWYS 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. |
CEP-8073 | 33364 | Approver reject reason is not visible in package that contains multiple documents |
eSignatures 5.5.0
Jira code | Issue code | Description |
---|---|---|
CEP-7078 | / | It’s currently not possible to sign with FranceConnect using eIDAS3. |
CEP-7667 | 32782 | Favicon in Internet Explorer and Edge shows incorrect icon |
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
- Version 4 of the API currently only supports mandated signing based on matchid in combination with contact groups, not with single contacts.
- 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.
2. Upgrade Information
If you have a version of eSignatures installed prior to version 6.0.1, consult the Connective - eSignatures 6.0.1 - Installation Documentation to learn how to upgrade it to version 6.0.