starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-25 05:46:01 +03:00

[GH-ISSUE #1524] Signature placeholder field #432

New issue

Open

opened 2026-02-26 18:47:02 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 18:47:02 +03:00

Owner

Originally created by @nirkons on GitHub (Dec 10, 2024).
Original GitHub issue: https://github.com/documenso/documenso/issues/1524

Feature Description

Add an option to use a placeholder for signature placement.

Use Case

I am preparing a dynamic PDF document with order details, since people purchase various amounts of products, the placement of the signature is dynamic, it could be on any page in the document after the order details.

Proposed Solution

Allow to use {{signature}} (or {{documenso_signature_1}} / {{documenso_signature_2}} etc..)

Alternatives (optional)

as far as I can see, the only way is to use figure out with code where my {{signature}} is place within the PDF and then use the documenso API to add a field on that location, but its complicated.

Additional Context

No response

Please check the boxes that apply to this feature request.

I have searched the existing feature requests to make sure this is not a duplicate.
I have provided a detailed description of the requested feature.
I have explained the use case or scenario for this feature.
I have included any relevant technical details or design suggestions.
I understand that this is a suggestion and that there is no guarantee of implementation.
I want to work on creating a PR for this issue if approved

Originally created by @nirkons on GitHub (Dec 10, 2024). Original GitHub issue: https://github.com/documenso/documenso/issues/1524 ### Feature Description Add an option to use a placeholder for signature placement. ### Use Case I am preparing a dynamic PDF document with order details, since people purchase various amounts of products, the placement of the signature is dynamic, it could be on any page in the document after the order details. ### Proposed Solution Allow to use {{signature}} (or {{documenso_signature_1}} / {{documenso_signature_2}} etc..) ### Alternatives (optional) as far as I can see, the only way is to use figure out with code where my {{signature}} is place within the PDF and then use the documenso API to add a field on that location, but its complicated. ### Additional Context _No response_ ### Please check the boxes that apply to this feature request. - [X] I have searched the existing feature requests to make sure this is not a duplicate. - [X] I have provided a detailed description of the requested feature. - [X] I have explained the use case or scenario for this feature. - [X] I have included any relevant technical details or design suggestions. - [X] I understand that this is a suggestion and that there is no guarantee of implementation. - [ ] I want to work on creating a PR for this issue if approved

kerem added the

Stale

status: triage

labels

2026-02-26 18:47:02 +03:00

kerem commented

2026-02-26 18:47:02 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 10, 2024):

Thank you for opening your first issue and for being a part of the open signing revolution!

One of our team members will review it and get back to you as soon as it possible 💚

Meanwhile, please feel free to hop into our community in Discord

@github-actions[bot] commented on GitHub (Dec 10, 2024): Thank you for opening your first issue and for being a part of the open signing revolution! <br /> One of our team members will review it and get back to you as soon as it possible 💚 <br /> Meanwhile, please feel free to hop into our community in [Discord](https://documen.so/discord)

kerem commented

2026-02-26 18:47:02 +03:00

Author

Owner

@daKmoR commented on GitHub (Dec 11, 2024):

We are in the same boat - generating large dynamic 60+ page documents with 10+ signature fields for 2+ signers.

Doing this by hand if we automatically generate the document is not really maintainable. We also can't use a template as the content may be different every time so the the signature position will be different as well.

We are currently experimenting with the following workflow

Generate HTML
Use a special 1x1px transparent image, scale it to the signature size for every signature
Convert HTML -> PDF using puppeteer
Analyse PDF to find all image => if image === same as the special 1x1px image => remember page + coordinates + size
Use Documenso API to add signature fields at the gathered locations

I'm hopeful this will work - we are pretty close to a POC.
Later we could have multiple different special images - one for each signer... so you could add 3 signature fields for Peter and 3 signature fields for Sandra.

And ultimately it would be nice if documenso could handle this directly - e.g. add a special transparent image and you got yourself a sign field.

@daKmoR commented on GitHub (Dec 11, 2024): We are in the same boat - generating large dynamic 60+ page documents with 10+ signature fields for 2+ signers. Doing this by hand if we automatically generate the document is not really maintainable. We also can't use a template as the content may be different every time so the the signature position will be different as well. We are currently experimenting with the following workflow 1. Generate HTML 2. Use a special 1x1px transparent image, scale it to the signature size for every signature 3. Convert HTML -> PDF using puppeteer 4. Analyse PDF to find all image => if image === same as the special 1x1px image => remember page + coordinates + size 6. Use Documenso API to add signature fields at the gathered locations I'm hopeful this will work - we are pretty close to a POC. Later we could have multiple different special images - one for each signer... so you could add 3 signature fields for Peter and 3 signature fields for Sandra. And ultimately it would be nice if documenso could handle this directly - e.g. add a special transparent image and you got yourself a sign field.

kerem commented

2026-02-26 18:47:02 +03:00

Author

Owner

@daKmoR commented on GitHub (Dec 16, 2024):

so that works quite nice 💪 e.g. drop a simple image in your html and you can later find it's location and then use it to generate sign fields for documenso 🎉

it works so well we decided to open source it
https://www.npmjs.com/package/@finum/html-to-pdf-to-sign

testing it would be appreciated 🤗

@daKmoR commented on GitHub (Dec 16, 2024): so that works quite nice 💪 e.g. drop a simple image in your html and you can later find it's location and then use it to generate sign fields for documenso 🎉 it works so well we decided to open source it https://www.npmjs.com/package/@finum/html-to-pdf-to-sign testing it would be appreciated 🤗

kerem referenced this issue

2026-02-26 19:31:19 +03:00

[PR #455] [MERGED] fix: resolve issues with signing document stickiness #984

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/documenso#432

No description provided.

Rows
Columns