An overview of the most important new functionality, changes and resolved issues in ValidSign between 8 and 14 October 2026.
New functionality
The table below lists the new functionality that becomes available with this release.
| Functionality | Component | Description |
|---|---|---|
| Attachments in the archive | PLATFORM Accounts with archiving |
A transaction archive now also contains the attachments uploaded by signers, in addition to the documents and the evidence summary. |
Changed functionality
The table below lists existing functionality that has been changed in this release.
| Change | Component | Description |
|---|---|---|
| Create an archive from a delegation | PLATFORM Users with delegations |
Before: an archive could not be created while working on behalf of another account. Now: you can also create an archive from a delegation. The archive belongs to the account you are acting for. |
| Environment shown in emails from test environments | PLATFORM Users of the test environment |
Before: emails, such as the password-expired notice, did not show which environment they came from. Now: emails from a test environment (for example try) state which environment they concern. Emails from production are unchanged. |
| Subsequent signatures by the same person | PLATFORM Users with delegations |
Before: for a signer with multiple signatures, the signer and a delegate could take over from each other halfway through. Now: whoever places a signer's first signature also places the next ones. Switching between signer and delegate is rejected and the signature stays open. |
| Events when signing with a hardware token in an iframe | FRONTEND Integrations that embed the signing page |
Before: when signing with a certificate (Token Reader) in an iframe, the host application received no message and did not know the document was signed. Now: the signing page sends messages when hardware-token signing starts, succeeds or fails, as with other signing methods. |
| Clearer error messages | FRONTEND All users |
Before: some error messages, for example on upload, transaction settings and conditional fields, appeared as a technical code or a generic message. Now: these messages are shown translated. If no translation exists, you see the message returned by the server. |
Bug fixes
The table below lists the issues resolved in this period.
| Subject | Component | Description |
|---|---|---|
| Confirming your own signature | PLATFORM | A signer who had already signed a document sometimes could not confirm it and got an error, depending on how the transaction was opened. A signer can now always confirm their own signature. |
| Document data not kept on changes | PLATFORM | Additional data passed to a document through the API (data) was cleared when the document was later renamed or reordered. This data is now kept. |
| Group transactions in other subaccounts | PLATFORM | Group members only saw a transaction sent to their group while the subaccount it was sent from was selected. The transaction is now visible and counted under To sign, whichever subaccount is selected. |
| No more expiry email for transactions in the trash | PLATFORM | For a sent transaction that had been moved to the trash, the email saying the signing request had expired was still sent after the expiry date. That email is no longer sent. |
| Thin lines in uploaded signatures in PDF/A | PLATFORM | An uploaded signature (transparent PNG) lost its thin lines in PDF/A documents, so the signature looked broken or dotted. The signature is now rendered in full and the document stays PDF/A. |
| Declined transaction in Recent transactions | FRONTEND | For a declined transaction, the icon of the signer who declined stayed blue. The icon is now red and the decline reason is shown, also in the transaction overview. |
| Managing delegations during an active delegation | FRONTEND | While working on behalf of another account, the Manage delegations window showed a search field that did nothing. The window now shows the current delegation and the available actions. |
| Default value of the previous field in the designer | FRONTEND | After switching fields in the designer, the Default value box could still show the value of the previous field. A field without a default value now shows an empty box. |
