דלגו לתוכן

Notes for Release 4.50

תוכן זה אינו זמין עדיין בשפה שלך.

Over the past weeks we have been working on improvements to Cellosign platform. In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed.

Stage environment: Scheduled for release on: 05/10/2026

Production & Pre-Production Environments: Scheduled for release on: 18/10/2026

LIVE connector — Response Field Mapping (field change webhook)

Section titled “LIVE connector — Response Field Mapping (field change webhook)”

The field change webhook now supports an explicit Response Mapping. Previously a returned value only landed in the form if its key matched an alias you had sent out or the exact ID of a form control — anything else was dropped. Turn on Use Response Mapping in the LIVE connector editor and add rows of alias → form control to route any returned key onto one or more controls (the same alias can fan out to several controls; each control can be targeted only once).

Off by default and fully backward compatible — existing connectors resolve responses exactly as before; no migration or API-contract change required.

📸 Screenshot placeholder — Response Mapping section in the LIVE connector editor.

Full detail: Field change webhook.

Behavior / configuration

  • Before it is sent, the resolved name is passed through a file-name sanitizer so characters that are unsafe in a file name — or that could break the archive JSON payload — are normalized. This keeps the archived file name valid across Windows, macOS and Linux.
  • Kept as-is: letters and digits in any language (including Hebrew), Hebrew niqqud, and the punctuation set . - _ ( ) [ ] ' + , & # @ and space.
  • Every other character (slashes, colons, ?, *, |, quotes, emoji, control/zero-width characters, right-to-left overrides, etc.) is replaced with an underscore _.
  • Runs of underscores or spaces are collapsed to one, and the file extension is always preserved.
  • Reserved Windows names (CON, PRN, AUX, NUL, COM1–COM9, LPT1–LPT9) get a trailing underscore. The name is limited to 255 UTF-8 bytes without splitting a multi-byte character.
  • Example: a configured name of invoice/2026:final is archived as invoice_2026_final.pdf.
  • Backwards compatibility: when no mail_pdf_name is configured, the archived document keeps its previous name (the internal storage file name), so existing setups are unaffected until a name template is configured.
  • Custom font in print header and footer is now fixed.
  • Agent Screen in live session: sending an invitation is now blocked.
  • Accessibility: the maximum-scale attribute has been removed from the form view so users can zoom.
  • Bullet repeater in the formula builder is now fixed.
  • Public UI has been refactored completely. As part of this rework there may be minor visual glitches in the view — please report anything you spot.
  • Legacy manager application reference removed. The manager application now runs entirely on new infrastructure; the reference to the legacy application has been removed.
  • Project logo size limit. The logo in project settings is now limited to 250 KB.