Suitecrm: Using "E-Mail" from the action menu does not include variables from the templates

[cjmny]

After implementing the fix from pull request #1168, the emails themselves will send, but the don't pull the variables mentioned in the email templates (e.g. Instead of "John", the email is addressed to "prospect_first_name").

[sathishsengodan]

Hi @cjmny

I am unable to replicate this issue.I have created a test template with account variables and sent out email from the accounts module using that template. I have received the all the values for the variables in the template to the email that I have sent.

Please can you explain this in bit more detail so I can look into this further.

Thanks

[cjmny]

Thanks for the update @sathishsengodan . I experienced this issue with an email template built for the Prospects module. I am basically just trying to address the emails by name, but when I do the email gets delivered with "Hello $prospect_first_name,". When the same email is sent through a Workflow, it has the variable data.

[cjmny]

Update to this. If you generate the email and specify the related module record, it does work. This does present an issue though. You can multi select in the list view to email multiple accounts/prospects, and while SuiteCRM will warn you that unintended results could occur, if you are pulling required fields from the record in the email they should populate.

[samus-aran]

The fix proposed will need to be tested thoroughly as a replacement for the the current parse_template function. Something we will need to schedule in and perhaps encourage the community to test.

[ghost]

I've tested pull request 2562 today on v7.7.7. Works fine except for multi-enum fields: They show item key values (as saved in database, e.g. "^item1^") instead of language file entries.

It's a big step in the right direction. Thanks for this!

[benjaromero]

Any update in this issue?

I am experiencing a similar problem. I have built two custom modules, one basic and the other one contacts.

I add variables from both to the email template but the email sent just shows right variables of the contact module. The variables from the basic module doesn't show the variable values. Any idea why?

I really appreciate any help.

Ben

[boombata]

@benjaromero see nelem post #13089, maybe adding your modules around line 500

[PedroErnst]

I've just fixed #4636 which is a somewhat related issue. Template variables in the related module should now replace correctly in 7.8.x (it was already fixed in 7.9.x).

So this issue now is only the bulk action email.

When selecting multiple Leads/Contacts/etc and using the bulk action Email, if you choose a template:

SuiteCRM 7.8.x LTS will warn you explicitly that this is not supposed to work. You're supposed to use Email Campaigns for such functionality. No bug.

In 7.9.x, with the reworked Email module this warning no longer appears.

So my question is what is the intended functionality here?

• The warning is simply missing, and the way to go for this kind of personalized email is still Email Campaigns.

• Or is bulk action emails supposed to replace the contact details for each of the addressees selected in the bulk action? So instead of sending a single email with X addresses in TO the CRM would split it into individual emails. Some other functionality would be lost here (for example reply-to-all for anyone receiving such an email).

So I think maybe only the warning is missing here.

@mattlorimer @daniel-samson

[Mausino]

@Dillon-Brown @samus-aran should be the milestone 7.10.10 closed and this hight priority issue and also all 12 tickets of 7.10.10 milestone move to milestone 7.10.11 or 7.11 ?

[Mausino]

@samus-aran shoud it be in milestone 7.10.12 ? because it's Fix Proposed and Hight Priority issue. I want only that we wont forget on this ticket if has tested solotion.

[samus-aran]

I agree in this particular case that we could add the current 7.10.12 because there appears tobe fixes for this throughout the application regarding parsing.

https://github.com/salesagility/SuiteCRM/issues?q=is%3Aopen+is%3Aissue+milestone%3A7.10.12

[samus-aran]

Ideally https://github.com/salesagility/SuiteCRM/pull/6466 Should be the new fixed proposed.