I'm sure there is an open jira issue around somewhere that is relevant to this discussion.
Regards Scott HotWax Media http://www.hotwaxmedia.com On 6/07/2011, at 3:13 AM, BJ Freeman wrote: > I would like to hear why the EmailTemplateSetting was emplemented. > I am also concerned that the current production systems, with > customization would be effected. > so if this effort can be done so that it is transparent to production > servers, then I don't see a problem. > > Nicolas Malin sent the following on 7/5/2011 6:10 AM: >> Hi all, >> >> I analyse email notification in OFBiz to set a generic system for a crm >> et project managment components. >> >> We have two entity to manage email notification : EmailTemplateSetting >> and ProductStoreEmailSetting. In OFBiz history, the first entity used >> was ProductStoreEmailSetting, for automatic email during ecommerce >> process and in last time the EmailTemplateSetting for specific >> notification. >> >> Both entities have the same field : bodyScreenLocation, >> xslfoAttachScreenLocation, fromAddress, ccAddress, bccAddress, subject, >> contentType. Just primary key are differents. >> >> To simplify the notification system, I will suggest : >> * use only EmailTemplateSetting to edit email configuration >> * associate ProductStoreEmailSetting to EmailTemplateSetting >> * convert all service and screen that use ProductStoreEmailSetting >> * create convert service. >> * add contentId on EmailTemplateSetting (hors templaceContentId) to use >> a content for rendering email >> >> If somebody are interest, I can open a jira issue to manage this >> improvement. >> >> Any suggest ? >> >> Nicolas >>
smime.p7s
Description: S/MIME cryptographic signature
