Garry Klooesterman
Senior Technical Content Creator
Published January 02, 2025
Updated October 14, 2026
5 min
Case Management with Apryse WebViewer and Digital Signatures in Appian
Garry Klooesterman
Senior Technical Content Creator
Summary: Digital signatures prove who signed a case document and whether it changed afterward. This post covers why case work needs them and what the Apryse WebViewer plugins add to Appian case applications.
Introduction
Some case files need more than a name on a line. They need proof of who signed and whether anything changed afterward. A digital signature provides that by binding the signature to a certificate. Apryse WebViewer creates and validates digital signatures in the browser, with long-term validation (LTV) and trusted timestamps so a signature stays verifiable for as long as the case record exists.
The Apryse WebViewer plugin for Appian puts that inside your case applications. Your users open, annotate, and sign documents without leaving Appian.
Why Case Work Needs Digital Signatures
- Proof that holds up later. A digital signature shows who signed and whether the document changed afterward. Trusted timestamps record when.
- No paper, no in-person signing. Signers complete documents from wherever they work the case.
- Validation, not just capture. Reviewers can check signatures on documents that arrive from outside parties before the case moves forward.
Where this shows up:
- Legal: filings and agreements that other parties will scrutinize
- Healthcare: patient consent forms and release authorizations
- Finance: loan documents and account agreements
- Government: license applications and permits
What the Plugins Add
Here’s what the Apryse WebViewer plugins add to the Appian interfaces your team builds:
- Document work inside Appian interfaces. Case managers view, annotate, and edit documents in the same interface where they work the case.
- Digital signatures. Sign documents with certificate-based digital signatures and validate existing ones, so reviewers can confirm who signed and whether the file changed.
- Redaction. Permanently remove sensitive text and images before a document leaves the case. Redaction can’t be undone, so build a review step into your process model.
- Client-side processing. WebViewer processes documents in the browser. No document content goes to Apryse servers.
- A UI scoped to the case. The modular UI shows only the tools each case type needs, and it supports WCAG 2.2 Level AA.
Appian still owns routing, approvals, automations, and case history. The plugins cover the document steps in between.
Get Started
Appian already holds your case. The plugins keep its documents there too.
Start with the installation guide. Get a trial key at dev.apryse.com. Questions about your setup? Talk to an expert or ask on Discord.
