How to use the eSignature extension to add electronic signature functionality to Espo
Collapse
X
-
Hello, I have version 4.0.4 of "eSignature Documents for EspoCRM" installed on Espocrm 8.2.5 with Advanced Pack 3.3.1 and Sales Pack 2.3.4.
It works almost perfectly, when I generate the file the signature is shown correctly but when I send the pdf with signature as attachment both using Sales Pack "Send Email" function and ext\pdf\generate() in workflow the signature is not rendered. What could be the issue?Leave a comment:
-
Sorry to all, but I can't buy/download the new eSignature extension from devcrm link: can you help me, please?Leave a comment:
-
Just wondering if you don't use this logic in your business workflow. this is a pretty common scenario.Leave a comment:
-
Just wondering if you don't use this logic in your business workflow. this is a pretty common scenario.Leave a comment:
-
Check your entityDefs json file to verify that both fields have the setting: "required": false then clear cache Administration > Clear cache and rebuild Administration > Rebuild then do a hard reload Ctrl+Shift+R in your browser and verify the entityDefs file again.
Read the documentation, search for examples in the forum or post your question in the Developer help or General Help forums.Last edited by telecastg; 09-30-2023, 02:23 AM. -
Hi, I have cleared the cache and taken off the required check mark on both fields... still showing the error. In regards the dynamic handler is more difficult for me as I am not a programmer, I don't know what code should i use. thanks for helpLeave a comment:
-
Did you clear cache and rebuild after removing the "required" flag from the "signatureondelivery" field ?
If you did, and the message appeared again, try removing the required flag from the other eSignature field ("signature") in your entity as well, clear cache and rebuild.
If you want to force completion of a esignature field under a given scenario, use a dynamic handler as stated above instead of the GUI settingsLast edited by telecastg; 09-29-2023, 04:48 PM. -
thanks for replying.Leave a comment:
-
I have already answered your questions and the extension has nothing to do with your issues:
1) The display issues are triggered by your dynamic logic setup. Remove those conditions and the field will work fine. If you want to find out a better way to determine field visibility and other interface features, use a dynamic handler instead of dynamic logic: https://docs.espocrm.com/development/dynamic-handler/
2) You flagged the Signature on Delivery field as "required" in Entity Defs, that is why Espo throws an error, which is the correct behavior. Remove this condition and the issue will disappear. Somehow you are trying to save the entity while the field empty.
Using a dynamic handler to define your logic will help define the events or conditions and results that you are trying to achieve in the user interface.Last edited by telecastg; 09-28-2023, 08:48 PM. -
the major issue is that the delivery signature canvas won't display properly so I am unable to sign (doesn't work), another issue is when I click to create another order form an error comes up saying the signature can't be blank. see picture
2 PhotosLeave a comment:
-
The reason why you can't save the Pickup entity without the delivery signature being signed is because you marked the field as "Required", uncheck this box and you will be able to save / update the entity before the delivery signature is completed.
The extension is not interferring with your logic at all.
If you have further questions regarding your application, please post them in the Developer Help or General Questions forums so other members can read them and help if they can.
Thanks
Leave a comment: