/
eSignAnyWhere Release News

eSignAnyWhere Release News

This page shows the features with the respective versions. For detailed information about LTS (Long-Term-Support) please have a look at: eSignAnyWhere Release Policy
Current LTS version: 23.76

Explanation of Feature Release and LTS Release:

Feature Release: New functionality, lower priority fixes

Long-Term-Support-Release (LTS): 2 years of guaranteed hotfixes for critical bugs and Critical/High security findings.


Feature Release

eSignAnyWhere 24.52

Date: Planned February 2025 (already installed on demo)

We are excited to announce this release that brings a concentrated effort on stabilizing and enhancing existing features to deliver an even smoother user experience. Our primary goal with this release is to make your interactions with eSignAnyWhere more seamless.

  1. Stabilization of existing features: We have dedicated significant effort to stabilize and fortify the core functionalities you rely on every day. By addressing potential issues and optimizing performance, we aim to provide a more robust and dependable user experience. We have diligently worked on resolving various minor issues. This includes addressing bugs, enhancing error handling, and refining the overall user interface to smooth out any potential disruptions.
  2. Feature Improvement: In addition to stabilization, we have fine-tuned and improved several existing features. This ensures that the features are now even more user-friendly and efficient. 
  3. Preparing for upcoming LTS version: This release sets the groundwork for our upcoming Long-Term Support (LTS) version. By focusing on stability and fixing minor issues, we are laying a solid foundation for a LTS version that not only meets but exceeds your expectations in terms of reliability and performance.
 Whatsapp as additional notification channel

