Martyn Houghton Posted September 4, 2018 Share Posted September 4, 2018 Are there any plans to add support the creation of Email Template Translations, i.e. you have one Email Templates, such as 'RequestMessage' one which has the option to hold translated versions in addition to the default one, with the correct one being selected based on the 'Customers' language? This would fit in with only being able to select a single default request message template on the service, where as at the moment we would have to create seperate templates for each lanuage and use separate services or only send emails via the BPM where we can determine which email template to use. Cheers Martyn Link to comment Share on other sites More sharing options...
HHH Posted September 7, 2018 Share Posted September 7, 2018 We have the same issue with multi language customers and want to be added as an interested party to this. 1 Link to comment Share on other sites More sharing options...
HHH Posted November 21, 2018 Share Posted November 21, 2018 Hi Hornbill Anything on this. We work in 8 languages and being able to use templates rather than manually writing everything or using snippets would help a lot. Also when building BPM's it's a hassle to need to branch every process 8-ways depending on language as soon as customer communications is neccesary. 1 Link to comment Share on other sites More sharing options...
HHH Posted June 17, 2019 Share Posted June 17, 2019 @Martyn Houghton I just started testing using ESP conditions as a workaround. Some text in Swedish and then the condition '{{Customer Contact.H_language}}'='sv' then another text in English and the condition '{{Customer Contact.H_language}}'='en-GB' This works as expected but is a bit fiddly so proper translations would be preferred. https://wiki.hornbill.com/index.php/Email_Templates 1 Link to comment Share on other sites More sharing options...
HHH Posted October 16, 2019 Share Posted October 16, 2019 Are email template translations something that is considered for implementation? 1 Link to comment Share on other sites More sharing options...
Martyn Houghton Posted November 7, 2019 Author Share Posted November 7, 2019 @HHH Are your ESP Conditions still working okay for the languages with hyphen in them? Where "{{Customer Contact.H_language}}='en'" works but "{{Customer Contact.H_language}}='en'-US" does not. Cheers Martyn Link to comment Share on other sites More sharing options...
HHH Posted November 12, 2019 Share Posted November 12, 2019 @Martyn Houghton '{{Customer Contact.H_language}}'='en-GB' AND {{.h_customer_type}} = 1 works as expected But I noticed in your example above there are ' ' around the en part of the language code rather than the full code. Or maybe that was just a copy/paste error in your post. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now