Skip to content

signature

Signature requests: a signed-in user asks several people to sign one PDF of the tenant. Every request belongs to a host row of an entity named in hostEntities; a user sees and works on a request only while that row is readable to them. Each signer draws a signature on a display in person or through a link in the URL fragment (14 days, limited opens, revocable, single-use, one answer for every rejection). The last signature moves the request to all-signed; a job renders a signature page through the print client, appends it to the unchanged original and completes the request. Events completed, declined, expired and failed report the outcome; signer name, email, image, IP and user agent are personal data.

What this feature needs to run (Requires, top) and the write commands this feature provides (Provides, bottom).

flowchart TB
  n_signature["signature"]
  subgraph how_reqs["Requires"]
    n_files["files"]
    n_user_data_rights["user-data-rights"]
    n_renderer_puppeteer_client["renderer-puppeteer-client"]
  end
  subgraph how_provides["Provides"]
    n_cmd_signature_write_cancel(["cancel"])
    n_cmd_signature_write_decline_by_link(["decline-by-link"])
    n_cmd_signature_write_expire(["expire"])
    n_cmd_signature_write_fail(["fail"])
    n_cmd_signature_write_finish(["finish"])
    n_cmd_signature_write_forget_signer(["forget-signer"])
    n_cmd_more(["+10 more"])
  end
  n_files --> n_signature
  n_user_data_rights --> n_signature
  n_renderer_puppeteer_client --> n_signature
  n_signature --> n_cmd_signature_write_cancel
  n_signature --> n_cmd_signature_write_decline_by_link
  n_signature --> n_cmd_signature_write_expire
  n_signature --> n_cmd_signature_write_fail
  n_signature --> n_cmd_signature_write_finish
  n_signature --> n_cmd_signature_write_forget_signer
  n_signature --> n_cmd_more

Provides — write commands this feature registers (dispatch them through the command bus):

  • Registers extension: userData → signatureSigner