An overview of the most important new functionality, changes and resolved issues in ValidSign between 22 and 29 October 2026.
New functionality
The table below lists the new functionality that becomes available with this release.
| Functionality | Component | Description |
|---|---|---|
| A separate name per transaction in a bulk send | PLATFORM Senders who use bulk sending |
Transactions created from a bulk file all carried the name of the template, which made them impossible to tell apart in the transaction list. The new optional column TRANSACTION_NAME gives every row in the CSV file its own transaction name, for example a contract number or an employee name. The transaction can then be found in the transaction list, in reports and through the API. If you leave the column out, the template name still applies. |
| Administrators can reset two-factor authentication | PLATFORM Administrators |
When a user can no longer use two-factor authentication, the request went to the account owner only, and only the owner could switch two-factor authentication off. With the new two-factor management permission, administrators who hold that permission receive the notification as well and can switch off two-factor authentication for a user. You grant the permission through role management. |
| Validation on text fields | FRONTEND Senders who use form fields |
In the designer you can now pick a validation type on a text field, starting with Dutch IBAN. If the signer enters a value that does not match the format, they get a readable message in their own language instead of a technical error code. The available validation types come from the platform, so new types appear in the list automatically. |
| More control over the embedded designer | FRONTEND Integration partners and organisations with their own integration |
When the designer is opened from another application, the URL can now hide more parts of the interface, set the language of the designer, and pass a return URL. After sending, the sender returns to your own application instead of staying in ValidSign, and the designer no longer always opens in Dutch. |
Bug fixes
The table below lists the issues resolved in this period.
| Subject | Component | Description |
|---|---|---|
| Empty text in documents converted from Word | PLATFORM | During the conversion of a Word document to PDF, calculated fields in the document were recalculated. References to text elsewhere in the document returned nothing as a result, so company names, address details and invoicing details, for example, ended up empty in the signed document even though they were visible in Word. The values as stored in the Word file are now used. |
| An empty value in a field with validation | PLATFORM | A field with a validation returned an error as soon as the signer left it empty or cleared the value, even when the field was not required. On top of that, the check on Dutch IBANs rejected valid account numbers, because an additional legacy checksum was applied next to the official IBAN check. An empty field is now valid, and an IBAN is checked on format and the official IBAN check only. |
| SIGNER_COMPLETE callback sent more than once | PLATFORM | Integrations that rely on callbacks sometimes received the SIGNER_COMPLETE notification two or three times for the same signer, within seconds of each other. A signer who has finished now produces a single notification. |
| Forwarding a recipient | PLATFORM | When a recipient was replaced or a transaction was forwarded, the signatures already placed and the field values already entered moved along to the new recipient. The transaction could no longer be completed as a result. Completed actions now stay with the recipient who performed them, and only the outstanding tasks move to the new recipient. |
