Nitro regularly releases updated products with new features, enhancements, and bug fixes.
Latest version: 7.3.0
Release date: 2023-01-31
Discover eSignatures 7.3.0 new features and check fixed issues.
New features and improvements
Signer application has a new look
The Signer application has been revamped to offer you a better user experience.
Enhancements to themes
Updates to default themes
The Connective theme has been replaced with the Nitro theme that uses new branding colors. In the new installations, the System theme will have the same styles as the Nitro theme.
New Theming tool
With the Theming tool, the administrator can easily customize themes and instantly preview how they look in the Signer application.
The administrator can download the customized theme as a .json file and, to start using it in your eSignatures environment, upload it in the Configuration Index. The same .json file can be used to update multiple themes.
Changes to Theme settings
The WYSIWYS settings have been simplified. Instead of configuring the color for each component in the Page and Modal settings, you can now indicate Brand and Status colors that will be automatically applied to multiple components.The Redirect page tab has been removed. In the new installations, the Redirect page will use the Main color code configured in the WYSIWYS settings.
For the upgrade to eSignatures 7.3.0, we carefully process your customized themes to preserve your settings. However, in the redesigned Signer application, they can look different. That's why we recommend that, after the upgrade to eSignatures 7.3.0, the administrator reviews themes and, if needed, finetunes them with the Theming tool or in the WYSIWYS settings.
Improved manual signing
Previously, with the manual signing method, you could add a signature only by drawing or by typing it. Now, you can also add your signature by uploading an image.
If you upgrade to eSignatures 7.3.0, only previously used options for manual signing are enabled (for example, only the Type option). The administrator can enable additional options in Configuration Index > Configuration > Signing Options Settings. Prior to 7.3.0, in these settings, the administrator could select Mouse or Keyboard as an input type. As of 7.3.0, the Draw, Type, and Upload input types can be enabled at the same time.
The old options are mapped to the new ones as follows:
|Prior to 7.3.0||As of 7.3.0|
The administrator can define maximum size of a signature image for the Upload option in manual signing by using the new parameter MaximumSignatureImageSize that has been added to Configuration Index > Configuration > Signing Options Settings.
External reference for contacts and contact groups
The new External reference field is available when creating or editing contacts and contact groups. This parameter can be used to correlate a contact or a contact group in eSignatures to relevant information in a third-party application.
Support for Microsoft Exchange Online
You can configure Microsoft Exchange Online as a mail sender type and use Graph API to connect your applications.
New parameter for Counter API
The new SubmittedThroughApi parameter is now available to filter results based on how a package was submitted.
|Jira code||Issue code||Description|
|CEP-12264||/||Fix to asynchronous signing after the rollback.|
|Fix to redirect to the F2FURL created via API when a package was rejected in the Signer application during a face-to-face signing session.|
|CEP-12244||/||Fix to migrate all files with StorageMigrator.|
|CEP-12194||/||Fix to correctly display long names of signing methods.|
|CEP-12181||/||Fix to a transaction exception in Australian environments.|
|CEP-12166||00026251||Fix to prevent the wrong navigation and unnecessary auto-refresh of the pages in the Signer Portal.|
|CEP-12148||/||Fix to preserve markers in PDFs when creating a template.|
|CEP-12135||/||Fix to the Add document to package call in API v4 that was failing to parse the list of SigningMethodWithKeypair objects.|
|CEP-12063||/||Fix to retrieve packages with the Failed status via API v4.|
|CEP-12051||/||Fix to reset a password for a virtual root when multiple virtual roots are configured.|
|CEP-12030||00025349||Fix to display the correct date when a signature was added in the Signer application.|
|CEP-12010||00025374||Fix to show details of package templates in the Document Portal.|
|CEP-11948||/||Fix to show a clear error message if signing with email OTP fails.|
|CEP-11883||/||Fix to refresh templates when another documentation group is selected.|
|CEP-11864||/||Fix to correctly show signatures added with itsme after the rollback.|
|CEP-11657||00020954||Fix to make the Close this session button visible on the white background.|
|CEP-11650||/||Fix to remove alternative group names regardless of used characters.|
|CEP-11145||/||Fix to allow users to access the drag and drop action URL when they are not logged in.|
|CEP-10838||/||Fix not to block a tenant creation when the virtual root uses an IP or loopback address.|
|CEP-10205||00012223||Fix not to change locations if the package status is set to Pending via API v3.|
Latest version: 7.2.0
Release date: 2023-01-31
Discover eSignatures 14.2.0 new features and check fixed issues.
Configure certificates for signing methods
In the DSS Settings tab in the Configuration Index, you can now define certificate-related keypairs for each signing behavior. When creating a package in the Document Portal or Template Portal, the initiator clicks on the signing behavior of their choice and then has a drop-down list to choose between the keypairs that have been made available in the DSS Settings tab in the Configuration Index.
After a package has been submitted in the Document Portal, initiators (and not only signers or other actors) can intervene by reassigning a package to a different stakeholder while the package is pending.
Related to the actor reassignment feature for initiators, new notifications are available.
For the initiator, the following new notifications are sent when a document is reassigned:
For stakeholders, the following new notifications are sent when a document is reassigned.
File size optimization
A new configuration setting “IsOptimizeFileSizeEnabled” is available in the “Signing Format Settings” tab. It enables or disables file size optimization during PDF to PdfA1A or PdfA2A conversion. It is disabled by default. When enabled, file size is reduced, although this may impact performance.
Correlate audit trail with signed documents
For signed documents, downloaded packages now include the applicable package ID and document ID at the end of the legal notice, specifically for signing fields.
Jira code Issue code Description CEP-9066 / Fix in Signer Portal to enable multiple bulk signings. CEP-9306 / Fix for size of tables leading to filling up table quota. CEP-11041 / Fix in API v4 for placing unplaced elements via param Id or unplacedElementsId. CEP-11097 / Fix to remove several deprecated Microsoft (Azure) libraries. CEP-11170 / Fix to allow eSignatures to check headers before client certification. CEP-11279 00021048 Fix to RedirectURL in API v4 to avoid data being omitted after the #. CEP-11323 / Fix to upgrade to new version of client-side encryption in Azure Storage SDK. CEP-11530 / Fix to mark SMTP password field as password field. CEP-11711 / Fix to F2F itsme so that WYSIWYS asks to change to last signer. CEP-11715 / Fix to Configuration Index to enable saving changes in the Signing Options Settings. CEP-11728 / Fix to CleanTokensCommand timeouts on Azure databases. CEP-11758 00022450 Fix to follow default setting of environment when certain settings are set to null. CEP-11766 / Fix in package created from template having a random order of documents. CEP-11879 / Fix to remove readline at end of migrator to allow automation. CEP-11885 00023612 Fix to timeouts during PDF conversions. CEP-11890 / Fix to API v3 to enable creation of instant packages.
Jira code Issue code Description CEP-8766 / Cannot sign mandated with birthdate using LuxID.
Jira code Issue code Description CEP-8541 / Preview issue in Config Index Theme section. CEP-8543 / PDF preview of optional documents is off center on mobile devices.
Jira code Issue code Description CEP-8371 / SMS OTP throttling error
- 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 file 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.
- 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 Document Portal) 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.
- 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.
Uploading PDF/A documents to which you add form fields in eSignatures API v4 breaks the "/A" part of the PDF. As a result, the documents end up a regular PDF.
As a workaround, you must set the TargetFormat parameter in the POST document call to PDF/A_1A or PDF/A_2A (depending on the source format). The breaking will still happen but after all form fields have been filled or saved, the document will be converted to the set target format, resulting in a PDF/A document again.
(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_1A or PDF/A_2A. 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.
- 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.
- When using Swisscom signing, the AdditionalSpace value under DSS > General Settings > PaDES Settings must be set to 20000 in the eSignatures or DSS Configuration Index (depending on the one you are using).
- When using Swisscom signing in packages, each document within the package must be signed individually, which means QuickSigning is not supported.
Mandated signing rules
- The mandated signing rules that have been configured in the Config Index cannot be overwritten using API v4 calls.
- When using LuxID, only mandated signing rules based on FirstName and LastName can be used.
It may occur that Download notifications are still handled like spam / read by URL protection software, even after whitelisting them.
As a workaround, mail recipients must add the URL to the Microsoft Office 365 Advanced Threat Protection (ATP) Do not rewrite the following URLs list.
Audit proofs / Audit trails
Certigna certificates are not supported in combination with Audit proofs or Audit trails. If Audit proofs and/or Audit trails are required in your environment, you need to use other certificate types.
If you have a version of eSignatures installed prior to version 7.2.0, consult the Connective - eSignatures 7.2.0 - Installation Documentation to learn how to upgrade it to version 7.2.0.
Latest version: 7.2.0
Release date: 2023-01-31
Discover eSignatures 14.2.0 new features and check fixed issues.