A new “Restart Envelope” event has been introduced alongside performance optimizations for the notification queue and finished‑envelope backups. These changes help integrated systems react more precisely when an envelope is restarted, make notification handling and backup processing more efficient even at high volumes, and ensure a more consistent visual result for approver signatures (ClickToSign) by avoiding stamp imprint customizations.

Pre‑authentication is now used for Workstep Controller (WSC) management calls, improving the security of administrative operations and providing a more robust foundation for managing signing workflows in complex environments. In addition, core viewer and SDK components have been updated to current versions, ensuring continued compatibility with supported document formats and incorporating the latest vendor fixes.

Some identity providers and use cases do not rely on a phone number for secure identification. In previous versions, a phone number was typically required when configuring certain eID options.

In 26.8 it is now possible to configure an eID without a phone number:

• This supports scenarios where a phone number is not needed or not available.

• It helps you adapt eSignAnyWhere to a broader range of identity providers and regulatory environments.

• It can simplify onboarding for recipients who prefer not to share their mobile number.

This provides more flexibility when setting up your signing and identification flows, especially in markets with specific data‑minimization requirements.

New options to simplify the signing experience
With API v6, we have introduced new settings that let you control how the signing screen looks and behaves for each recipient.

In practice, whoever configures the document sending can now decide:

1. What happens at the end of the signing process

   1. You can hide the download window that appears at the end of the process, so the flow closes in a more linear and simple way.

   2. The system can automatically close the session as soon as all required signatures and mandatory fields have been completed, without any extra clicks from the user.

2. How much guidance to give to the signer

   1. The on screen guidance (through signatures, text fields, etc.) can start automatically as soon as the document is opened.

   2. You can configure the guidance to:

      • guide the user only through required fields

      • guide them through both required and optional fields

      • turn guidance off completely, letting the signer move freely in the document.

These options make it possible to adapt the signing experience to each process:

• more guided and faster for less experienced users or critical flows

• more flexible for advanced users or less strict scenarios.

Improved traceability for signatures created from text labels (SigString)

When preparing a document using text labels inside the PDF (SigString) to mark where signatures should be placed, the system now clearly indicates which label created each signature field.

This makes it easier to:

• understand how signature fields are placed within the document

• check and troubleshoot SigString-based configurations

• generate clearer logs and reports for auditing and analysis purposes

Optimizations for large-document handling maintain responsiveness during peak activity, delivering faster envelope preparation and shorter overall processing times in high‑volume scenarios.

API v5 now supports CAdES signatures, enabling their preparation and application via the API and expanding signature options for integration‑driven workflows.

The recipient language within envelope drafts can now be updated when a language is deactivated at the organization level, ensuring accurate localization handling.

This enhancement introduces push notifications for signing documents, allowing users to receive alerts and sign envelopes directly within the app for a smoother and more convenient signing experience. Stay tuned for the next generation of apps, which may leverage on this feature!

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: Feature Flags

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

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.

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

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.

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.

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 GlobalXML - restricted access

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#Disposablecertificate, Recipients Page and Signer Guide#Disposablecertificate

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

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

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.

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.

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.

We are pleased to introduce full support for document visibility in P7m signers.

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.

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.

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 Feature Flags. We added two new feature flags in order to use the new notification channel: AllowSmsNotification and BulkEnvelopesWithSmsNotification

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.

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.

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

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

For the definition/index page:

Open

• Recipient role

  • Needs to sing

  • Receives a copy

  • Must view

  • Needs to sign (P7M)

• Recipient settings

• Authentication settings

• Signature settings

• Remove recipient

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

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):

Open

Open

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.