+1 for both the points, first introduce the feature with design proposal
shared by Ratnesh. And in a separate discussion/effort we can discuss and
finalize the generic data model approach. Even this thread is also good
start for discussing the generic data model proposal.
Rishi Solanki
Sr Manag
Le 23/09/2017 à 16:29, Ratnesh Upadhyay a écrit :
Hi Jacques,
Thanks for the response. I was thinking that retrieval gets slow down when
we have a lot of data in communication event entity. Actually, I've
prepared this proposal based on the current implementation of
CommunicationEventOrder on th
Hi Jacques,
Thanks for the response. I was thinking that retrieval gets slow down when
we have a lot of data in communication event entity. Actually, I've
prepared this proposal based on the current implementation of
CommunicationEventOrder on this assumption that it's an approved feature
that's i
Le 23/09/2017 à 13:14, Ratnesh Upadhyay a écrit :
Imagine if we use the generic data model to record each kind of
communication and when the system tries to pull a specific email or
specific type email communication from this model then system has to browse
a lot of data and due to this most of t
Your assumption is correct, Rishi thanks for the inputs.
Regards,
Ratnesh Upadhyay
HotWax Systems | www.hotwaxsystems.com
On Sat, Sep 23, 2017 at 4:05 PM, Rishi Solanki
wrote:
> +1 for the proposal, I'll be happy to discuss and finalizing the things.
>
> Assuming that you have already consider
Thanks for your inputs Deepak.
Agreed that CommunicationEvent is way generic and this is the main use case
to keep the order and return separately from this model as they are using
most frequently in each business.
Imagine if we use the generic data model to record each kind of
communication and w
+1 for the proposal, I'll be happy to discuss and finalizing the things.
Assuming that you have already consider ProductStoreEmailSetting and
EmailTemplateSetting for sending the different notification for return.
Rishi Solanki
Sr Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Hi Ratnesh,
I like you idea, but instead of adding new entity can we define some
generic way to use CommunicationEvent along with all kind of activity.
Like CommunicationEvent is generic DataModel, it applicable for invoice,
workEffort, marketing campaign, contact list, order , return, etc.
As p
Hi Devs,
In OOTB we are having the ability to record order specific communication in
*CommunicationEventOrder* and the user can retrieve/review them from party
> communications screen but we don't have such support for return
communications. So It would be great to have an ability to record return
