Mailing-List: contact dev-help@ofbiz.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ofbiz.apache.org
MIME-Version: 1.0
From: Swapnil Mane <swapnil.mane@hotwaxsystems.com>
Date: Fri, 11 Aug 2017 11:31:06 +0530
Message-ID: <CAJZt1n28Jjn07-DHk3Uj-=PxFRS_Ba6-3dg66jqQ_XeTZEhexA@mail.gmail.com>
Subject: [Proposal] - Leverage the CMS capability for Product Store's Email
To: Dev list <dev@ofbiz.apache.org>
Cc: Swapnil Mane <swapnil.mane@hotwaxsystems.com>
Content-Type: multipart/alternative; boundary="001a1146fa76577dfe0556740c94"
archived-at: Fri, 11 Aug 2017 06:01:57 -0000

--001a1146fa76577dfe0556740c94
Content-Type: text/plain; charset="UTF-8"

Hello Devs,

While looking into the support of email templates for Product Store, we
found it is managed by screens.

Like for Order Completion

<ProductStoreEmailSetting
bodyScreenLocation="component://ecommerce/widget/EmailOrderScreens.xml#OrderCompleteNotice"
emailType="PRDS_ODR_COMPLETE" fromAddress="ofbiztest@example.com"
productStoreId="9000" subject="OFBiz Demo - Your Order Is Complete
#${orderId}"/>

Here you can see, we are having dependency on screens (i.e. templates
defined in file system)
Due to this, the user is unable to edit the email template on the fly.

We can enhance this mechanism by making the template as content driven.
Here is the design plan,

We can extend the ProductStoreEmailSetting entity by contentId field.
While rendering email based on its type, if the contentId is present, this
content will render, else system will look for bodyScreenLocation (our
existing implementation)

Using this we can leverage the CMS capability of the OFBiz.
Right now if end user (client) wants to make any change in the email
template, it required the changes in the file.
If we manage this by content, the user can edit this on the fly with the
help of CMS.

All the inputs and suggestions are welcome!


- Best Regards,
Swapnil M Mane
www.hotwaxsystems.com
www.hotwax.co

--001a1146fa76577dfe0556740c94--