Release Notes 2.261.0 (22.07.2026)

This release enhances multi-party document signing workflows by introducing targeted signature field assignment and automated identity prefilling between Web Forms and the Document Viewer.

Targeted Signature Field Mapping

When a document contains multiple signature components (such as multi-party contracts or counterpart agreements), you can now specify exactly which signature field a user must interact with.

• Component Identification: Each Signature component in a template has a unique ID, which can be defined in the Template Editor under the Advanced properties tab or generated automatically.
• Restricted Signing Scope: By passing signature_id inside the prefill data object, the Document Viewer activates only the matching signature field. The user is restricted from clicking or modifying signature components assigned to other signers.
• Default Placement: If no signature_id is specified in the prefill payload, the Document Viewer maintains standard behavior, allowing the user to select or place a signature component freely.

Developers can pass both identity details and the targeted signature_id within the prefill dataset when fetching or storing document viewer URLs:

{
  "prefill": {
    "first_name": "Jane",
    "last_name": "Doe",
    "email": "jane.doe@example.com",
    "id_code": "UK182912312",
    "editable": true,
    "signature_id": "disclosing_party_signature"
  }
}

Automated Form-to-Review Data Prefill

We updated the data bridge between embedded Web Forms and the Document Viewer to eliminate duplicate data entry.

• Automatic Mapping: If your Web Form dataset contains the standard identity keys first_name, last_name, id_code, and email, these values are passed directly into the Document Viewer review step.
• Reduced Friction: When the "Sign the document" option is enabled after form submission, the reviewer identity fields populate automatically, allowing the user to proceed straight to reviewing and signing.

Updated on: 22/07/2026