[
https://issues.apache.org/jira/browse/OFBIZ-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718322#action_12718322
]
Mridul Pathak commented on OFBIZ-2581:
--------------------------------------
Currently status for bounced email is set in commevent status, which I think,
is a interest of marketing. So, if we remove commevent status column, user
won't be able to see the list of bounced emails. In that case, there is an
option to change the functionality for bounced emails to set the status is
commeventrole status, which will need to add another status type
"COM_ROLE_BOUNCED" for commeventrole. Or, for now, show both the statuses.
> 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.
