ofbiz-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ratnesh Upadhyay (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (OFBIZ-9911) Add ability to record Return Communication
Date Sat, 25 Nov 2017 14:32:00 GMT

    [ https://issues.apache.org/jira/browse/OFBIZ-9911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265728#comment-16265728
] 

Ratnesh Upadhyay edited comment on OFBIZ-9911 at 11/25/17 2:31 PM:
-------------------------------------------------------------------

*Quick Update:* I am done with the feature implementation, now system started recording return
related communications. Also user should be able to find and view communication by return
from newly added screen. Attached patch and will share technical summary and verification
details soon.




was (Author: upadhyay.ratnesh):
*Quick Update:* I am done with the feature implementation, now system started recording return
related communications. Also user should be able to find and view communication by return
from newly added screen. I'll share technical summary and verification details soon.



> Add ability to record Return Communication
> ------------------------------------------
>
>                 Key: OFBIZ-9911
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-9911
>             Project: OFBiz
>          Issue Type: New Feature
>          Components: order, party
>            Reporter: Ratnesh Upadhyay
>            Assignee: Rishi Solanki
>         Attachments: OFBIZ-9911.patch
>
>
> 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 specific communication in the system.
> We have to implement following items to establish this feature :
> *Data Model Details:*
> - We will have to create new entity CommunicationEventReturn to record return communication.
It should have returnId and communicationEventId along with other necessary fields.
> - We have to implement following view CommunicationEventAndReturn to fetch return communications
over screens as needed.
> *New Implementation Details:*
> - We have to add CRUD services for the new entity. 
> *Existing Implementation Details:*
> - We have to extend createCommunicationEvent service definition with retunId field and
extend the existing implementation to create the record in CommunicationEventReturn based
on supplied returnId parameter.
> - Also, we have to extend return related email services to provide returnId in service
context.
> *User Interface Details:*
> - In the current system we have Party > Communications > Find Communication By
Order screen, in the same way, we can add another screen to find communication by return.
> - We can add return communication screenlet over Order Manager > Return > Return
History screen or we can add communication tab under Order > Return screen, this is just
a thought still thinking on it.
> - We can also provide communication tab in order component as well.
> Thanks to [~jacques.le.roux], [~rishisolankii] and [~deepakddixit] for discussion and
inputs.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message