eSignature (electronic signature) extension for espocrm

[skynext280]

Tested on espocrm latest versions 8.0 -> Actual (8.4.1)

Hey all, I want to present a eSignature (electronic signature) extension.


This module to allow the use of an electronic signature canvas as a field and to generate full page documents that incorporate the electronic signature and can be printed using the browser's PDF engine.

In my github (https://github.com/Lithiuhm/eSignatu...ocrm/tree/main) you have the complete guide, with photos and well explained everything that needs to be done, it is not difficult at all and works for the new versions of espocrm.

I will explain a little what it says in the guide


HOW TO USE

Go to fields and create a new esignature field, and named it as you want




Then put this field on a layout and thats it









Print to PDF

To get the image use
<img src="{{img_data ESIGNATUREGFILEDNAME}}">



And to get the date and time use
<img src="{{sign_date ESIGNATUREGFILEDNAME}}">



And that is all




The extension is edited by me and adapted to the new versions of espocrm, but I have taken the extension created by telecastg and Anthony Andriano created 5 years ago that worked for old versions of espocrm

github of the original extension https://github.com/EspoCRM-Custom-Modules/eSignature-for-Documents

thank you so much and enjoy

[ChrisSka83]

I have just tested it.
What I noticed is that the signature field is not activated for new entries.
Unfortunately, this only works with entries that have been created and then edited again.
If you are then in edit mode, you still have to activate the signature field again with the pen.
This could easily be misunderstood and interpreted as an inactive field.

I use the extension public-form from eymen-elkum
This means that you cannot use the signature field at all.
For example, as a binding order and then confirm with a signature. The pen does not exist in the extension.
I only get the name of the field.

[esforim]

Beautiful, will give it a try.

I also add it to the unofficial wiki: https://github.com/o-data/EspoCRM-Le...ign/wiki/Home/

Look like search for the word "espocrm unofficial wiki" this page is now showing up

[sapyantuk]

skynext280

I also feel the same way about the extension as ChrisSka83 mentioned. The signature field is not activated for new entries, which is quite inconvenient. It only works if you create an entry and then edit it again. Even then, you need to manually activate the signature field with the pen icon in edit mode. This can easily be misunderstood as an inactive field.

Could you please resolve this issue to ensure the signature field is active for new entries from the start?

Thank you for your attention to this matter.

[PavelZ]

Do you plan to update this extension for the new version 9.2.2?

[bandtank]

If the author does not update the extension, I will end up doing it in the next week or three. I will also move it to custom/Modules instead of application/Modules.

[PavelZ]

That would be great. Thank you.

[tarasm]

Hi everyone,

I've forked and updated the extension to support EspoCRM v9.2.0.
The code has been refactored and improved for better performance and maintainability.

Feel free to download and try it out:

https://github.com/tmachyshyn/ext-e-signature

[PavelZ]

Hi, it looks very good. However, I have many documents where the eSignature field is used. Your extension creates a new E-Signature field.
Q1: How do I move signatures from the eSignature field to E-Signature?
Q2: Is it possible to modify the extension so that signatures can be deleted?

[emillod]

Good work, man! Congrats!

[Cipher]

This is a good job. If it works well, I’ll donate a couple of dollars.

[victor]

- Migration for versions EspoCRM from v8.4.0 to v9.1.9 https://github.com/tmachyshyn/ext-e-...rm-v840---v919.
- Migration for versions EspoCRM from v9.2.0 https://github.com/tmachyshyn/ext-e-...2-espocrm-v920.

If you encounter any problems or difficulties during the migration, please leave your messages in this thread.

[victor]

There are no such plans.

[Emmker]

Hi Victor.

On GitHub you said to use that:
<p><img src="{{eSignatureSign c<FIELD_NAME>}}"></p>

<p>{{eSignatureDate c<FIELD_NAME>}}</p>

for the templates.

The thing is that these, stop the espo from creating the document.

I have noticed that, even if I paste exactly that on the pdf template code editor
<p><img src="{{eSignatureSign c<signature>}}"></p>

after I save it becomes:
<p><img src="{{eSignatureSign c&lt;signature&gt;}}"></p>

and the logs say:
[2025-10-23 18:24:57] ERROR: Formula function: ext\pdf\generate, Error while generating. Message: Wrong variable naming as 'c&lt;signature&gt;' in {{eSignatureSign c&lt;signature&gt;}} ! You should wrap ! " # % & ' * + , ; < = > { | } ~ into [ ].

[victor]

Emmker,

Please write as a regular post in this topic, not as a comment, because I did not understand what you are asking about and what steps you are taking. The only thing I understood is that your question is not related to my post about migration this extension from version to version, but to problems with using the extension itself.

[Gri.N]

Wow ! You cool !!!!!

[muulox]

Hello everyone,

I've been using this extension for about a year. We are now looking to change our workflow for signing documents.

Instead of the default behavior, we want to make it so that clicking the "Sign" button opens the signature interface in a new browser tab or, ideally, "Embedding the URL content inside an Espo Modal." We plan to achieve this using the Link Button extension: https://github.com/Kharg/link-button.

Our use case is for our front-office colleagues. Each of them has a 10" touchscreen monitor for the clients, and our goal is to display the signature interface on that monitor for clients to use directly.

This leads me to my question for the community: How do you handle the in-person client signing process? Do you have a similar setup, or could you share your workflow?

Any insights would be greatly appreciated.

Thank you

[Emmker]

Hi Victor.

I have installed E-Signature (v2.10) on a 9.2.2 espocrm.

In the forms entity, I have created a 'signature' filed that I have put in the detail layout of the forms.

I have created a pdf template called 'GDPR' for forms entity.

I created a forms workflow:

// Define the ID of the template PDF
$pdfTemplateId = '6799f56c050ea7cbe';
$entityId = entity\attribute('id');


$FormName = record\attribute('CForm', $entityId, 'name'); // Name


// Generate the PDF and create an attachment
$attachmentId = ext\pdf\generate('CForm', $entityId, $pdfTemplateId, $FormName);



// Create Document
$documentId = record\create('Document',
    'name', $FormName,
    'status', 'Active',
    'fileId', $attachmentId,
    'cClientId', contactId
);

record\relate('CForm', $entityId, 'documents', $documentId);

In the pdf template that I reference in the workflow, I have put <p><img src="{{eSignatureSign c<signature>}}"></p> in code view
and hit save.

When I hit save on the pdf template and go back to the code view the code:

<p><img src="{{eSignatureSign c<signature>}}"></p>

has become:

<p><img src="{{eSignatureSign c&lt;signature&gt;}}"></p>

and the pdf creation gives an error in my espocrm logs:

ERROR: Formula function: ext\pdf\generate, Error while generating. Message: Wrong variable naming as 'c&lt;signature&gt;' in {{eSignatureSign c&lt;signature&gt;}} ! You should wrap ! " # % & ' * + , ; < = > { | } ~ into [ ].

[shalmaxb]

Hi, did you try to escape the < and the > as stated in the error by brackets?

[Emmker]

Th error is generated because the
<p><img src="{{eSignatureSign c<signature>}}"></p>
becomes
<p><img src="{{eSignatureSign c&lt;signature&gt;}}"></p>

as soon as I save.

so it refers to <p><img src="{{eSignatureSign c&lt;signature&gt;}}"></p>

What to wrap in [ ]?

[lazovic]

Hi Emmker,

You need to insert the field name instead of the c<signature> value. Something like cSignature. Please check properly the fields names in the Administration > Entity Manager > CForm > Fields.

[Emmker]

Now I get it.

I do not have a c before my fields. The filed is named 'signature'

I just put <p><img src="{{eSignatureSign signature}}"></p>
and it worked fine.

I misunderstood the 'c<something>' part of the code