Tweet
Hi,
I've been trying to use 'parseTemplate' function for parsing my entity data into the template dynamically. But as I checked the implementation, some fields were missing because of forbidden ACL field scope. An example would be, sending an email that was triggered by a different user to a specific user that has different access control. I had the same issue also on the PDF templates with Htmlizer but I just make the ACL as null. I made my own implementation of the Pdf service.
Htmlizer has a parameter for the ACL which makes it more easier while the EmailTemplate service 'parseText' has no option to ignore the ACL.
For better understanding, please check the following implementations below:
Htmlizer: https://github.com/espocrm/espocrm/b...lizer.php#L100
EmailTemplate: https://github.com/espocrm/espocrm/b...plate.php#L180
Htmlizer having if statement for ACL and 'parseText' none.
I've been trying to use 'parseTemplate' function for parsing my entity data into the template dynamically. But as I checked the implementation, some fields were missing because of forbidden ACL field scope. An example would be, sending an email that was triggered by a different user to a specific user that has different access control. I had the same issue also on the PDF templates with Htmlizer but I just make the ACL as null. I made my own implementation of the Pdf service.
Htmlizer has a parameter for the ACL which makes it more easier while the EmailTemplate service 'parseText' has no option to ignore the ACL.
For better understanding, please check the following implementations below:
Htmlizer: https://github.com/espocrm/espocrm/b...lizer.php#L100
EmailTemplate: https://github.com/espocrm/espocrm/b...plate.php#L180
Htmlizer having if statement for ACL and 'parseText' none.
Comment