We are excited to announce the introduction of a new notification channel - Whatsapp! With this enhancement, users can now receive timely and convenient notifications directly through Whatsapp. Whether it`s important updates, reminders, processing, or completion, this addition ensures that users stay informed and engaged via one of the most widely used messaging platforms. This new channel is designed to improve communication, provide real-time updates, and enhance the overall user experience by offering a seamless and accessible way to stay updated.

For the new whatsapp notification channel two more feature flags are available:

  • AllowWhatsappNotification
  • BulkEnvelopesWithWhatsappNotifications

For more information about the feature flags please see: /wiki/spaces/eSign/pages/91992775

For more information about the configuration please see: Organization Settings and Whatsapp


Feature Release

eSignAnyWhere 24.49

Date: Planned December 2024 (already installed on demo)

Beside, focusing on stabilizing and improving existing features to make them even better to use, this release additionally introduces the following:

 Audit trails can be generated PDF/A-2B compliant

We are excited to introduce an enhancement to our platform: audit trails can now be generated in PDF/A-2b format.

PDF/A-2b is a standardized format specifically designed for long term digital preservation. It ensures that files remain accessible and visually consistent across devices and software. This compliance guarantees:

  • Preservation of visual integrity: Fonts, images and layouts are embedded to maintain fidelity.
  • Future-proofing: Files adhere to archival standards recognized globally.

Generating audit trails in a PDF/A-2b compliant format ensures:

  • Regulatory and legal compliance for industries requiring document preservation.
  • Enhanced trustworthiness of stored records.

This functionality is fully configurable in your organization settings. Administrators can enable PDF/A-2b compliance for audit trail generation, ensuring your documents meet the archival standards.

Administrators can set the default behavior either enabled or disabled in the Organization Settings, giving administrators control over how identification steps are handled within the organization. For detailed information please see the Organization Settings#Audit-Trail-Settings

In the Identity Providers section it is possible to add signature types the configured provider authorizes. For detailed information see Identity Providers

Per envelope it can be configured in the envelope settings please see Recipients Page.

 Late identification

We are excited to announce a new setting for allowing late identification, designed to provide greater flexibility and streamline workflows.

When the late identification is enabled, users can:

  • Open and read documents before identification: Users can review the document content without needing to complete the identification process upfront.
  • Identification performed at signing: The identification step will now occur only when initiating the signing process.

This feature provides a smoother experience for users who need to access document content before committing to the signing and identification process. Additionally flexibility:

  • For organizations or workflows that required identification before opening the document, this option remains available, as it has been supported prior to this release. This ensures you can tailor the process to your specific compliance or security needs.

For detailed information about the organization settings please see Organization Settings#Recipient-settings

 Removed Api version 3 and 4

As part of this release an of our ongoing commitment to streamline and enhance our platform, we are as announced in the API Migration Guides removing the api versions v3 and v4.
The 23.76 (published March 2024) will be the last LTS version that includes these API versions.


Feature Release

eSignAnyWhere 24.45

Date: November 2024

Beside, focusing on stabilizing and improving existing features to make them even better to use, this release additionally introduces the following:

 Relocation of Terms and Conditions

In this release, we have made UI improvement by moving the Terms and Conditions, Privacy and Api links to the "About" dialog. This change helps streamline the interface, ensuring essential information remains accessible while maintaining a cleaner and more organized design.


Feature Release

eSignAnyWhere 24.40

Date: October 2024

Beside, focusing on stabilizing and improving existing features to make them even better to use, this release additionally introduces following feature:

 Backup supports multiple zip and cloud storage

All supported storage types now include the capability for backing up envelope data. To enable a specific <storage> type for backups, ensure that the <usedFor> setting in the _gobal.xml configuration file is updated. This setting must include either "Backups" or "Everything".

The generated backup will be divided into multiple parts, allowing each part to be downloaded and extracted separately. The size of each uncompressed part can be customized by setting the uncompressedBackupPartSizeinMB parameter in the _global.xml under the path .../jobs/BackupJob/uncompressedBackupPartSizeinMB. By default this value is set to 1000 MB.

For more information about the backup feature please see Organization Settings#Backup

For detailed information about the configuration in the global.xml please see /wiki/spaces/eSign/pages/91883022 - restricted access


Feature Release

eSignAnyWhere 24.36

Date: September 2024 

Beside, focusing on stabilizing and improving existing features to make them even better to use, this release additionally introduces following features:

 Full support for disposable AML certificate type

The AML identification is now fully supported. All disposable document data fields

  • Document Type
  • Document Number
  • Document Issued On
  • Document Issued By
  • Document Expiry Date and Document Issuing Country

are optional. However, if any one of the document fields is provided, then all of them must be completed, with the exception of Document Issued By, which remains optional in all cases.

For more information about disposable certificate in general please see Electronic Signature Guide#DisposablecertificateRecipients Page and Signer Guide#Disposablecertificate

 Support for using data from eID assertions for disposable certificate signing

We are excited to introduce a new feature that streamlines the process of certificate issuance. Instead of manually providing data for disposable certificate issuance for each envelope, you can now leverage an eID assertion from an authorized eID service provider via OAuth authentication. This enhancement simplifies the workflow by using a single assertion across multiple envelopes.

Additionally, we have added a toggle option in the Identity Providers section, available when adding a new OAuth or editing an existing one. This toggle allows you to easily enable or disable the use of eID assertions for OAuth, giving you greater control over how eID assertions are managed within your system.

For more information please see the Identity Providers

 Support for multiple signature batches

You can now create custom batch groups, allowing you to specify which signatures should be grouped together and which should be in separate groups. Previously, it was only possible to define a single batch. With batch groups, a signer can sing multiple signature fields simultaneously within a defined group. This feature is available for both the UI and the API, giving you greater flexibility and control over the signing process.

For more information about the UI and multiple signature batches please see the User Guide#Batch-Signature and Signer Guide#BatchSignature.

For more information about the Api and multiple signature batches please see Envelope structure#TaskConfiguration


Feature Release

eSignAnyWhere 24.27

Date: July 2024

Beside, focusing on stabilizing and improving existing features to make them even better to use, this release additionally introduces following features:

 Prevent Actions on Signed PDFs

We are excited to introduce a new feature in the extended signing options section under Organization Settings: "Prevent actions on signed PDFs". This per-organization setting allows administrators to prevent any actions on already signed PDFs, addressing scenarios where signed documents should remain unaltered.

Key points:

  • Per-Organization Setting: This feature can be enabled or disabled for each organization, providing flexibility based on specific needs.
  • Protection for Signed Documents: Ensures that once a PDF is signed, no further actions can be taken, preserving it integrity.
  • No impact on existing Envelopes: This setting does not affect envelopes that have already been sent.
  • Global XML Configuration: The setting is also configurable via the global.XML for streamlined, centralized management.

This enhancement ensures greater control and security over your signed documents, maintaining their authenticity and integrity.

Recommendation: Disable “Default for: Prevent editing of form fields after envelope is finished“ when this setting is enabled!

 Instance-wide OAuth providers

We are excited to announce the addition of a new feature: Instance-Wide OAuth Provider MyNamirial. This enhancement allows administrators to configure a single OAuth provider for the entire instance, simplifying the authentication process for all users.

Key benefits:

  • Unified Authentication: Streamline login procedures by using a single OAuth provider across the instance.
  • Improved Security: Centralize authentication management to enhance security and compliance.
  • Easier Management: Simplify the configuration and maintenance of user authentication settings.


Feature Release

eSignAnyWhere 24.23

Date: June 2024

Beside, focusing on stabilizing and improving existing features to make them even better to use, this release additionally introduces following features:

 AML Disposable Type
Introducing of AML type for disposable certificate signing. We are excited to announce a new feature that integrates Anti-Money Laundering (AML) measures into the process of signing disposable certificates. This enhancement is designed to fortify security protocols and ensure compliance with AML regulations.
 P7M Document Visibility
We are pleased to introduce full support for document visibility in P7m signers.
 Increased Api v6 File Limit
We have increased the maximum number of files per envelope in Api v6 from 50 to 100. This significant enhancement provides greater flexibility and efficiency, allowing users to manage larger batches of documents within a single envelope. This update is particularly beneficial for organizations that handle high volumes of documents, streamlining their workflow and improving overall productivity.


Feature Release

eSignAnyWhere 24.19

Date: May 2024

Beside, focusing on stabilizing and improving existing features to make them even better to use, this release additionally introduces the following features:

 SMS notification

Introducing enhanced notification management with this release.

We have revamped our notification handling system to provide even more flexibility. Now, alongside emails, users can opt for phone number-based notification, expanding accessibility.

Please be aware that this feature requires updated notification plugins. Previous versions will no longer be compatible. Check out the corresponding release notes sections of the latest plugin versions. Please also see the /wiki/spaces/eSign/pages/91883022 for the URL shortener configuration.

Within the organization settings, you now have the option to choose between email or SMS for notifications. Additionally, you can customize the templates for SMS notifications in the notification templates section.

For more information please see the Organization Settings and Notification Template Settings.

Please also see the /wiki/spaces/eSign/pages/91992775. We added two new feature flags in order to use the new notification channel: AllowSmsNotification and BulkEnvelopesWithSmsNotification

 Reworked notification queue processing

We have overhauled our notification queue processing capabilities, enhancing efficiency and performance. Now, notification are managed with greater agility, ensuring timely delivery and smoother operations.


Feature Release

eSignAnyWhere 24.14

Date: April 2024

Beside, focusing on stabilizing and improving existing features to make them even better to use, this release additionally introduces the following features:

 Prevent using the last n passwords

We have introduced a new feature to prevent users and (admin-web admins) from updating or changing their password to a previously used one. The system now tracks a specified number of old passwords, which can be configured in the "passwordValidationRules" node under the "numberOfIldPasswordsWhichShouldNotBeMatched" setting in the globalXML.

This check applies to the following pages:

  • Reset Password
  • Reset/Change the automatically generated password

Additionally. the new configuration offers the following values:

  • Default: 8
  • Maximum: 20
  • Minimum: 0

Setting the value to 0 means that the system will not check for any old passwords, allowing users to reuse passwords they have used before. It is important to note that in the case of resetting or changing the automatically generated password, the system will always prevent the reuse of the same generated password.

 Document conversion supported file types

With the this release we have changed the list of supported types for the document conversion service. In detail the following types are no longer supported:

  • "ods",
  • "odp" or
  • "odt" filetpyes.

Following types are allowed:

  • .pdf
  • .docx
  • .xlsx
  • .pptx
  • .png
  • .bmp
  • .jpeg
  • .jpg
  • .doc
  • .xls
  • .ppt
  • .gif
  • .jp2
  • .tif
  • .txt
  • .xml
  • .md
 Tooltips adjustment

To enhance user experience. we have refined the tooltips below to provide clearer explanations of each setting's functionality:

For the definition/index page:


  • Recipient role
    • Needs to sing
    • Receives a copy
    • Must view
    • Needs to sign (P7M)
  • Recipient settings
  • Authentication settings
  • Signature settings
  • Remove recipient




LTS Release

eSignAnyWhere 23.76 ("24 LTS")

Date: April 2024

LTS version based on the feature release version 23.52.



Feature Release

eSignAnyWhere 24.10

Date: March 2024

Beside, focusing on stabilizing and improving existing features to make them even better to use, this release additionally introduces CIE signing, which refers to process of digitally signing documents or transactions using the Italian electronic identity card.

 Added additional document/identification types for Disposable Certificate signing (CIE)

New document types:

  • Residence Permit
  • Italian National Electronic Identity Card (CIE)
  • Temporary Residence Permit
  • Documents for Embassy/Consulate Personnel

New identification types:

  • Residence Permit
  • Temporary Residence Permit
  • Embassy/Consulate Personnel Document

For more information about the disposable certificate please see: Designer Page#DisposableCertificate, Electronic Signature Guide#Disposablecertificate and for an API use case: Envelope structure#DisposableCertificate

 FileBasedLocalCertificate

The FilebasedLocalCertificateGSP is a GenericSigningPlugin which allows applying a signature by using a local certificate, which is held by the signer and is available as files (.cer, .key):

Local File Based Certificate

Local File Based data



Feature Release

eSignAnyWhere 23.52

Date: February 2024

We are excited to announce this release that brings a concentrated effort on stabilizing and enhancing existing features to deliver an even smoother user experience. Our primary goal with this release is to make your interactions with eSignAnyWhere more seamless.

  1. Stabilization of existing features: We have dedicated significant effort to stabilize and fortify the core functionalities you rely on every day. By addressing potential issues and optimizing performance, we aim to provide a more robust and dependable user experience. We have diligently worked on resolving various minor issues. This includes addressing bugs, enhancing error handling, and refining the overall user interface to smooth out any potential disruptions.
  2. Feature Improvement: In addition to stabilization, we have fine-tuned and improved several existing features. This ensures that the features are now even more user-friendly and efficient. 
  3. Preparing for upcoming LTS version: This release sets the groundwork for our upcoming Long-Term Support (LTS) version. By focusing on stability and fixing minor issues, we are laying a solid foundation for a LTS version that not only meets but exceeds your expectations in terms of reliability and performance.

REST API /v3 and /v4 DEPRECATION: The 23.76 (published March 2024) will be the last LTS version that includes these API versions. By early June 2024, the REST API routes to v3/v4 will be deactivated on DEMO. Early December 2024, the REST API routes to v3/v4 will be removed from feature stream releases. Note that there is no date communicated yet to discontinue REST APIv5 (and where v5 refers to v4 routes, these will still remain); however we recommend to use the /v6 API specification already. Moving from v4 to v5 is anticipated to be a minimal change.
For further information please also see the API Migration Guides


Feature Release

eSignAnyWhere 23.49

Date: December 2023

Beside, focusing on stabilizing and improving existing features to make them even better to use, this release additionally introduces the following:

 Custom sealing certificates per envelope

With our latest update, users now have the flexibility to select a custom sealing certificate for individual envelopes. This enhancement extends beyond the previous organizational-level limitation, empowering users with greater control over the sealing process for each specific envelope. This means you can tailor the security measures to suit the unique needs of each document ensuring an even higher level of protection and customization.

This setting can be found on the Recipients Page in the section Envelope Settings. Please note that this feature is also available via API.

For more information please see: Custom Sealing Certificate

 Added general policies

With this release we have added the general policies for the viewer that dictate the actions and content accessible to the user on the Main Application Screen - SignAnyWhere Viewer (for the UI as well as for API v6). The following policies have been added:

  • Allow to save the document
  • Allow to save the audit trail
  • Allow to print the document
  • Allow to attach ad hoc pdf to the document
  • Allow to reject the document
  • Allow to undo the last step
 Digital Remote Signature feature flag

We are excited to introduce the "DigitalRemoteSignature" feature flag with this latest release. Therefore, we have added a layer of flexibility, allowing more selective activation of this feature to maintain a cleaner user interface. Additionally, for on premise, the configuration is now available on a per-organization basis, enabling the choice to enable or disable the Digital Remote Signature method.

By incorporating this feature flag, we empower organizations to fine-tune their signing preferences according to their specific requirements, ensuring a more personalized and streamlined experience.

Please also see: /wiki/spaces/eSign/pages/91992775

 Override Localizations

Introducing the latest feature: "Activity-Engine Custom Localizations" within the organization settings. This setting allows you to override localizations, enabling customization for various elements such as signature image rendering labels and text for transaction code configuration (e.g. SMS text). You now have the ability to upload a translation bundle, reset to default settings, download the current translation bundle, and also access the default template for localizations. This feature empowers users to tailor their interface and messaging precisely to their preferences, ensuring a seamless and personalized experience.

Precondition is the following feature flag: /wiki/spaces/eSign/pages/91992775


Feature Release

eSignAnyWhere 23.45

Date: November 2023

Beside, focusing on stabilizing and improving existing features to make them even better to use, this release additionally introduces the following. With these exciting updates, you will experience a platform that not only offers a more captivating visual experience but also provides you with greater control and insights into your organization's operations. It is time to embrace the benefits of these enhancements and take your user experience to the next level:

 New Color Scheme - A modernized UI in flat look and UX with optimized mouse interaction aims for enhanced accessibility support

Get ready for a visual transformation as we introduce a captivating new color scheme that revolves around the enchanting primary color, teal. This change marks a departure from the previous purple theme and brings a fresh, invigorating look to our platform. The advantages of this recoloring are not just cosmetic, it enhances user experience, making your interactions more engaging and visually appealing.

Please also see: UI/UX Rework - New Color Scheme 2023

 Enhanced Custom Organization Sealing Certificate Configuration - Unleash the Potential
In this release, we are thrilled to introduce a feature that gives you more control and flexibility over your document sealing processes. With the new "AllowUsingCustomSealingCertificate" feature flag, you can now seamlessly enable or disable the configuration of a specific sealing certificate for each organization. This update not only streamlines your operations but also ensures that your organization's unique needs are met.
Please also see: /wiki/spaces/eSign/pages/91992775
 Envelope History - Gain Deeper Insights and Benefits
We have taken a significant step to enhance your observability with the introduction of our new Envelope History feature. This feature is designed to provide you with comprehensive insights into the events related to an envelope, as well as detailed information on any events that may have encountered issues. The advantages are clear:
  • User Event History Access: With this permission, users can delve into the event history of an envelope, gaining valuable insights and control over the process.
  • Anonymized Organization Envelope History: This permission empowers users to access anonymized history data for any envelope within their organization, ensuring that you have the data you need while maintaining privacy and security.

You can find both permissions in the "Roles and Permissions" section.

Please note that this feature is also available via api with the following call:
GET /v6/envelope/{envelopeId}/history

Please also see: Envelope History


Feature Release

eSignAnyWhere 23.40

October 2023

Beside, focusing on stabilizing and improving existing features to make them even better to use, this release additionally introduces the following:

 TypeToSignSignature feature flag

We are pleased to announce the introduction of a new feature flag, "TypeToSignSignature", with this release. This feature flag brings forth notable implications for both existing and new organizations. Existing organizations as well as new organizations will have access to the TypeToSign signing method. However, we now offer the added flexibility of being more selective in activating this product feature to keep the UI a bit more clean. Furthermore, on-premise customers can configure on a per-organization basis if they want to allow TypeToSign signing method.

By implementing this feature flag, we empower organizations to tailor their signing preferences to their specific needs, ensuring a more customized and efficient experience.

For further details, please refer to /wiki/spaces/eSign/pages/91992775.

 Organization specific timestamp

We are pleased to introduce a new feature flag to allow an organization specific timestamp - "AllowUsingCustomTimestampService". This feature allows you to set a dedicated timestamp service for each organization. With "AllowUsingCustomTimestampService", you gain the ability to fine-tune timestamp configurations on a per-organization basis. This means that it is now possible to customize timestamp services to meet the specific needs of each organization in your instance, ensuring that timestamps align perfectly with their unique requirements. This feature provides enhanced control and flexibility, making timestamp management more precise and adaptable across your entire instance.

Please also see /wiki/spaces/eSign/pages/91992775 and the Organization Settings

 OAuth configuration enhancement

We are excited to introduce new configuration options for OAuth in this release. You now have the flexibility to control how OAuth values are compared, whether it's case sensitive or not. Specifically, for the Signer OAuth Provider, the following comparison modes are additionally available:

  • Validate (respect case): OAuth values will be validated with strict case sensitivity.
  • Validate (ignore case): OAuth values will be validated while ignoring case differences.

OAuth Configuration Validation

This enhancements offer greater control and customization, ensuring your OAuth integration is tailored to your exact needs.

For general information about OAuth please refer to OAuth2 Authentication Reference and for samples OAuth2 Authentication Samples.


Feature Release

eSignAnyWhere 23.36

Date: September 2023

Beside, focusing on stabilizing and improving existing features to make them even better to use, this release additionally introduces the following:

 DrawToSignSignature feature flag

We are pleased to announce the introduction of a new feature flag, "DrawToSignSignature", with this release. This feature flag brings forth notable implications for both existing and new organizations. Existing organizations as well as new organizations will have access to the DrawToSign signing method. However, we now offer the added flexibility of being more selective in activating this product feature to keep the UI a bit more clean. Furthermore, on-premise customers can configure on a per-organization basis if they want to allow DrawToSign signing method.

By implementing this feature flag, we empower organizations to tailor their signing preferences to their specific needs, ensuring a more customized and efficient experience.

For further details, please refer to /wiki/spaces/eSign/pages/91992775.

 Backup feature flag

We are pleased to announce the introduction of a new feature flag, "Backup", with this release. This feature flag brings forth notable implications for both existing and new organizations. Existing organizations as well as new organizations will have access to the Backup feature. We believe in giving our users the ultimate control and flexibility in managing their document workflows. With this feature flag, you now have the power to enable or disable the "Backup" envelopes functionality based on your specific needs and preferences. In addition to its control benefits, this flexibility also contributes maintaining a clean and streamlined user interface. Furthermore, on-premise customers can configure on a per-organization basis if they want to allow "Backup".

For further details, please refer to /wiki/spaces/eSign/pages/91992775 and Organization Settings#Backup.

 Notification Plugin

We are excited to announce some significant improvements to our notification settings that will elevate your experience with our platform. To provide more clarity and organization, we have moved relevant notification settings into a dedicated <notificationSettings> node, ensuring easier access and management.

Here are the key changes you need to be aware of:

  1. Move Notification relevant settings
    1. We have streamlined the location of notification settings for a smoother user experience. They can now be found within the <notificationSettings> node, making it more intuitive to customize your preferences.
  2. Renaming <mailAttachmentDonwloadsExpireDays> to <attachmentDownloadsExpireinDays>

    1. To enhance consistency and understanding, we have renamed this settings. Please note that the functionality remains the same, we simply improved the naming for better clarity.
  3. Change from single <emailNotificationSetting> to a list of <notificationPlugins>
    1. We are excited to introduce a powerful change that will allow you to configure multiple <notificationPlugin> instances rather than just a single one. This enhancement empowers you to have more granular control over your notification services.

For each node in the <notificationPlugins> list please take note of the following:

  1. CUSTOM_PLUGIN_ID must be set and needs to be unique on the instance
  2. Exactly one plugin must be marked as default (<notificationPlugin customPluginId="CUSTOM_PLUGIN_ID isDefault="1">)

  3. Mail providers which previously called <FLOW_WEB_URL>/WebHook/Email to report status updates (bouncing), now need to call  <FLOW_WEB_URL>/WebHook/Email/CUSTOM_PLUGIN_ID with the same payload as before
  4. Custom plugin implementations need to be adapted to follow the new format (nuget Namirial.Plugin.Notification 23.30.0.4)


Configuration changes can be found here: