E-Signature extension providing electronic signature capabilities for EspoCRM.
This extension enables the use of an electronic signature canvas field within EspoCRM, allowing users to capture signatures directly in the application. It also supports generating full-page documents that embed the captured signature, which can be printed or saved as PDF using the browser's built-in PDF functionality.
Follow the standard EspoCRM extension installation process to add the E-Signature extension to your instance.
In the EspoCRM Administration panel, customize the desired entity (e.g., Contact, Opportunity, Document) and add the "Signature" field to the layout using the Layout Manager.
When viewing or editing a record with the signature field, users can draw their signature directly in the provided canvas area.
After saving the record, the captured signature will be stored and displayed within the record details.
Use the extension's document generation feature to create a full-page document that includes the captured signature. You can print or save this document as a PDF using your browser's print functionality.
Available Placeholders:
<p><img src="{{eSignatureSign c<FIELD_NAME>}}"></p>
<p>{{eSignatureDate c<FIELD_NAME>}}</p>
- In Administration > Extensions install E-Signature extension
2.0.0to the previously installed1.0.3.
скріншот-Administration-Extensions
- In Administration > Entity Manager > Your_entity_name delete the field with
eSignaturetype that was created in E-Signature extension1.0.3.
скріншот-Administration-Entity-Manager-Your_entity_name-Fields-Remove-eSignature
- Create a field with
E-Signaturetype with the same name as in the previous step.
screenhot-Administration-Entity-Manager-Document-Fields-E-Signature
Additionally, in Code View of the previously created PDF Template for your entity, you can replace the old Placeholder from:
<img src="{{img_data ESIGNATUREGFILEDNAME}}">
to
<p><img src="{{eSignatureSign c<FIELD_NAME>}}"></p>
<p>{{eSignatureDate c<FIELD_NAME>}}</p>
Since E-Signature extension 1.0.3 has stopped working on EspoCRM v9.2.0, perform the following steps:
- In Administration > Extensions install E-Signature extension
2.0.0to the previously installed1.0.3.
скріншот-Administration-Extensions
- In Administration > Entity Manager > Your_entity_name create a field with
E-Signaturetype with a different name than you used in E-Signature extension1.0.3.
скріншот-Administration-Entity-Manager-Document-Fields-New-E-Signature
- In Administration > Entity Manager > Your_entity_name > Formula > Before Save Custom Script create a formula that will copy data from the old field to the new one:
c<NewSignatureFieldName> = c<OldSignatureFieldName>;
// c<OldSignatureFieldName> = null; // Optional: clear the original value if it's no longer required
- Go to the List view of your entity and in drop-down menu of Actions execute Recalculate Formula.
скріншот-Your_entity_name-Actions-Recalculate-Formula
- Remove the old
eSignaturetype field from Entity Manager and Layout Manager. - Remove E-Signature extension
1.0.3.
For more information, follow the instructions.
Note: Since the jSignature library requires jQuery out-of-the-box, it is recommended to keep
isDeveloperModeset tofalse. This ensures proper loading of dependencies and stable operation of the extension.
Create config.php in the root directory of the repository:
<?php
return [
'useCache' => false,
'isDeveloperMode' => false,
];
You need to set the following paths to be ignored in your IDE:
buildsite/buildsite/custom/site/client/custom/site/tests/unit/Espo/Modules/ESignaturesite/tests/integration/Espo/Modules/ESignature
You can set up a file watcher in the IDE to automatically copy and transpile files upon saving.
File watcher parameters for PhpStorm:
- Program:
node - Arguments:
build --copy-file --file=$FilePathRelativeToProjectRoot$ - Working Directory:
$ProjectFileDir$
Note: The File Watcher configuration for PhpStorm is included in this repository.
E-Signature extension is published under MIT license. For more details, see LICENSE file.















