ofbiz-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rishi Solanki (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OFBIZ-9911) Add ability to record Return Communication
Date Thu, 18 Jan 2018 11:38:00 GMT

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

Rishi Solanki commented on OFBIZ-9911:
--------------------------------------

The patch has been committed in trunk -r1821486. Thanks for your contribution [~upadhyay.ratnesh]
and [~aishwary] for testing.

> 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
>            Priority: Major
>         Attachments: OFBIZ-9911-CommunicationEventReturn-Entity.jpg, OFBIZ-9911-FindCommByReturn-FilterRecords-Screen.jpg,
OFBIZ-9911-FindCommunicationByReturn-Screen.jpg, OFBIZ-9911.patch, OFBIZ-9911.patch, 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
(v7.6.3#76005)

Mime
View raw message