Thank you all for your inputs. We will be addressing the issue under - https://issues.apache.org/jira/browse/OFBIZ-10855 <https://www.google.com/url?q=https://issues.apache.org/jira/browse/OFBIZ-10855&sa=D&source=hangouts&ust=1552211567783000&usg=AFQjCNH8QA2mEITWPpldKVF10aN-ny_LdA>
Best Regards, -- Rishi Solanki Sr Manager, Enterprise Software Development HotWax Systems Pvt. Ltd. Direct: +91-9893287847 http://www.hotwaxsystems.com www.hotwax.co On Tue, Mar 5, 2019 at 9:16 AM Swapnil M Mane <swapnilmm...@apache.org> wrote: > +1 > > > - Best Regards, > Swapnil M Mane > > > On Fri, Mar 1, 2019 at 3:22 PM Rishi Solanki <rishisolan...@gmail.com> > wrote: > > > Dear All, > > While working with storeOrder service, I observe that few order header > > level values not passed and stored in that service. Also no code support > > exists for those order header fields. Below are the fields which is not > > taken care by the service code, please let me know if 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. > > > > Please let me know in case of any objections, I would like to commit the > > proposed changes. > > > > Best Regards, > > -- > > Rishi Solanki > > Sr Manager, Enterprise Software Development > > HotWax Systems Pvt. Ltd. > > Direct: +91-9893287847 > > http://www.hotwaxsystems.com > > www.hotwax.co > > >
