You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by Hans Bakker <h....@antwebsystems.com> on 2006/11/26 02:52:31 UTC
mail client in OFbiz (was commit: r478095)
David, Si and others interested.
The reason i added the code to delete the workeffort also, was indeed what Si
mentioned. I see this is not the right way and will revert this change and if
there is no objection I will add another service like
deleteCommunicationEventWorkeffort.
Currently I am very close to implement an email client which is based on a
very good idea of Si to link a communicationevent with an activity
(workeffort) When an email is received it normally needs action anyway which
is reflected nicely in the activity. However I extended this in a such a way
that the activity can contain more than one communicationEvent to keep all
emails, phoneCalls, faxes together which discuss the same subject i.e. a
thread.
Further, when an email comes in and the sender is not known, the email can be
allocated to an existing party or a new party can be created with one click
using the information on the email.
One problem i have however is that email client needs code in a heavily
modified crmsfa system from Si and is currenty used in my SharedOfbiz system
which allows many companies using the same ofbiz system and database.
Because Email processing is a critical process within a company, isn't it a
good idea to add this to the standard Ofbiz system? This means however that
code from crmsfa and sharedofbiz need to be moved. Si, do you have any
objections moving code related to this function into the standard ofbiz
system?
--
Regards,
Hans Bakker
ANT Websystems Co.,Ltd (http://www.antwebsystems.com)
If you want to verify that this message really originates from
from the above person, download the public key from:
http://www.antwebsystems.com/hbakkerAntwebsystems.asc
Re: mail client in OFbiz (was commit: r478095)
Posted by David E Jones <jo...@undersunconsulting.com>.
On Nov 25, 2006, at 6:52 PM, Hans Bakker wrote:
> The reason i added the code to delete the workeffort also, was
> indeed what Si
> mentioned. I see this is not the right way and will revert this
> change and if
> there is no objection I will add another service like
> deleteCommunicationEventWorkeffort.
Yes, this is a bit dangerous as is and should be reverted. A special
service to do this for this circumstance would be fine.
> Currently I am very close to implement an email client which is
> based on a
> very good idea of Si to link a communicationevent with an activity
> (workeffort) When an email is received it normally needs action
> anyway which
> is reflected nicely in the activity. However I extended this in a
> such a way
> that the activity can contain more than one communicationEvent to
> keep all
> emails, phoneCalls, faxes together which discuss the same subject
> i.e. a
> thread.
How does this relate to the existing threading functionality modeled
as an hierarchy using the CommunicationEvent.parentCommEventId field.
Note that there is also a CommunicationEvent.origCommEventId but I
believe that is intended for when a CommunicationEvent is copied from
another.
-David