An overview of the most important new functionality, changes and resolved issues in ValidSign between 29 October and 5 November 2026.
New functionality
The table below lists the new functionality that becomes available with this release.
| Functionality | Component | Description |
|---|---|---|
| Set a Reply-To address for invitation e-mails | PLATFORM Organisations that want to receive replies to invitation e-mails |
When a signer replied to an invitation e-mail, the reply went to the general ValidSign sender address. A separate Reply-To address can now be set per account in the e-mail settings, so replies to e-mails from the account reach your own department directly. |
| Follow progress in a transaction with a signing order | PLATFORM Signers within the same account |
In a transaction where signers take turns, a signer who was not yet up could not see the transaction. Signers within the same account can now follow the progress on the dashboard and see who has already signed and who is still to come. They only get access to the document once it is their turn. |
| Accessible signature field in the signed PDF | PLATFORM All users, especially organisations with accessibility requirements |
The signature field in the signed PDF now has an accessible name and a correct structure for screen readers, in line with PDF/UA. Assistive software therefore recognises the field as a signature field. |
Changed functionality
The table below lists existing functionality that has been changed in this release.
| Change | Component | Description |
|---|---|---|
| Downloading documents without extra memory use | PLATFORM All users, especially with large documents |
Before: When a document or package was downloaded, the whole file was first loaded into the memory of the server, so large downloads put a heavy load on the server. Now: Documents and packages are streamed directly while downloading. The download works the same, but puts considerably less load on the platform. |
Bug fixes
The table below lists the issues resolved in this period.
| Subject | Component | Description |
|---|---|---|
| Resending with an expired end date | PLATFORM | Resending a declined transaction with an end date in the past returned a success response through the API, after which the transaction expired within a minute. The end date is now checked when sending and updating, and a date in the past is rejected with an error message. |
| Send validation with more than 10 documents | PLATFORM | Only the first 10 documents were checked when sending. If the document to be signed was in position 11 or later, the error that at least one document needs an approval was returned incorrectly. All documents are now included in the check. |
| Inherited role from a parent account | PLATFORM | From a sub-account, retrieving the users of a role inherited from the parent account returned a server error. The role is now resolved correctly and the users are returned. |
| Link from the completion e-mail with SSO login | PLATFORM | Users who log in through SSO landed on the dashboard instead of their transaction after clicking Download documents in the completion e-mail. The link to the transaction is now preserved during login. |
