[jira] [Resolved] (OFBIZ-10855) Store Order Service Imrovements
[ https://issues.apache.org/jira/browse/OFBIZ-10855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rishi Solanki resolved OFBIZ-10855. --- Resolution: Fixed > Store Order Service Imrovements > --- > > Key: OFBIZ-10855 > URL: https://issues.apache.org/jira/browse/OFBIZ-10855 > Project: OFBiz > Issue Type: Improvement > Components: order >Reporter: Rishi Solanki >Assignee: Rishi Solanki >Priority: Major > Fix For: Trunk > > Attachments: OFBIZ-10855.patch > > > Few OrderHeader level values not passed and stored in storeOrder service. > Also no code support exists for those order header fields. Below are the > fields which is not taken care by the service code. We can add conditional > support for these field, that means if the value comes in parameter then it > will be stored otherwise not. > - priority > - isRushOrder > > These values can be reset after creating order by using updateOrderHeader > service, but I think this should be fine to have these and other missing > values of header level as IN parameters and handled by the service. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OFBIZ-10855) Store Order Service Imrovements
[ https://issues.apache.org/jira/browse/OFBIZ-10855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rishi Solanki resolved OFBIZ-10855. --- Resolution: Fixed The patch has been committed in trunk revision 1855102. Thanks to [~harshvijay] for your contribution. > Store Order Service Imrovements > --- > > Key: OFBIZ-10855 > URL: https://issues.apache.org/jira/browse/OFBIZ-10855 > Project: OFBiz > Issue Type: Improvement > Components: order >Reporter: Rishi Solanki >Assignee: Rishi Solanki >Priority: Major > Fix For: Trunk > > Attachments: OFBIZ-10855.patch > > > Few OrderHeader level values not passed and stored in storeOrder service. > Also no code support exists for those order header fields. Below are the > fields which is not taken care by the service code. We can add conditional > support for these field, that means if the value comes in parameter then it > will be stored otherwise not. > - priority > - isRushOrder > > These values can be reset after creating order by using updateOrderHeader > service, but I think this should be fine to have these and other missing > values of header level as IN parameters and handled by the service. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
