How S-Sign Generates Envelopes

This document describes the full S-Sign transaction from document generation through completion. S-Docs produces the S-Doc record; S-Sign owns the envelope, envelope documents, Files-based signing PDFs, the signing experience, and the final signed and audit outputs. (This is separate from S-Docs eSignature where product responsibilities differ.)

---

End-to-end flow

1. Anchor on the base record Work starts from a Salesforce business record (the merge/signing context).
2. Generate the S-Doc S-Docs creates SDOC__SDoc__c from the S-Docs template and that record. The S-Doc is the reference S-Sign uses for the signing transaction; S-Docs does not run the signing engine.
3. Apply S-Sign configuration S-Sign resolves signing policy from SSIGN__SSTemplate__c, associated to SDOC__SDTemplate__c via SSign__SDTemplate__c. That template drives signer rules, tags/inputs, notifications, and output behavior when the envelope is prepared.
4. Create the Envelope S-Sign creates an S-Sign Envelope that junctions the transaction to the base record and acts as the parent for everything in that signing request.
5. Create Envelope Document(s) Under the envelope, S-Sign creates Envelope Document rows—one per signable document in the transaction.
6. Materialize signing PDFs (Salesforce Files) For each envelope document, S-Sign generates a PDF and stores it as Salesforce Files (ContentDocument / ContentVersion). The signing experience references these files as what the signer sees and executes against.
7. Run the signing experience Signers complete the flow in the Signing Experience UI, backed by the envelope, its envelope documents, and those PDF references.
8. Complete and persist outputs When signing finishes, the S-Sign managed package produces:

   • A signed PDF (executed document), and
   • An audit PDF (evidence / trail).

   Artifacts are saved per package behavior (typically new Files, linked to the appropriate records).

---

Multiple documents in one experience

If several documents are combined into a single signing experience, one Envelope still holds multiple Envelope Document children. Each child carries its own signing PDF in Files; completion still yields the package’s signed and audit outputs for the finished transaction.