Overview:
Three eSignatures appear in the Vault viewable rendition on a document that goes through two runs of the same workflow.
Root Cause:
The user selects a different eSignature reason capacity the second time the document goes through the same workflow run.
Solution:
An eSignature is considered unique by the combination of:
- Vault username
- User task verdict
- Reason capacity
These all need to be the same in order for two of the same eSignatures to only manifest the latest version of the eSignature on the document. Otherwise, all versions of the eSignature manifest on the document.
If the same user approves the document on more than two separate workflow runs and the capacity is different each time, only the latest prior workflow attempt plus the current workflow attempt manifest on the document. This is done to avoid the cluttering of the eSignature Page of the viewable rendition.
Related Documentation:
Vault Lifecycle Documentation: Configuring Lifecycles to Manifest eSignatures
Thank you