[
https://issues.apache.org/jira/browse/OFBIZ-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717956#action_12717956
]
Hans Bakker commented on OFBIZ-2581:
------------------------------------
I would like to suggest to use the CommunicationEventAndRole view for this
report and use the status roleStatusId. currently can have the values: entered,
read and completed(closed).
Use the roleTypeId for the role of the particular party whic can be addressee,
recipient, CC and BCC.
Because this status is party dependent we should not use the status on the
communicationevent for this.
Please also note that the COM_READ status is removed because this status is
only applicable for a certain party and not applicable for the communication
event in general.
Regards,
Hans
> Update communication event status as read in CommunicationEvent entity on the
> basis of status updated in CommunicationEventRole entity.
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: OFBIZ-2581
> URL: https://issues.apache.org/jira/browse/OFBIZ-2581
> Project: OFBiz
> Issue Type: Improvement
> Affects Versions: SVN trunk
> Reporter: Ratnesh Upadhyay
> Assignee: Ashish Vijaywargiya
> Priority: Minor
> Fix For: SVN trunk
>
> Attachments: com-read-status-ofbiz-2581.patch
>
>
> - In marketing > Reports > Email Status Report
> The resultant report is not showing the status of all those communication
> events which are in read status. In present system it is handled in
> CommunicationEventRole entity. Here we have "COM_ROLE_READ" status for all
> those communication events that are opened by the user (read by the
> recipient) but when we saw those communication events from report tab they
> are listed as completed status, because displayed list is prepared via
> "CommunicationEvent " entity and there is no any status update in case of
> read. (because updated in CommunicationEventRole entity)
> Apart from this if we have a look on those communication events that are in
> bounced status due to invalid email address , are updated in
> CommunicationEvent entity as well.
> So for updating status of a communication event as read , we wrote an ECA
> rule, to update CommunicationEvent entity's record to COM_READ , when the
> status of CommunicationEventRole is changed to COM_ROLE_READ. So that we can
> get all those communication events, that has read status from
> "CommunicationEvent" entity.
> Please suggest the proper approach from the above given solution. Or any
> other better approach, if any.
> Thanks in advance.
> --
> Ratnesh Upadhyay
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
