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
