New update for signoSign/Universal (version 3.28.1)

With the signoSign/Universal web application, you can sign your documents with greater flexibility than ever before. Use the application on your computer, smartphone or tablet. Capture signatures during face-to-face meetings or send documents to your contractual partners for signing. Cloud users (SaaS) have received the update automatically. You can find a complete overview of all the highlights and new features in this article.

Here are the key new features of version 3.28.1 at a glance:

• Mobile Capture can now be managed separately from the other signature methods: as a separate value in ‘SupportedCaptureInput’, it can be enabled per user in the user settings and analysed in the statistics. This allows you to specifically assign signature capture via smartphone to individual users or workflows.
• New setting ‘web.noteBrushDefaultThickness’ for the default line thickness of notes. Available in the Viewer, in user settings and in pool settings.
• Spanish is now available as a new interface language; the Italian translation has been updated.
• The devices supported for read mode are now documented.
• Revised navigation menu and a more descriptive subject line for the ‘Workflow completed’ notification.

For integrators

Workflow notifications can now be fully implemented using webhooks. The new blueprint attributes “activityWebhook” and “emailDeliveryDisabled”, new webhooks for the start and end of individual workflow steps, and a new endpoint “webhooks.messageeventendpoint” are available for this purpose. The tenant identifier can now be changed via the REST API, and selected demandSignature endpoints also return the access URL. Workflow processes now have their own context within the AuditContext.

Bug fixes

An overview of the key areas:

• Pen and touch can now be combined freely. Previously, ‘Electronic Pen’ could only be used in conjunction with ‘Touch Input’. Both methods can now be enabled independently of one another.
• Viewer on mobile devices and tablets: page and signature overview, pinch-to-zoom, font sizes, scaling of multi-page documents, display of documents with different page sizes, as well as checkboxes and buttons on small screens.
• Signature capture: interrupted signatures when using touch input on the iPad, correct recognition of the Apple Pencil as pen input, and missing anchor points in the signature path.
• signotec Delta: Display of the signature, signing across multiple pages, display outside full-screen browser mode and returning from read mode.
• Mobile Capture: Display of the QR code, generation of a new code following a connection failure, the effect of mouse movements on the signature, and a misleading status indicator when no device is connected.
• Forms: ‘Auto’ font size and the configured Courier font are reapplied; locked and empty fields behave correctly; mandatory checkboxes and radio buttons are reliably enforced; and field entries are retained when selecting ‘Continue later’.
• Workflows and templates: Document order, renaming and replacing placeholder documents, editing templates, clear error messages for incomplete workflows, recipient management and TAN dispatch via the designated server. The creation and deletion of templates are now recorded in the audit log.
• Sharing Cases: Declaration of consent, detailed view and correct user assignment.
• Databases and operations: Operation with Oracle 19c, clean-up routines and change notes for MSSQL, as well as timeout behaviour.
• Emails: Correct scaling of custom logos, more meaningful subject lines and corrections to the French template.
• API and documentation: corrected endpoints and status codes, revised Swagger descriptions, and a cleaned-up OpenAPI specification, which now allows client generation to run without errors.

Further details on the changes in each version can be found in the changelog!

---

Update notes

Cloud:

As usual, the update is automatically made available in the cloud. There are no special considerations to bear in mind.

On-premises:

• Java 21 (Jakarta) or later is required. If you are using Tomcat, you must therefore update to Tomcat 10.
• If you are using an external database, you may need to extend the database schema using the migration tool.
• Please check before updating whether any changes to the integration are necessary.

---

If you have any questions about the update or the new features, please do not hesitate to contact our sales team or your sales partner.