Re: Welcome to Priya Sharma as new committer!
Many congratulations Priya!! Welcome aboard!! Regards. Mridul Pathak On Thu, Mar 11, 2021 at 6:31 PM Pawan Verma wrote: > The OFBiz PMC has invited Priya to become a new committer and we are > pleased to announce that she has accepted the nomination. > > Welcome onboard Priya, more power to you! > > > Pawan >
Re: Welcome Akash Jain as new PMC member
Welcome aboard Akash!! Many Congratulations!! Regards. Mridul Pathak On Thu, Jan 28, 2021 at 10:10 PM Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > The OFBiz PMC has invited Akash Jain to become member of the committee and > we are glad to announce he has accepted the nomination. > > On behalf of the OFBiz PMC, welcome Akash! > >
Re: Welcome Girish Vasmatkar as new PMC member
Welcome aboard Girish!! Many Congratulations!! Regards. Mridul Pathak On Thu, Jan 28, 2021 at 10:10 PM Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > The OFBiz PMC has invited Girish Vasmatkar to become member of the > committee and we are glad to announce he has accepted the nomination. > > On behalf of the OFBiz PMC, welcome Girish! > >
Re: Welcome to Daniel Watford as new committer!
Congratulations Daniel, welcome aboard!! Regards, Mridul Pathak On Thu, Dec 31, 2020 at 9:50 PM Jacopo Cappellato < jacopo.cappell...@gmail.com> wrote: > The OFBiz PMC has invited Daniel to become a new committer and we are > pleased to announce that he has accepted the nomination. > > Welcome onboard Daniel! > > Jacopo >
Re: [PROPOSAL] Separate login service for API calls
+1 Thanks. Mridul Pathak On Tue, Sep 29, 2020 at 1:29 PM Michael Brohl wrote: > +1 > > With an addition: we should do the implementation in a way that the > user/password matching is implemented only once and used in both login > methods (not just copy & paste into another method). > > It might take some refactoring to pull these part out of the login event. > > Best regards, > > Michael Brohl > > ecomify GmbH - www.ecomify.de > > > Am 29.09.20 um 09:43 schrieb Jacopo Cappellato: > > +1 > > > > Jacopo > > > > On Sat, Sep 26, 2020 at 6:35 AM Girish Vasmatkar < > > girish.vasmat...@hotwaxsystems.com> wrote: > > > >> Hi > >> > >> I am using userLogin service to authenticate users before generating > auth > >> tokens for REST API and GraphQL calls. However, I figured that a > session is > >> also getting created and returned in response which is defeating the > >> purpose of having an API in place. Even though that session is not > getting > >> used anywhere when subsequent calls are made using the token, I still > think > >> it is an extra session lying around in tomcat's session cache. > >> > >> I propose to implement a new basic userLogin service > (basicAuthUserLogin) > >> that would just do username/password matching and be done with it > without > >> ever calling request.getSession(). This will ensure that APIs are > stateless > >> and no session is generated. > >> > >> Anything else you think should be part of the new service instead of > just > >> username/password validation? > >> > >> Best, > >> Girish > >> HotWax Systems > >> > >
Re: Encoding issues with product names
Hi Amit,
I agree with Jacques. Though I see that in shopping cart implementation
when copying product name to order item name it uses string encoding vs
html encoding, I think this could be fixed to use html encoding for
product/item name like it's done for product/item description in the same
method.
Thanks.
Mridul Pathak
On Mon, Sep 28, 2020 at 2:21 PM Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:
> Hi Amit,
>
> It's better to encode to prevent XSS. Then of course we need to decode
> when showing those values.
> Actually in this case it's automatically encoded by Freemarker as
> explained in this old but still good reference:
> https://ofbiz.markmail.org/thread/e2iznsqhhxxdplxh
>
> So we can do the same, ie using StringUtil.wrapString(), like
>
> value="${StringUtil.wrapString(cartLine.getName(dispatcher))?default("")}"/> />
>
> This should be done everywhere it's needed in FTL files.
>
> I have added a patch for similar "cartLine.get...()" cases at OFBIZ-12029.
> Of course other cases like that can pop out anytime; eg, I'll also fix a
> long awaiting one at OFBIZ-7343...
>
> We could think that using Freemarker autoescaping as suggested in
> OFBIZ-7675 would be better.
> But escaping is not encoding. You can check by using ?html (local
> autoescaping ) instead of StringUtil.wrapString(). You get
> "tes't"
>
> For widgets forms, there is a problem currently investigated with
> OFBIZ-12026...
>
> HTH
>
> Jacques
>
> Le 26/09/2020 à 11:00, Amit Gadaley a écrit :
> > Hello All,
> >
> > Recently working for a client I encountered a weird issue related to
> > special characters encodings. We have product names containing special
> > characters like ' (apostrophes). When we create orders for it, an encoded
> > value for it is stored in OrderItem.itemDescription. The same encoded
> value
> > also copied for invoice and return. When I checked the Product entity
> > record, the original value (name without encoding) was stored there. I
> > debugged the issue at code level and found that the system does encoding
> > (string or html) at the time of order creation.
> >
> > I understand that for security reasons (and I want to know more about
> it),
> > the system does the encodings. My concerns are related to not using
> > encoding when we create products. And it is not good UI experience to
> > display encoded forms of values to screens.
> >
> > I suggest we should use some methods to display encoded values properly
> on
> > screens or remove the encoding at the very first place.
> >
> > Please feel free to provide any suggestions or inputs.
> >
>
Re: Welcome Mridul Pathak as new PMC member!!
Thank you all for kind wishes, love being part of this community!! Regards, Mridul Pathak On Sat, Sep 26, 2020 at 6:22 PM Deepak Dixit wrote: > Many many congrats Mridul > > Thanks & Regards > — > Deepak Dixit > > On Sat, 26 Sep 2020 at 6:09 PM, Pranay Pandey < > pranay.pan...@hotwaxsystems.com> wrote: > > > Many congratulations Mridul! > > > > > > > > Best regards, > > > > Pranay Pandey > > > > > > > > > > > > On Fri, Sep 18, 2020 at 12:55 PM Ashish Vijaywargiya > > > > wrote: > > > > > > > > > The OFBiz PMC has invited Mridul Pathak to become a member of the > > committee > > > > > and we are glad to announce that he has accepted the nomination. > > > > > > > > > > On behalf of the OFBiz PMC, welcome on board Mridul! > > > > > > > > > -- > Thanks & Regards > — > Deepak Dixit >
Re: Welcome Swapnil Shah as new PMC member!!
Many congratulations Swapnil!! Thanks, Mridul Pathak On Mon, Sep 28, 2020 at 11:13 AM Deepak Dixit wrote: > Many many congrats Swapnil > > Kind Regards, > Deepak Dixit > > > > On Sat, Sep 26, 2020 at 8:14 PM Pranay Pandey < > pranay.pan...@hotwaxsystems.com> wrote: > > > Congratulations Swapnil! > > Best regards, > > Pranay Pandey > > > > > > On Sat, Sep 26, 2020 at 7:10 PM Swapnil Shah < > > swapnil.s...@hotwaxsystems.com> > > wrote: > > > > > Thank you everyone for your continuous support and kind wishes. > > > > > > Thanks, > > > Swapnil > > > > > > > -Original Message- > > > > From: Ashish Vijaywargiya > > > > Sent: 18 September 2020 12:56 > > > > To: dev@ofbiz.apache.org > > > > Subject: Welcome Swapnil Shah as new PMC member!! > > > > > > > > The OFBiz PMC has invited Swapnil Shah to become a member of the > > > committee > > > > and we are glad to announce that he has accepted the nomination. > > > > > > > > On behalf of the OFBiz PMC, welcome on board Swapnil! > > > > > >
Re: [VOTE] to use Lombok inside OFBiz
-1 Don’t think it’s of much use in OFBiz. Thanks. Mridul Pathak > On 08-Sep-2020, at 1:06 PM, Jacques Le Roux > wrote: > > Hi, > > Following our discussions about using Lombok inside OFBiz, as it's not clear > if we should, here is a vote to decide about that. > > The question is: "should we use Lombok inside OFBiz?" > > Please cast your vote: > > [+1] to use Lombok inside OFBiz > [0] to abstain > [-1]to not use Lombok inside OFBiz > > This vote will be open for a week. > > Thanks > > Jacques >
Re: Headless Commerce Plugin for OFBiz
+1. This is a great suggestion. OFBiz has been mainly adopted for its business applications, eCommere being one of the top ones. Though its tightly coupled nature doesn’t make it well suited for the modern day web or mobile application development. It definitely needs to be revamped to make it more relevant in this ever changing world of technology. Of course there will be some challenges that would need to be addressed to be able to build a truly REST API but that opens up the path to the long needed refactoring/reimplementation of some of these business processes and objects, for example shopping cart. It is high time that we start taking steps to move from somewhat monolithic implementation towards a more micro service based approach and eCommerce would be a great start. Headless capabilities are must and dedicated plugins could be a great way to expose existing business functions as REST APIs in the form of micro services without needing to change the core implementation much. The newly introduced REST plugin would play a major role in this journey. Thanks. Mridul Pathak > On 20-Aug-2020, at 12:40 PM, Deepak Dixit wrote: > > Hi Arpit, > > Sounds like a plan, As now ofbiz supports rest, so we can think of headless > commerce. > > I think you need to work on the B2C ordering process, as per current > implementation it's tightly coupled with ShoppingCart. > All the e-commerce related processes are bound with ShoppingCart and OFBiz > use session to maintain shoppingCart. > > > > Thanks & Regards > -- > Deepak Dixit > ofbiz.apache.org > > > On Tue, Aug 18, 2020 at 8:52 PM Arpit Mor > wrote: > >> Hi Devs, >> >> Hope everyone is safe and healthy amidst Covid-19 pandemic >> >> Most of you might have heard about “Headless Commerce” or API first >> commerce, but in case you haven’t, here is a brief summary of what headless >> commerce is and why it is the need of the hour. >> >> What is Headless Commerce? >> In its simplest form, headless commerce is the decoupling of the >> presentation layer (frontend) of an eCommerce from backend such that both >> are able to function independently. This decoupling is achieved by using >> APIs to expose core backend functionalities. >> >> Why Headless Commerce? >> Today, customers are consuming context from various channels and >> touch-points. Gone are the days when customers primarily needed to visit a >> website to buy online. With the rise of smartphones and the Internet of >> Things (IoT), customers can now shop from multiple channels like IoT >> devices, progressive web apps (PWAs), social media platforms, mobile apps, >> smart assistants, smart TV, kiosks, and many more. >> By decoupling frontend from backend - user interface, social commerce, >> mobile apps, IoT, and many more – can be changed or updated individually, >> without interfering with backend. Data is available to separate frontend >> applications via API calls and the backend runs invisibly in the >> background. >> >> Benefits of Headless Commerce >> Unlimited Channels and Touchpoints: With API first Headless Commerce, >> integration with the new channels and touchpoints becomes easy, economical, >> and quick. >> >> Innovation and Engaging User Experience: With traditional monolithic >> Commerce, making user-centric changes to your website requires both a front >> and backend transformation. But with headless commerce, all the >> frontend/app developers have to focus on is user experience, >> personalization, and consistency without having to worry about changes to >> the backend. >> >> Easy-to-Manage Integrations: Headless commerce not only includes providing >> API support to the frontend, but it also includes communication between >> various components (like ERP, WMS, OMS, CRM, POS, etc.) via APIs. This will >> reduce the complexity of the integration and its maintenance. >> >> Business Agility & less time to market: Companies must be able to respond >> quickly to new market opportunities by constantly releasing new features. >> In traditional commerce, each component is tightly coupled with another >> which makes changes a complex task. But with Headless commerce different >> components communicate via APIs, which make changes to one component easy >> without having to worry about changes to other components. >> >> I’d like to put forward a suggestion for developing a headless commerce >> plugin, to keep the competitive edge of OFBiz with the rapidly changing >> technological trends by exposing core backend functionalities via APIs (The >> REST capabilities are already added to OFBiz recently). >> >> Looking forward to suggestions and feedback. >> >> Thanks & Regards >> Arpit Mor >>
Re: Welcome to Devanshu Vyas as new committer!
Many Congratulations Devanshu!! Regards, Mridul Pathak > On 19-Aug-2020, at 2:31 PM, Pawan Verma wrote: > > The OFBiz PMC has invited Devanshu Vyas to become a new committer and we > are happy to announce that he has accepted this role. > > Some of the reasons for inviting Devanshu Vyas include: > > - He is invested in the OFBiz project and has been a member for many years > - He is taking an initiative towards improving the system > - He has functional experience in various areas of the framework > - He enjoys working with the community and collaborating with others > > Please join me in welcoming and congratulating Devanshu! > > Cheers > Pawan Verma > ofbiz.apache.org
Re: Moving third party shipping integrations from applications to plugins
Thanks everyone for the feedback. I have created OFBIZ-11961 <https://issues.apache.org/jira/browse/OFBIZ-11961> to track this. Regards Mridul Pathak > On 17-Aug-2020, at 10:49 AM, Arun Patidar wrote: > > +1 > > > > Regards > --- > Arun Patidar > > > > On Mon, Aug 17, 2020 at 10:16 AM Pritam Kute > wrote: > >> Hello Mridul, >> >> Indeed it is good design. +1 for the introduction of entity >> "ProductStoreShipmentSettings". >> >> Kind Regards, >> -- >> Pritam Kute >> >> >> On Fri, Aug 14, 2020 at 10:57 PM Jacques Le Roux < >> jacques.le.r...@les7arts.com> wrote: >> >>> +1 >>> >>> Jacques >>> >>> Le 14/08/2020 à 12:12, Pawan Verma a écrit : >>>> Hi Mridul, >>>> >>>> Thanks for bringing this to attention. >>>> >>>> It is a really good idea. Currently, all the shipment integrations >>>> are grappled to simply that "ProductStoreShipmentSettings" entity would >>> be >>>> a game-changer. >>> >>> >>
Moving third party shipping integrations from applications to plugins
Hi, Recently, discussion around moving third party integrations has been initiated again on dev mailing list thread <https://lists.apache.org/thread.html/rf7967b26b89d753388ccee364643f502c72e781da54fe6d5aca1577f@%3Cdev.ofbiz.apache.org%3E> and was also discussed in past on dev mailing list thread <https://lists.apache.org/thread.html/e2a2b5598fb4314062beca47e0522434852d0189e888e36852b5a6cd@%3Cdev.ofbiz.apache.org%3E>. When reviewing third party shipping integration in this context, I noticed that some of the shipping integration services (example, upsShipConfirm, fedexShipRequest, etc.) are hard coded at places in product and order components and in shipment workflow in facility application. There could be some other such occurrences as well. Ideally these third party services needs to be configurations and to be able to move these shipping integrations out of applications to plugins some refactoring is needed so as to not loose any existing support in OFBIz applications. We do have ProductStoreShipmentMeth entity for configurations but it is more specific to detailed shipment method level configurations rather than carrier level configurations. We also have carrier level shipping gateway configuration entities like ShipmentGatewayUPS, etc. But again these are more specific to store connectivity configurations. I feel that we need more like a ProductStorePaymentSettings entity to configure various possible integration services (like rate service, request label service, address verification service, etc.) offered by these third party logistic services. I propose to introduce a new entity “ProductStoreShipmentSettings” to configure available shipping gateway services for shipping carriers at product store level. To begin with the entity could have following fields, 1. productStoreId (pk) 2. carrierPartyId (pk) 3. shipmentServiceEnumId (pk) 4. shipmentService 5. shipmentGatewayConfigId (Ideally this field should become party of this new entity, though it is currently supported in ProductStoreShipmentMeth entity) The above change would enable us to refactor these hardcoded reference to make them configurable and be able to move these integrations to plugins without loosing any available support in applications. Looking forward to suggestions and feedback. Thanks. Mridul Pathak
Re: Repository Management For Third-Party Plugins
Hi Pawan, Though few years ago I was advocate of the approach #2 that you have suggested here, now I think that #1 is the best approach. In real time implementations the idea of plugins is to be able to use only what you need. Like for payment integrations you selectively use the gateways, mostly one. So it should be as easy to drop the plugin for your preferred gateway and use it, you shouldn’t need to unnecessarily have to code of all other payment integrations that you don’t need. Also, from maintenance perspective even though some of these third party integrations could be categorised but still each of them have their own API specification, configurations and they need to be maintained separately. So, my vote would be to #1 that is to create separate plugins for each third party integration. Thanks. -- Mridul Pathak > On 30-Jul-2020, at 8:34 PM, Pawan Verma wrote: > > Hi Pritam, > > I am also more inclined to not create a different repository for > third-party-plugins. As we can have any number of plugins in OFBiz and > Users can set up required plugins as per their need. > > I would suggest creating separate plugins for each third-party integration > like ups, firstdatapaymentgateway, etc that way if the user wants only a > specific gateway or plugins can have only that one. > > I suggest two approaches: > #1: Create a separate plugin for each integration and put them into the > plugins directory. > > #2: Club all the related plugins into one directory and can add that parent > directory in base/config/component-load.xml. The benefit of this approach > is we can have all payment or other gateways in one place and also don't > need to create a separate repository for the third-party-plugins. > Example for shipping gateways: > > 1. Club all shipping gateways into the plugins/shipping-gateway directory > 2. Add this shipping-gateway into base/config/component-load.xml > as > > If we follow the #2 approach we may need to improve our plugin setup Gradle > target i.e. pullPluginSource. > > Please let me know your thoughts and I can provide more detail if needed. > > Best > Pawan
Re: Welcome Pawan Verma as new PMC member
Many congratulations Pawan!! Thanks. -- Mridul Pathak > On 28-Jul-2020, at 1:21 PM, Jacques Le Roux > wrote: > > The OFBiz PMC has invited Pawan Verma to become member of the committee and > we are glad to announce that he has accepted the nomination. > > On behalf of the OFBiz PMC, welcome on board Pawan! >
Re: Repository Management For Third-Party Plugins
I recall having at length discussions on this topic in the mentioned ticket back then. I too was a bit concerned about having too many plugins for similar type of code like payment integration or shipping integrations. But now when I think of it again, the core idea behind plugin architecture is to be able to build any number of plugins on an existing product/framework. So I think it’s fine having any number of individual plugins for these third party integrations, in fact many of the plugins today are third party integrations. We shouldn’t be needing another repository for this. Though I would definitely suggest that we should review each of these third party integrations and only move those which are valid implementations today. There could be certain integrations which might be deprecated or defunct now due to lack of maintenance and needs to be updated or rewritten for their latest versions. It could be a good idea to create place holder Jira issues for reimplementation for contributors to pick. Thanks. -- Mridul Pathak > On 25-Jul-2020, at 11:59 AM, Pritam Kute > wrote: > > Hello Devs, > > Recently, we have pushed integration of the First Data payment gateway to > OOTB. When we were doing that, we got one question about repository > management for third-party applications. We have one ticket [1] open in > JIRA about moving third party code from framework to separate repositories > to make framework lightweight. > > Now the question is how we are going to manage the repository structure for > third party integration codes. If we talk about payment gateways, we have > around 12 different integrations available in the framework component. If > we move them to plugins as a separate plugin, it will increase the number > of plugins in the plugin repository. I am personally not in favor of that. > We should have some type of repository categorization there. One > categorization I would like to suggest is to have separate repository all > together for third party integrations and to have a Gradle task to fetch > only required third party integration inside plugins directory as like we > have done for plugins repository itself: > apache - >-- ofbiz-framework >-- ofbiz-plugins >-- *ofbiz-thrid-party* >-- ofbiz-site >-- ofbiz-tools > > I would like to invite thoughts on this so that we can proceed with the > migration of third party code out of the framework. > > [1] https://issues.apache.org/jira/browse/OFBIZ-7415 > > Kind Regards, > -- > Pritam Kute
Re: Nested attributes for Collection Types
Hi Girish, I think this would be a good improvement to service definition. While it makes more sense that it would enable creating JSON like schema definitions it would make service definitions more predictable in general. This improvement could also be applied to existing service definitions to be able to expose them as an API in a more sensible way. Thanks. -- Mridul Pathak > On 16-Jul-2020, at 5:20 PM, Girish Vasmatkar > wrote: > > Hey Guys, > > While working on OpenApi integration as well as GraphQL implementation, I > faced issues on how to automatically document request/response JSON > structure for service attributes that were of Collection types (Map, List > etc). > > For simple types, it is just plain easy but when it comes to Map/Lists, you > have to know what exactly is inside them to be able to convey properly in > the OpenApi schema. > > I was thinking to may be try to introduce nested attributes in service > definition such that if the attribute type is Map/List, you can actually > specify what goes inside that attribute - > > > > > > > > > > > > With this change, it becomes possible to generate the schema for the > service attribute, Where as if we don't have this option, we can't possibly > indicate what the structure of the "header" key is going to be if it was > represented in JSON format. > > Of course, this change will only help documentation and GraphQL > implementation and that there is very little case for it to benefit a > general OFBiz service call. > > Any thoughts or comments on this? Is this too big of a change (impact wise > and not coding perspective) to avoid it and consider something else? Has > this been discussed before? > > Best, > Girish
Re: Welcome Aditya Sharma as new PMC member
Many Congratulations Aditya!! Thanks. -- Mridul Pathak > On 05-Jul-2020, at 10:23 PM, Jacques Le Roux > wrote: > > The OFBiz PMC has invited Aditya Sharma to become member of the committee and > we are glad to announce that he has accepted the nomination. > > On behalf of the OFBiz PMC, welcome on board Aditya! >
Re: Welcome Suraj Khurana as new PMC member
Many Congratulations Suraj!! Thanks. -- Mridul Pathak > On 04-Jul-2020, at 5:22 PM, Jacques Le Roux > wrote: > > The OFBiz PMC has invited Suraj Khurana to become member of the committee and > we are glad to announce that he has accepted the nomination. > > On behalf of the OFBiz PMC, welcome on board Suraj! >
Re: Welcome Arun Patidar as new PMC member
Many Congratulations Arun!! Thanks. -- Mridul Pathak > On 06-Jul-2020, at 12:30 PM, Jacques Le Roux > wrote: > > The OFBiz PMC has invited Arun Patidar to become member of the committee and > we are glad to announce that he has accepted the nomination. > > On behalf of the OFBiz PMC, welcome on board Arun! >
Re: IMPROVEMENT: Checkstyle formatting issues
+1 Thanks. -- Mridul Pathak > On 30-May-2020, at 9:55 PM, Suraj Khurana wrote: > > Hello Devs, > > Hope you are doing good !! > > Currently, there are many checkstyle issues in code base which are due to > formatting best practices, like indentation, using spaces before/after > symbols etc. > > We can solve many thousands of such issues by correcting all such > occurrences. Please share your thoughts on this. > > A known thing is that we will lose the last history of such codebase while > doing this re-factoring. > > Any other ideas to solve the problem are most welcome. > -- > Best Regards, > Suraj Khurana > Senior Technical Consultant
Re: LineLength for checkstyle
+1 Thanks. -- Mridul Pathak > On 23-May-2020, at 8:59 PM, Suraj Khurana wrote: > > Hello Devs, > > Recently we are facing some checkstyle issues and one cause of it is > LineLength property. > Currently we have set it to 120, I think we should make it to 150 instead. > It is pretty visible in 13/14 font sizes as well. > > Please share your thoughts on this. > > -- > Best Regards, > Suraj Khurana > Senior Technical Consultant
Re: @deprecated No replacement
+1 to remove references. Thanks. -- Mridul Pathak > On 22-May-2020, at 1:03 PM, Jacques Le Roux > wrote: > > Hi, > > We have 5, 8 years old, , "@deprecated No replacement" references in Java > code: > https://ofbiz.markmail.org/search/?q=%22%40deprecated+No+replacement%22 > > It seems they are all related to Minilang. I think we should either remove > the concerned methods. > > Or rather, easier, remove the "@deprecated No replacement" references since > anyway Minilang is deprecated as a whole. > > I'm for the later and will do so in a week if nobody is against. > > Jacques >
Re: Modify OFBiz commit message template
+1 Thanks. -- Mridul Pathak > On 20-May-2020, at 2:31 PM, Jacques Le Roux > wrote: > > Hi, > > With Git IMO it's convenient (more information) to have the Jira number in > the title, eg: https://markmail.org/message/cyslglyoh5gf7l7t > > If nobody disagree I'd like to modify > > https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+commit+message+template > > We could have > > > > [Implemented | Improved | Fixed | Completed| Documented | Reverted]: [Jira > title | Free text] [(OFBIZ-)] > > [(OFBIZ-)] > > [More detailed explanation of what has been done and what the fix achieves, > sideeffects etc.] > > [Thanks:] [ for ... and for] > > > > But I would prefer: > > [Implemented | Improved | Fixed | Completed| Documented | Reverted]: [Jira > title | Free text] [(OFBIZ-)] > > [More detailed explanation of what has been done and what the fix achieves, > sideeffects etc.] > > [Thanks:] [ for ... and for] > > > Opinions? > > Thanks > > Jacques >
Re: Welcome Rishi Solanki as new PMC member
Congratulations Rishi!! Thanks Mridul Pathak > On 28-Apr-2020, at 7:52 PM, Jacopo Cappellato > wrote: > > The OFBiz PMC has invited Rishi Solanki to become member of the committee > and we are glad to announce that he has accepted the nomination. > > On behalf of the OFBiz PMC, welcome on board!
Re: Valid Item Status for partial shipment
The way order statuses works today seems to be fine, OrderReadHelper has the necessary methods to get additional details for the order item. 1) If order item is partially shipped and remaining quantity is pending you could get the shipped quantity from OrderReadHelper. Approved status seems valid here. 2) If order item is partially shipped and remaining quantity is cancelled, the cancelled quantity is stored in OrderItem.cancelQuantity. Again you could get the shipped quantity and cancelled quantity from OrderReadHelper. Completed status seems valid here. Thanks. Mridul Pathak > On 25-Apr-2020, at 10:57 AM, Mohammad Kathawala > wrote: > > Hello Shikha, > > The statuses mentioned by you in all the scenarios seem correct to me and > AFAIK it works in the same way in OFBiz. We can definitely improve it by > adding a 'Partially Complete/Partially Fulfilled' status to an order item > as mentioned by Pawan. > > Thanks & Regards > Mohammad Kathawala > > On Tue, Apr 14, 2020 at 6:03 PM Suraj Khurana > wrote: > >> Adding Dev ML. >> >> -- >> Best Regards, >> Suraj Khurana >> Senior Technical Consultant >> >> On Tue, Apr 14, 2020 at 5:13 PM Shikha Jaiswal < >> shikha.jais...@hotwaxsystems.com> wrote: >> >>> Hello team, >>> >>> From the business point of view, please share what should be the exact >>> status of an item after approval, if it is being shipped partially. >>> >>> Suppose an order item is of 3 qty and all three are split down into >>> separate ship groups and shipped one by one, what should be the ideal >>> status on each following instances, as we maintain item status on >> OrderItem >>> level only, not specific to OISGA: >>> >>> - One item is shipped, two are pending. >>> -- IMO, it should be Approved as there are still pending items, please >>> confirm. >>> >>> - Two items are shipped, one is pending. >>> -- IMO, it should be Approved as there are still pending items, please >>> confirm. >>> >>> - Two items are shipped, one is canceled. >>> -- IMO, it should be Completed as it is shipped or canceled, please >>> confirm. >>> >>> OR >>> >>> - All three items are shipped >>> -- IMO, it should be Completed as all items are shipped. >>> >>> Please let me know your thoughts on this. >>> >>> -- >>> Thanks & Regards, >>> Shikha Jaiswal >>> Senior Enterprise Software Engineer >>> >>
Re: [VOTE] [RELEASE] Apache OFBiz 17.12.03
+1 Thanks. -- Mridul Pathak > On 20-Apr-2020, at 2:33 PM, Jacopo Cappellato > wrote: > > This is the vote thread to release a new bug fix release for the > release17.12 branch. This new release, "Apache OFBiz 17.12.03" will > supersede the previous release from the same branch. > > The release files can be downloaded from here: > https://dist.apache.org/repos/dist/dev/ofbiz/ > and are: > * apache-ofbiz-17.12.03.zip > * KEYS: text file with keys > * apache-ofbiz-17.12.03.zip.asc: the detached signature file > * apache-ofbiz-17.12.03.zip.sha512: checksum file > > Please download and test the zip file and its signatures (for instructions > on testing the signatures see http://www.apache.org/info/verification.html). > > Vote: > [ +1] release as Apache OFBiz 17.12.03 > [ -1] do not release > > This vote will be open for 5 days. > > For more details about this process please refer to > http://www.apache.org/foundation/voting.html > > Best Regards, > > Jacopo
Re: Welcome James Young as new PMC member
Congratulations James!! Thanks. -- Mridul Pathak On Wed, Apr 22, 2020 at 2:08 PM Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > The OFBiz PMC has invited James Young to become member of the committee > and we are glad to announce that he has accepted the nomination. > > On behalf of the OFBiz PMC, welcome on board! > >
Re: Welcome Swapnil M Mane as new PMC member
Many congratulations Swapnil!! Thanks. -- Mridul Pathak On Thu, Apr 23, 2020 at 5:02 PM Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > The OFBiz PMC has invited Swapnil M Mane to become member of the committee > and we are glad to announce that he has accepted the nomination. > > On behalf of the OFBiz PMC, welcome on board! > >
Re: Welcome to Vasmatkar as new committer!
Congratulations Girish!! -- Mridul Pathak On Wed, Apr 22, 2020 at 3:09 PM Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > The OFBiz PMC has invited Girish to become a new committer and we are > pleased to announce that he has accepted. > > Girish is part of the community for near 2 years and has proposed several > smart propositions notably related to security and GraphQL, but not only. > > Please join me in welcoming and congratulating Girish. > > Jacques > > >
Re: [DISCUSSION] Organising our own OFBiz Meetup or Conference in 2017
Hi Sharan, It seems like a great idea. OFBiz user base has been constantly growing in India since last few years. -- Thanks & Regards, Mridul Pathak HotWax Systems > On Mar 30, 2017, at 3:32 PM, Sharan Foga wrote: > > Hi All > > Although I've had no responses on this thread I haven't given up because I > think it has a lot of potential. So I'd still like to have a go at organising > something just as a proof of concept :-) > > Thanks > Sharan > > On 2017-03-14 11:21 (+0200), "Sharan Foga" wrote: >> Hi Everyone >> >> I'd like bring up the topic of running an OFBiz meetup / conference again. >> It was one of the things that came up in the discussions in Apachecon >> Seville. >> >> https://s.apache.org/smos >> >> OFBiz has a strong user base and really appeals to the business community >> but many of users and companies don't go to Apachecon because it is seen as >> a developer conference. >> >> I think that we need to start engaging more with our user community and a >> conference / meetup would help do that. So I'd like to explore the idea >> (think of it as a Proof of Concept) of holding an OFBiz conference in India. >> >> Why India? I think that we have a strong user and developer base there. I >> think it could be put on very cheaply and I think it could open the door for >> us as a project to raise our profile and run other conferences in other >> locations. >> >> Funding could come through sponsorship. We have a lot of service providers >> that we could approach for funding. I know it's still high level but I'd >> like to get some initial feedback about the general concept. >> >> What do people think? >> >> Thanks >> Sharan >>
Re: [VOTE] [RELEASE] Apache OFBiz 16.11.01
+1 -- Thanks & Regards, Mridul Pathak > On Nov 22, 2016, at 12:21 AM, Jacopo Cappellato > wrote: > > This is the vote thread to issue the first release from the branch > "release16.11". > > The name of the new release will be "Apache OFBiz 16.11.01". > > The release files can be downloaded from here: > > https://dist.apache.org/repos/dist/dev/ofbiz/ > > and are: > > * apache-ofbiz-16.11.01.zip: the actual release file > > * KEYS: file with keys > > * apache-ofbiz-16.11.01.zip.asc: the detached signature file > > * apache-ofbiz-16.11.01.zip.md5, apache-ofbiz-16.11.01.zip.sha: hashes > > Vote: > > [ +1] release as Apache OFBiz 16.11.01 > > [ -1] do not release > > This vote will be open for 5 days. > > For more details about this process please read > http://www.apache.org/foundation/voting.html > > You can download and test the zip file and its signature and hashes (for > instructions on testing the signature see > http://www.apache.org/info/verification.html). > > Kind Regards, > > Jacopo
Re: svn commit: r1765058 - in /ofbiz/trunk/framework/widget: dtd/ src/main/java/org/apache/ofbiz/widget/model/ src/main/java/org/apache/ofbiz/widget/renderer/ src/main/java/org/apache/ofbiz/widget/ren
Hi Nicolas,
Thanks for your input. I’ll work on a better approach to implement this feature.
--
Thanks & Regards,
Mridul Pathak
> On Oct 18, 2016, at 5:31 PM, Nicolas Malin wrote:
>
> Hi Mridul,
>
> I like the idea on this commit but I see two problems.
>
> * The modification on ModelForm break the threadsafe set by adrian. If I
> understand what he did, the boolean hideHeader should be rest final, and you
> don't update the ModelForm during the treatment. To improve it, insteade of
> *if (!modelForm.getHideHeader()) {* use more *if (!modelForm.getHideHeader()
> && !elementOnList) {* . After this isn't a good solution to use
> getHideHeader() to display the message "no element found" because if I create
> a form without header to display and only the list, :) I'm going to blame you
> !
>
> * The message isn't call a flexibleStringExpander so you can't use
> translation and the default label need to use a common label.
>
> Nicolas
>
> Le 15/10/2016 à 15:19, mridulpat...@apache.org a écrit :
>> Author: mridulpathak
>> Date: Sat Oct 15 13:19:35 2016
>> New Revision: 1765058
>>
>> URL: http://svn.apache.org/viewvc?rev=1765058&view=rev
>> Log:
>> Improved: In form widgets of list type empty header row should not render if
>> list to render in file is empty.
>> (OFBIZ-7598)
>>
>> Thanks: Suraj Khurana for contribution.
>>
>> Modified:
>> ofbiz/trunk/framework/widget/dtd/widget-form.xsd
>>
>> ofbiz/trunk/framework/widget/src/main/java/org/apache/ofbiz/widget/model/ModelForm.java
>>
>> ofbiz/trunk/framework/widget/src/main/java/org/apache/ofbiz/widget/renderer/FormRenderer.java
>>
>> ofbiz/trunk/framework/widget/src/main/java/org/apache/ofbiz/widget/renderer/FormStringRenderer.java
>>
>> ofbiz/trunk/framework/widget/src/main/java/org/apache/ofbiz/widget/renderer/macro/MacroFormRenderer.java
>> ofbiz/trunk/framework/widget/templates/HtmlFormMacroLibrary.ftl
>>
>> Modified: ofbiz/trunk/framework/widget/dtd/widget-form.xsd
>> URL:
>> http://svn.apache.org/viewvc/ofbiz/trunk/framework/widget/dtd/widget-form.xsd?rev=1765058&r1=1765057&r2=1765058&view=diff
>> ==
>> --- ofbiz/trunk/framework/widget/dtd/widget-form.xsd (original)
>> +++ ofbiz/trunk/framework/widget/dtd/widget-form.xsd Sat Oct 15 13:19:35 2016
>> @@ -86,6 +86,7 @@ under the License.
>>
>>
>>
>> +
>>
>>
>>
>> @@ -327,6 +328,7 @@ under the License.
>>
>>
>>
>> +
>>
>>
>>
>>
>> Modified:
>> ofbiz/trunk/framework/widget/src/main/java/org/apache/ofbiz/widget/model/ModelForm.java
>> URL:
>> http://svn.apache.org/viewvc/ofbiz/trunk/framework/widget/src/main/java/org/apache/ofbiz/widget/model/ModelForm.java?rev=1765058&r1=1765057&r2=1765058&view=diff
>> ==
>> ---
>> ofbiz/trunk/framework/widget/src/main/java/org/apache/ofbiz/widget/model/ModelForm.java
>> (original)
>> +++
>> ofbiz/trunk/framework/widget/src/main/java/org/apache/ofbiz/widget/model/ModelForm.java
>> Sat Oct 15 13:19:35 2016
>> @@ -147,7 +147,7 @@ public abstract class ModelForm extends
>> private final String formWidgetAreaStyle;
>> private final boolean groupColumns;
>> private final String headerRowStyle;
>> -private final boolean hideHeader;
>> +private boolean hideHeader;
>> private final String itemIndexSeparator;
>> private final List lastOrderFields;
>> private final String listEntryName;
>> @@ -184,6 +184,7 @@ public abstract class ModelForm extends
>> private final String targetType;
>> private final FlexibleStringExpander targetWindowExdr;
>> private final String title;
>> +private final String emptyFormDataMessage;
>> private final String tooltip;
>> private final String type;
>> private final boolean useRowSubmit;
>> @@ -241,6 +242,13 @@ public abstract class ModelForm extends
>> title = parentModel.title;
>> }
>> this.title = title;
>> +String emptyFormDataMessage =
>> formElement.getAttribute("empty-form-data-message");
>> +
Re: svn commit: r1765058 - in /ofbiz/trunk/framework/widget: dtd/ src/main/java/org/apache/ofbiz/widget/model/ src/main/java/org/apache/ofbiz/widget/renderer/ src/main/java/org/apache/ofbiz/widget/ren
Hi Jacques, I’ll do some tests and see if it could be fixed quickly, else revert it for now. -- Thanks & Regards, Mridul Pathak > On Oct 17, 2016, at 6:43 PM, Jacques Le Roux > wrote: > > Hi Mridul, > > After Arun fixed a compilation issue at r1765080, I found that this > introduced a regression. Please see > https://issues.apache.org/jira/browse/OFBIZ-8505 > > I think it's better to revert and test this more. > > Thanks > > Jacques > > > Le 15/10/2016 à 16:25, Jacques Le Roux a écrit : >> Hi Mridul, >> >> Did you notice we have a compilation issue with this commit? >> >> https://ci.apache.org/builders/ofbiz-trunk >> >> https://ci.apache.org/builders/ofbiz-trunk/builds/1607/steps/shell/logs/stdio >> >> Thanks >> >> Jacques >> >> >> Le 15/10/2016 à 15:19, mridulpat...@apache.org a écrit : >>> Author: mridulpathak >>> Date: Sat Oct 15 13:19:35 2016 >>> New Revision: 1765058 >>> >>> URL: http://svn.apache.org/viewvc?rev=1765058&view=rev >>> Log: >>> Improved: In form widgets of list type empty header row should not render >>> if list to render in file is empty. >>> (OFBIZ-7598) >>> >>> Thanks: Suraj Khurana for contribution. >>> >>> Modified: >>> ofbiz/trunk/framework/widget/dtd/widget-form.xsd >>> ofbiz/trunk/framework/widget/src/main/java/org/apache/ofbiz/widget/model/ModelForm.java >>> ofbiz/trunk/framework/widget/src/main/java/org/apache/ofbiz/widget/renderer/FormRenderer.java >>> ofbiz/trunk/framework/widget/src/main/java/org/apache/ofbiz/widget/renderer/FormStringRenderer.java >>> ofbiz/trunk/framework/widget/src/main/java/org/apache/ofbiz/widget/renderer/macro/MacroFormRenderer.java >>> ofbiz/trunk/framework/widget/templates/HtmlFormMacroLibrary.ftl >>> >>> Modified: ofbiz/trunk/framework/widget/dtd/widget-form.xsd >>> URL: >>> http://svn.apache.org/viewvc/ofbiz/trunk/framework/widget/dtd/widget-form.xsd?rev=1765058&r1=1765057&r2=1765058&view=diff >>> == >>> --- ofbiz/trunk/framework/widget/dtd/widget-form.xsd (original) >>> +++ ofbiz/trunk/framework/widget/dtd/widget-form.xsd Sat Oct 15 13:19:35 >>> 2016 >>> @@ -86,6 +86,7 @@ under the License. >>> >>> >>> >>> +>> /> >>> >>> >>> >>> @@ -327,6 +328,7 @@ under the License. >>> >>> >>> >>> +>> /> >>> >>> >>> >>> >>> Modified: >>> ofbiz/trunk/framework/widget/src/main/java/org/apache/ofbiz/widget/model/ModelForm.java >>> URL: >>> http://svn.apache.org/viewvc/ofbiz/trunk/framework/widget/src/main/java/org/apache/ofbiz/widget/model/ModelForm.java?rev=1765058&r1=1765057&r2=1765058&view=diff >>> == >>> --- >>> ofbiz/trunk/framework/widget/src/main/java/org/apache/ofbiz/widget/model/ModelForm.java >>> (original) >>> +++ >>> ofbiz/trunk/framework/widget/src/main/java/org/apache/ofbiz/widget/model/ModelForm.java >>> Sat Oct 15 13:19:35 2016 >>> @@ -147,7 +147,7 @@ public abstract class ModelForm extends >>> private final String formWidgetAreaStyle; >>> private final boolean groupColumns; >>> private final String headerRowStyle; >>> -private final boolean hideHeader; >>> +private boolean hideHeader; >>> private final String itemIndexSeparator; >>> private final List lastOrderFields; >>> private final String listEntryName; >>> @@ -184,6 +184,7 @@ public abstract class ModelForm extends >>> private final String targetType; >>> private final FlexibleStringExpander targetWindowExdr; >>> private final String title; >>> +private final String emptyFormDataMessage; >>> private final String tooltip; >>> private final String type; >>> private final boolean useRowSubmit; >>> @@ -241,6 +242,13 @@ public abstract class ModelForm extends >>> title = parentModel.title; >>> } >>> this.title = title; >>> +Stri
Re: Offer of Snoot Analytic Services for OFBiz
+1 -- Thanks & Regards, Mridul Pathak HotWax Systems http://www.hotwaxsystems.com > On Aug 23, 2016, at 3:04 PM, Sharan Foga wrote: > > Hi Everyone > > The ASF is offering all projects the opportunity to get for analytic > services. (from Snoot). > I'm not sure if you have seen the ASF Snoot 'Did you know' factoids that have > been appearing on Twitter (https://twitter.com/snoot_io) but our project has > been highlighted recently here: > > https://twitter.com/snoot_io/status/767063202123354112 > > https://twitter.com/snoot_io/status/767059661103194112 > > Only 10 ASF projects are being on-boarded per month on a > first-come-first-served basis and as expected it has already been quite > popular (the the first 10 places already being allocated within hours of the > offer being made!) > > A waiting list of projects wanting these analytics has been started so I'd > like to get some feedback to find out if the community would like me to ask > for OFBiz to be added the waitlist. > > Thanks > Sharan
Re: system property not define
Hi Taher, Yes, I was talking about splitting those and implement as it’s own method rather than using the common approach for both. -- Thanks & Regards, Mridul Pathak http://www.hotwaxsystems.com > On Aug 12, 2016, at 7:49 PM, Taher Alkhateeb > wrote: > > Hi Mridul, > > I'm assuming you want to split the methods, not copy-paste into a new file > right? If yes then yeah I think It's a good idea. > > Taher Alkhateeb > > On Thu, Aug 11, 2016 at 5:37 PM, Mridul Pathak > mailto:mridul.pat...@hotwaxsystems.com>> > wrote: > The other area that I believe needs be fixed is the use of UtilProperties for > both configurations and UI Labels. UI Labels used to be in properties files > way back and at that time when migrating to XML format it made sense to keep > using the same methods for properties and UI Labels to minimize the effort. I > think handling of configurations versus UI Labels can be redesigned to be > distinct functionalities. > > -- > Thanks & Regards, > Mridul Pathak > Senior Manager > HotWax Systems > http://www.hotwaxsystems.com <http://www.hotwaxsystems.com/> > > > On Aug 8, 2016, at 10:56 PM, Taher Alkhateeb > <mailto:slidingfilame...@gmail.com>> wrote: > > > > However as far as configuration files are concerned, I find the whole > > approach currently used in OFBiz a bit confusing and problematic. There are > > too many files scattered in too many places. Some of them are XML and some > > are .properties. we should really have one or a few files preferrably in > > one directory for all configurations related to framework and core > > applications. Or maybe just one master configuration file for framework and > > another one for applications and that's it. Also many configurations should > > be code and vice versa. All of this makes tweking OFBiz confusing and > > difficult. > > > > So my real preference is to shake things up, redesign and centralize > > configurations for OFBiz. For example if you think of apache httpd, then > > it's really one or two major files isn't it? It should be similar with us I > > think. > >
Re: system property not define
The other area that I believe needs be fixed is the use of UtilProperties for both configurations and UI Labels. UI Labels used to be in properties files way back and at that time when migrating to XML format it made sense to keep using the same methods for properties and UI Labels to minimize the effort. I think handling of configurations versus UI Labels can be redesigned to be distinct functionalities. -- Thanks & Regards, Mridul Pathak Senior Manager HotWax Systems http://www.hotwaxsystems.com > On Aug 8, 2016, at 10:56 PM, Taher Alkhateeb > wrote: > > However as far as configuration files are concerned, I find the whole > approach currently used in OFBiz a bit confusing and problematic. There are > too many files scattered in too many places. Some of them are XML and some > are .properties. we should really have one or a few files preferrably in > one directory for all configurations related to framework and core > applications. Or maybe just one master configuration file for framework and > another one for applications and that's it. Also many configurations should > be code and vice versa. All of this makes tweking OFBiz confusing and > difficult. > > So my real preference is to shake things up, redesign and centralize > configurations for OFBiz. For example if you think of apache httpd, then > it's really one or two major files isn't it? It should be similar with us I > think.
[jira] [Closed] (OFBIZ-7821) Remove unused system generated fields from all data files
[ https://issues.apache.org/jira/browse/OFBIZ-7821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak closed OFBIZ-7821. Closing this parent ticket as all the sub tasks are now closed. > Remove unused system generated fields from all data files > - > > Key: OFBIZ-7821 > URL: https://issues.apache.org/jira/browse/OFBIZ-7821 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Suraj Khurana > Assignee: Mridul Pathak >Priority: Minor > Fix For: Upcoming Branch > > > There are four system generated fields for every entity as lastUpdatedStamp, > lastUpdatedTxStamp, createdStamp and createdTxStamp > To increase readability of data files, these fields are not necessary to be > there in data files, as it gets generated every time when data load occurs. > This ticket will be served as a parent ticket and I will be creating child > tickets component wise for all affected components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-7821) Remove unused system generated fields from all data files
[ https://issues.apache.org/jira/browse/OFBIZ-7821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak reassigned OFBIZ-7821: Assignee: Mridul Pathak (was: Nicolas Malin) > Remove unused system generated fields from all data files > - > > Key: OFBIZ-7821 > URL: https://issues.apache.org/jira/browse/OFBIZ-7821 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Suraj Khurana > Assignee: Mridul Pathak >Priority: Minor > Fix For: Upcoming Branch > > > There are four system generated fields for every entity as lastUpdatedStamp, > lastUpdatedTxStamp, createdStamp and createdTxStamp > To increase readability of data files, these fields are not necessary to be > there in data files, as it gets generated every time when data load occurs. > This ticket will be served as a parent ticket and I will be creating child > tickets component wise for all affected components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OFBIZ-7821) Remove unused system generated fields from all data files
[ https://issues.apache.org/jira/browse/OFBIZ-7821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak resolved OFBIZ-7821. -- Resolution: Fixed Fix Version/s: Upcoming Branch > Remove unused system generated fields from all data files > - > > Key: OFBIZ-7821 > URL: https://issues.apache.org/jira/browse/OFBIZ-7821 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Suraj Khurana > Assignee: Mridul Pathak >Priority: Minor > Fix For: Upcoming Branch > > > There are four system generated fields for every entity as lastUpdatedStamp, > lastUpdatedTxStamp, createdStamp and createdTxStamp > To increase readability of data files, these fields are not necessary to be > there in data files, as it gets generated every time when data load occurs. > This ticket will be served as a parent ticket and I will be creating child > tickets component wise for all affected components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7901) Remove system generated fields - Content
[ https://issues.apache.org/jira/browse/OFBIZ-7901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak closed OFBIZ-7901. > Remove system generated fields - Content > > > Key: OFBIZ-7901 > URL: https://issues.apache.org/jira/browse/OFBIZ-7901 > Project: OFBiz > Issue Type: Sub-task > Components: content >Affects Versions: Trunk >Reporter: Suraj Khurana > Assignee: Mridul Pathak >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-7901.patch > > > Remove all system generated fields from content component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7903) Remove system generated fields - Marketing
[ https://issues.apache.org/jira/browse/OFBIZ-7903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak closed OFBIZ-7903. > Remove system generated fields - Marketing > -- > > Key: OFBIZ-7903 > URL: https://issues.apache.org/jira/browse/OFBIZ-7903 > Project: OFBiz > Issue Type: Sub-task > Components: marketing >Affects Versions: Trunk >Reporter: Suraj Khurana > Assignee: Mridul Pathak >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-7903.patch > > > Remove all system generated fields from marketing component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7904) Remove system generated fields - Product
[ https://issues.apache.org/jira/browse/OFBIZ-7904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak closed OFBIZ-7904. > Remove system generated fields - Product > > > Key: OFBIZ-7904 > URL: https://issues.apache.org/jira/browse/OFBIZ-7904 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Suraj Khurana > Assignee: Mridul Pathak >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-7904.patch > > > Remove all system generated fields from product component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7909) Remove system generated fields - Accounting
[ https://issues.apache.org/jira/browse/OFBIZ-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak closed OFBIZ-7909. > Remove system generated fields - Accounting > --- > > Key: OFBIZ-7909 > URL: https://issues.apache.org/jira/browse/OFBIZ-7909 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Suraj Khurana > Assignee: Mridul Pathak >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-7909.patch > > > Remove all system generated fields from accounting component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OFBIZ-7909) Remove system generated fields - Accounting
[ https://issues.apache.org/jira/browse/OFBIZ-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak resolved OFBIZ-7909. -- Resolution: Fixed Fix Version/s: Upcoming Branch Thanks [~suraj.khurana] for your contribution. Your patch is in trunk r1755301. > Remove system generated fields - Accounting > --- > > Key: OFBIZ-7909 > URL: https://issues.apache.org/jira/browse/OFBIZ-7909 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Suraj Khurana > Assignee: Mridul Pathak >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-7909.patch > > > Remove all system generated fields from accounting component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-7904) Remove system generated fields - Product
[ https://issues.apache.org/jira/browse/OFBIZ-7904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak reassigned OFBIZ-7904: Assignee: Mridul Pathak (was: Suraj Khurana) > Remove system generated fields - Product > > > Key: OFBIZ-7904 > URL: https://issues.apache.org/jira/browse/OFBIZ-7904 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Trunk >Reporter: Suraj Khurana > Assignee: Mridul Pathak >Priority: Minor > Attachments: OFBIZ-7904.patch > > > Remove all system generated fields from product component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7905) Remove system generated fields - Scrum
[ https://issues.apache.org/jira/browse/OFBIZ-7905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak closed OFBIZ-7905. > Remove system generated fields - Scrum > -- > > Key: OFBIZ-7905 > URL: https://issues.apache.org/jira/browse/OFBIZ-7905 > Project: OFBiz > Issue Type: Sub-task > Components: specialpurpose/scrum >Affects Versions: Trunk >Reporter: Suraj Khurana > Assignee: Mridul Pathak >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-7905.patch > > > Remove all system generated fields from scrum component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7902) Remove system generated fields - Ecommerce
[ https://issues.apache.org/jira/browse/OFBIZ-7902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak closed OFBIZ-7902. > Remove system generated fields - Ecommerce > -- > > Key: OFBIZ-7902 > URL: https://issues.apache.org/jira/browse/OFBIZ-7902 > Project: OFBiz > Issue Type: Sub-task > Components: specialpurpose/ecommerce >Affects Versions: Trunk >Reporter: Suraj Khurana > Assignee: Mridul Pathak >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-7902.patch > > > Remove all system generated fields from ecommerce component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-7909) Remove system generated fields - Accounting
[ https://issues.apache.org/jira/browse/OFBIZ-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak reassigned OFBIZ-7909: Assignee: Mridul Pathak (was: Suraj Khurana) > Remove system generated fields - Accounting > --- > > Key: OFBIZ-7909 > URL: https://issues.apache.org/jira/browse/OFBIZ-7909 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Suraj Khurana > Assignee: Mridul Pathak >Priority: Minor > Attachments: OFBIZ-7909.patch > > > Remove all system generated fields from accounting component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OFBIZ-7902) Remove system generated fields - Ecommerce
[ https://issues.apache.org/jira/browse/OFBIZ-7902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak resolved OFBIZ-7902. -- Resolution: Fixed Fix Version/s: Upcoming Branch Thanks [~suraj.khurana] for your contribution. Your patch is in trunk r1755304. > Remove system generated fields - Ecommerce > -- > > Key: OFBIZ-7902 > URL: https://issues.apache.org/jira/browse/OFBIZ-7902 > Project: OFBiz > Issue Type: Sub-task > Components: specialpurpose/ecommerce >Affects Versions: Trunk >Reporter: Suraj Khurana > Assignee: Mridul Pathak >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-7902.patch > > > Remove all system generated fields from ecommerce component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-7902) Remove system generated fields - Ecommerce
[ https://issues.apache.org/jira/browse/OFBIZ-7902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak reassigned OFBIZ-7902: Assignee: Mridul Pathak (was: Suraj Khurana) > Remove system generated fields - Ecommerce > -- > > Key: OFBIZ-7902 > URL: https://issues.apache.org/jira/browse/OFBIZ-7902 > Project: OFBiz > Issue Type: Sub-task > Components: specialpurpose/ecommerce >Affects Versions: Trunk >Reporter: Suraj Khurana > Assignee: Mridul Pathak >Priority: Minor > Attachments: OFBIZ-7902.patch > > > Remove all system generated fields from ecommerce component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-7905) Remove system generated fields - Scrum
[ https://issues.apache.org/jira/browse/OFBIZ-7905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak reassigned OFBIZ-7905: Assignee: Mridul Pathak (was: Suraj Khurana) > Remove system generated fields - Scrum > -- > > Key: OFBIZ-7905 > URL: https://issues.apache.org/jira/browse/OFBIZ-7905 > Project: OFBiz > Issue Type: Sub-task > Components: specialpurpose/scrum >Affects Versions: Trunk >Reporter: Suraj Khurana > Assignee: Mridul Pathak >Priority: Minor > Attachments: OFBIZ-7905.patch > > > Remove all system generated fields from scrum component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-7903) Remove system generated fields - Marketing
[ https://issues.apache.org/jira/browse/OFBIZ-7903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak reassigned OFBIZ-7903: Assignee: Mridul Pathak (was: Suraj Khurana) > Remove system generated fields - Marketing > -- > > Key: OFBIZ-7903 > URL: https://issues.apache.org/jira/browse/OFBIZ-7903 > Project: OFBiz > Issue Type: Sub-task > Components: marketing >Affects Versions: Trunk >Reporter: Suraj Khurana > Assignee: Mridul Pathak >Priority: Minor > Attachments: OFBIZ-7903.patch > > > Remove all system generated fields from marketing component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-7901) Remove system generated fields - Content
[ https://issues.apache.org/jira/browse/OFBIZ-7901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak reassigned OFBIZ-7901: Assignee: Mridul Pathak (was: Suraj Khurana) > Remove system generated fields - Content > > > Key: OFBIZ-7901 > URL: https://issues.apache.org/jira/browse/OFBIZ-7901 > Project: OFBiz > Issue Type: Sub-task > Components: content >Affects Versions: Trunk >Reporter: Suraj Khurana > Assignee: Mridul Pathak >Priority: Minor > Attachments: OFBIZ-7901.patch > > > Remove all system generated fields from content component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7415) Move 3rd party payment integrations from accounting application to sepcialpurpose
[ https://issues.apache.org/jira/browse/OFBIZ-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401258#comment-15401258 ] Mridul Pathak commented on OFBIZ-7415: -- That makes sense. Let's wait for Pierre's input, if he has something of this sort ready that can be contributed to OFBiz, we could use it as a base for payment and shipping integration plugins. Although, the nature and protocol of shipping integrations is different from that of payment integrations. So, I am not sure if one common framework solution would apply to both. > Move 3rd party payment integrations from accounting application to > sepcialpurpose > - > > Key: OFBIZ-7415 > URL: https://issues.apache.org/jira/browse/OFBIZ-7415 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk > Reporter: Pierre Smits >Assignee: Mridul Pathak > > This is a placeholder issue to capture all sub tasks for removing 3rd party > payment integrations from accounting application and moving to a new > component in special purpose. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7415) Move 3rd party payment integrations from accounting application to sepcialpurpose
[ https://issues.apache.org/jira/browse/OFBIZ-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401185#comment-15401185 ] Mridul Pathak commented on OFBIZ-7415: -- Hi [~jacques.le.roux], I agree. My only concern is to not spread the similar kind of code too much in many components until we have a concrete solution around a payment integration framework. Also, to not get blocked at least to remove it from applications. We can ask for community opinion - one component or multiple components, the topic on this thread seems to be dead. What course of action do you suggest? > Move 3rd party payment integrations from accounting application to > sepcialpurpose > - > > Key: OFBIZ-7415 > URL: https://issues.apache.org/jira/browse/OFBIZ-7415 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Mridul Pathak > > This is a placeholder issue to capture all sub tasks for removing 3rd party > payment integrations from accounting application and moving to a new > component in special purpose. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7529) Delete stale java files from applications and framework
[ https://issues.apache.org/jira/browse/OFBIZ-7529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401080#comment-15401080 ] Mridul Pathak commented on OFBIZ-7529: -- Hi [~taher], Please attach it in OFBIZ-7415, it'll be utilized there. > Delete stale java files from applications and framework > --- > > Key: OFBIZ-7529 > URL: https://issues.apache.org/jira/browse/OFBIZ-7529 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Mridul Pathak >Assignee: Mridul Pathak > > As per the discussions on the thread - > http://ofbiz.135035.n4.nabble.com/Proposal-to-delete-stale-java-files-tt4683855.html, > following files and their references needs to be deleted from applications > and framework, > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeByteArrayInputStream.java > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeByteArrayOutputStream.java > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeServices.java > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeWorker.java > applications/content/src/org/ofbiz/content/report > applications/content/src/org/ofbiz/content/report/JREntityListIteratorDataSource.java > applications/content/src/org/ofbiz/content/report/JRMapCollectionDataSource.java > applications/product/src/ShipmentScaleApplet.java > applications/securityext/src/org/ofbiz/securityext/thirdparty/truition/TruitionCoReg.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsJXlsViewHandler.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsPdfViewHandler.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsPoiXlsViewHandler.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsXmlViewHandler.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-7529) Delete stale java files from applications and framework
[ https://issues.apache.org/jira/browse/OFBIZ-7529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401077#comment-15401077 ] Mridul Pathak edited comment on OFBIZ-7529 at 7/31/16 9:53 AM: --- All the files mentioned in the description are now deleted along with all their references in trunk r1754634, r1754635, r1754636, r1754637, r1754644, r1754645. Will keep this issue open for next couple days if anything is found or reported in context of this change. In the mean time I'll add these to attic before closing. was (Author: mridul.pathak): All the files mentioned in the description are now deleted along with all their references in trunk r1754634, r1754635, r1754636, r1754637, r1754644, r1754645. Will keep this issue open for next couple days if anything is found or reported in context of this change. > Delete stale java files from applications and framework > --- > > Key: OFBIZ-7529 > URL: https://issues.apache.org/jira/browse/OFBIZ-7529 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Mridul Pathak >Assignee: Mridul Pathak > > As per the discussions on the thread - > http://ofbiz.135035.n4.nabble.com/Proposal-to-delete-stale-java-files-tt4683855.html, > following files and their references needs to be deleted from applications > and framework, > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeByteArrayInputStream.java > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeByteArrayOutputStream.java > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeServices.java > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeWorker.java > applications/content/src/org/ofbiz/content/report > applications/content/src/org/ofbiz/content/report/JREntityListIteratorDataSource.java > applications/content/src/org/ofbiz/content/report/JRMapCollectionDataSource.java > applications/product/src/ShipmentScaleApplet.java > applications/securityext/src/org/ofbiz/securityext/thirdparty/truition/TruitionCoReg.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsJXlsViewHandler.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsPdfViewHandler.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsPoiXlsViewHandler.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsXmlViewHandler.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7529) Delete stale java files from applications and framework
[ https://issues.apache.org/jira/browse/OFBIZ-7529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401077#comment-15401077 ] Mridul Pathak commented on OFBIZ-7529: -- All the files mentioned in the description are now deleted along with all their references in trunk r1754634, r1754635, r1754636, r1754637, r1754644, r1754645. Will keep this issue open for next couple days if anything is found or reported in context of this change. > Delete stale java files from applications and framework > --- > > Key: OFBIZ-7529 > URL: https://issues.apache.org/jira/browse/OFBIZ-7529 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk > Reporter: Mridul Pathak >Assignee: Mridul Pathak > > As per the discussions on the thread - > http://ofbiz.135035.n4.nabble.com/Proposal-to-delete-stale-java-files-tt4683855.html, > following files and their references needs to be deleted from applications > and framework, > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeByteArrayInputStream.java > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeByteArrayOutputStream.java > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeServices.java > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeWorker.java > applications/content/src/org/ofbiz/content/report > applications/content/src/org/ofbiz/content/report/JREntityListIteratorDataSource.java > applications/content/src/org/ofbiz/content/report/JRMapCollectionDataSource.java > applications/product/src/ShipmentScaleApplet.java > applications/securityext/src/org/ofbiz/securityext/thirdparty/truition/TruitionCoReg.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsJXlsViewHandler.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsPdfViewHandler.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsPoiXlsViewHandler.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsXmlViewHandler.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7529) Delete stale java files from applications and framework
[ https://issues.apache.org/jira/browse/OFBIZ-7529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400573#comment-15400573 ] Mridul Pathak commented on OFBIZ-7529: -- Hi [~taher], I believe that would apply to only those files which we move to special purpose which would be handled in OFBIZ-7415, OFBIZ-7935 and OFBIZ-7936. In this ticket we will be taking care of those files which needs to be deleted permanently. I would look forward to your reference patch. > Delete stale java files from applications and framework > --- > > Key: OFBIZ-7529 > URL: https://issues.apache.org/jira/browse/OFBIZ-7529 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk > Reporter: Mridul Pathak >Assignee: Mridul Pathak > > As per the discussions on the thread - > http://ofbiz.135035.n4.nabble.com/Proposal-to-delete-stale-java-files-tt4683855.html, > following files and their references needs to be deleted from applications > and framework, > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeByteArrayInputStream.java > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeByteArrayOutputStream.java > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeServices.java > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeWorker.java > applications/content/src/org/ofbiz/content/report > applications/content/src/org/ofbiz/content/report/JREntityListIteratorDataSource.java > applications/content/src/org/ofbiz/content/report/JRMapCollectionDataSource.java > applications/product/src/ShipmentScaleApplet.java > applications/securityext/src/org/ofbiz/securityext/thirdparty/truition/TruitionCoReg.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsJXlsViewHandler.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsPdfViewHandler.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsPoiXlsViewHandler.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsXmlViewHandler.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OFBIZ-7442) Error in adding Party tax authority
[ https://issues.apache.org/jira/browse/OFBIZ-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak resolved OFBIZ-7442. -- Resolution: Fixed Fix Version/s: Release Branch 13.07 Release Branch 14.12 Release Branch 15.12 Thanks [~arvind.singh], you patch with some corrections is in trunk r1754591, 15.12 r1754592, 14.12 r1754593, 13.07 r1754594. Thanks [~padma.rawat] for reporting the issue and [~pfm.smits] for your input. > Error in adding Party tax authority > --- > > Key: OFBIZ-7442 > URL: https://issues.apache.org/jira/browse/OFBIZ-7442 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 >Reporter: Padmavati Rawat >Assignee: Mridul Pathak > Fix For: Release Branch 15.12, Release Branch 14.12, Release > Branch 13.07 > > Attachments: OFBIZ-7442_trunk.patch, Tax_Authority_Party.png > > > Steps: > 1) Navigate to Party page. > 2) Search for parties, select Company Party ID. > 3) Navigate on Tax Infos tab to, Add Party Tax Authority Info. > 4) Add detail of "Tax Authority Party" and click on Create button. > Expected : > Tax Authority Party should add successfully. > Actual: > Showing error while adding Tax Authority Party. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7442) Error in adding Party tax authority
[ https://issues.apache.org/jira/browse/OFBIZ-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak closed OFBIZ-7442. > Error in adding Party tax authority > --- > > Key: OFBIZ-7442 > URL: https://issues.apache.org/jira/browse/OFBIZ-7442 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 >Reporter: Padmavati Rawat >Assignee: Mridul Pathak > Fix For: Release Branch 13.07, Release Branch 14.12, Release > Branch 15.12 > > Attachments: OFBIZ-7442_trunk.patch, Tax_Authority_Party.png > > > Steps: > 1) Navigate to Party page. > 2) Search for parties, select Company Party ID. > 3) Navigate on Tax Infos tab to, Add Party Tax Authority Info. > 4) Add detail of "Tax Authority Party" and click on Create button. > Expected : > Tax Authority Party should add successfully. > Actual: > Showing error while adding Tax Authority Party. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7529) Delete stale java files from applications and framework
[ https://issues.apache.org/jira/browse/OFBIZ-7529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400562#comment-15400562 ] Mridul Pathak commented on OFBIZ-7529: -- Thanks Jacques. > Delete stale java files from applications and framework > --- > > Key: OFBIZ-7529 > URL: https://issues.apache.org/jira/browse/OFBIZ-7529 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk > Reporter: Mridul Pathak >Assignee: Mridul Pathak > > As per the discussions on the thread - > http://ofbiz.135035.n4.nabble.com/Proposal-to-delete-stale-java-files-tt4683855.html, > following files and their references needs to be deleted from applications > and framework, > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeByteArrayInputStream.java > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeByteArrayOutputStream.java > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeServices.java > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeWorker.java > applications/content/src/org/ofbiz/content/report > applications/content/src/org/ofbiz/content/report/JREntityListIteratorDataSource.java > applications/content/src/org/ofbiz/content/report/JRMapCollectionDataSource.java > applications/product/src/ShipmentScaleApplet.java > applications/securityext/src/org/ofbiz/securityext/thirdparty/truition/TruitionCoReg.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsJXlsViewHandler.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsPdfViewHandler.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsPoiXlsViewHandler.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsXmlViewHandler.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7529) Delete stale java files from applications and framework
[ https://issues.apache.org/jira/browse/OFBIZ-7529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400561#comment-15400561 ] Mridul Pathak commented on OFBIZ-7529: -- Hi [~jacques.le.roux], I think we should still delete all these files for the cleanup purpose since they are already excluded in build.gradle. Once delete we could remove the exclude part in build.gradle. > Delete stale java files from applications and framework > --- > > Key: OFBIZ-7529 > URL: https://issues.apache.org/jira/browse/OFBIZ-7529 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk > Reporter: Mridul Pathak >Assignee: Mridul Pathak > > As per the discussions on the thread - > http://ofbiz.135035.n4.nabble.com/Proposal-to-delete-stale-java-files-tt4683855.html, > following files and their references needs to be deleted from applications > and framework, > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeByteArrayInputStream.java > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeByteArrayOutputStream.java > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeServices.java > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeWorker.java > applications/content/src/org/ofbiz/content/report > applications/content/src/org/ofbiz/content/report/JREntityListIteratorDataSource.java > applications/content/src/org/ofbiz/content/report/JRMapCollectionDataSource.java > applications/product/src/ShipmentScaleApplet.java > applications/securityext/src/org/ofbiz/securityext/thirdparty/truition/TruitionCoReg.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsJXlsViewHandler.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsPdfViewHandler.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsPoiXlsViewHandler.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsXmlViewHandler.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7297) Migrate promotext.properties to UiLabels
[ https://issues.apache.org/jira/browse/OFBIZ-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak closed OFBIZ-7297. > Migrate promotext.properties to UiLabels > > > Key: OFBIZ-7297 > URL: https://issues.apache.org/jira/browse/OFBIZ-7297 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk > Reporter: Mridul Pathak > Assignee: Mridul Pathak >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-7297-2.patch, OFBIZ-7297.patch > > > promotext.properties file is used only in > ProductPromoWorker.makeAutoDescription() method and was implemented way back > when UI Labels were managed in *.properties files. It should be moved to > UiLabels file because all the properties defined in the file are text > descriptions and not system configurations, which makes them a candidate of > internationalization. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7529) Delete stale java files from applications and framework
[ https://issues.apache.org/jira/browse/OFBIZ-7529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400514#comment-15400514 ] Mridul Pathak commented on OFBIZ-7529: -- I think it can be deleted now as POS is in attic. I can take care of that under this task. > Delete stale java files from applications and framework > --- > > Key: OFBIZ-7529 > URL: https://issues.apache.org/jira/browse/OFBIZ-7529 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk > Reporter: Mridul Pathak >Assignee: Mridul Pathak > > As per the discussions on the thread - > http://ofbiz.135035.n4.nabble.com/Proposal-to-delete-stale-java-files-tt4683855.html, > following files and their references needs to be deleted from applications > and framework, > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeByteArrayInputStream.java > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeByteArrayOutputStream.java > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeServices.java > applications/content/src/org/ofbiz/content/openoffice/OpenOfficeWorker.java > applications/content/src/org/ofbiz/content/report > applications/content/src/org/ofbiz/content/report/JREntityListIteratorDataSource.java > applications/content/src/org/ofbiz/content/report/JRMapCollectionDataSource.java > applications/product/src/ShipmentScaleApplet.java > applications/securityext/src/org/ofbiz/securityext/thirdparty/truition/TruitionCoReg.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsJXlsViewHandler.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsPdfViewHandler.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsPoiXlsViewHandler.java > framework/webapp/src/org/ofbiz/webapp/view/JasperReportsXmlViewHandler.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7442) Error in adding Party tax authority
[ https://issues.apache.org/jira/browse/OFBIZ-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak updated OFBIZ-7442: - Affects Version/s: Release Branch 13.07 Release Branch 14.12 Release Branch 15.12 > Error in adding Party tax authority > --- > > Key: OFBIZ-7442 > URL: https://issues.apache.org/jira/browse/OFBIZ-7442 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 >Reporter: Padmavati Rawat >Assignee: Mridul Pathak > Attachments: OFBIZ-7442_trunk.patch, Tax_Authority_Party.png > > > Steps: > 1) Navigate to Party page. > 2) Search for parties, select Company Party ID. > 3) Navigate on Tax Infos tab to, Add Party Tax Authority Info. > 4) Add detail of "Tax Authority Party" and click on Create button. > Expected : > Tax Authority Party should add successfully. > Actual: > Showing error while adding Tax Authority Party. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-7442) Error in adding Party tax authority
[ https://issues.apache.org/jira/browse/OFBIZ-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak reassigned OFBIZ-7442: Assignee: Mridul Pathak (was: Arvind Singh Tomar) > Error in adding Party tax authority > --- > > Key: OFBIZ-7442 > URL: https://issues.apache.org/jira/browse/OFBIZ-7442 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 >Reporter: Padmavati Rawat >Assignee: Mridul Pathak > Attachments: OFBIZ-7442_trunk.patch, Tax_Authority_Party.png > > > Steps: > 1) Navigate to Party page. > 2) Search for parties, select Company Party ID. > 3) Navigate on Tax Infos tab to, Add Party Tax Authority Info. > 4) Add detail of "Tax Authority Party" and click on Create button. > Expected : > Tax Authority Party should add successfully. > Actual: > Showing error while adding Tax Authority Party. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Create a "notifications" mailing list
+1 -- Thanks & Regards, Mridul Pathak HotWax Systems http://www.hotwaxsystems.com > On Jul 24, 2016, at 6:29 PM, Jacopo Cappellato > wrote: > > Rationale: Jira notifications are currently sent to the "dev" list, causing > a lot of traffic and sometimes distracting from actual conversations; the > creation of a "notification" email (similar to the "commits" mailing list) > will solve this problem; in the future we may vote to use the > "notification" list to host traffic coming from buildbot etc... thus the > proposal for naming it "notifications" rather than just "issues"; however > this vote is only about traffic from Jira (we will discuss if we want to > extend the usage of this list in the future). > > Please vote, > > +1 > > to create a "notifications" mailing list (i.e. > notificati...@ofbiz.apache.org) and redirect to it all the traffic coming > from Jira notifications. > > Otherwise vote -1 to continue to use the "dev" list for Jira notifications.
Re: Proposal to delete stale java files
Hi Taher, Yes, I think it’s the right time for the movement. Below are the JIRA ticket links for the overall work discussed in this thread. Delete stale java files from applications and framework <https://issues.apache.org/jira/browse/OFBIZ-7529> Move 3rd party payment integrations from accounting application to sepcialpurpose <https://issues.apache.org/jira/browse/OFBIZ-7415> Move 3rd party shipping integrations from product application to sepcialpurpose <https://issues.apache.org/jira/browse/OFBIZ-7935> Move 3rd party tax integrations from order application to sepcialpurpose <https://issues.apache.org/jira/browse/OFBIZ-7936> -- Thanks & Regards, Mridul Pathak Senior Manager HotWax Systems http://www.hotwaxsystems.com > On Jul 27, 2016, at 5:37 PM, Taher Alkhateeb > wrote: > > Hi Mridul, Everyone, > > Now that we have a stable running build, perhaps it's time to move forward > with this discussion? All the excluded java files are listed in the master > build.gradle. If you move them to specialpurpose we can figure out a simple > solution to hide these exclusions away from the master build script and > declare them in the components build.gradle files away from the framework > and applications. > > Do we have an available JIRA? Are you still interested in applying the work? > > Taher Alkhateeb > > On Sun, Jun 19, 2016 at 11:09 PM, Jacques Le Roux < > jacques.le.r...@les7arts.com> wrote: > >> This needs to be carefully reviewed indeed (I did not yet) >> >> Jacques >> >> >> Le 18/06/2016 à 13:00, Pierre Smits a écrit : >> >>> I agree that there are common patterns. And the common patterns should be >>> in the base component, to enable the payment and shipment solution >>> integrations. These integration solutions should be optional when >>> implementing an OFBiz setup. >>> >>> An example please evaluate the MultiSafepay integration component I >>> created. >>> See for a high level description: >>> http://oem.ofbizci.net/oci-2/products/p_omultisafepay. >>> Visit for the code: https://github.com/ORRTIZ/omultisafepay >>> And for the implementation instruction: >>> https://github.com/ORRTIZ/omultisafepay/wiki/How-to-implement >>> >>> This component applies the common patterns, without any new entities to be >>> created, and a minimal adjustment to the e-commerce and the product >>> component. >>> >>> Best regards, >>> >>> Pierre Smits >>> >>> ORRTIZ.COM <http://www.orrtiz.com> >>> OFBiz based solutions & services >>> >>> OFBiz Extensions Marketplace >>> http://oem.ofbizci.net/oci-2/ >>> >>> On Sat, Jun 18, 2016 at 12:08 PM, Mridul Pathak < >>> mridul.pat...@hotwaxsystems.com> wrote: >>> >>> Creating payment/shipping/tax solution specific components would introduce >>>> 17 new components to specialpurpose and that doesn’t seems like a >>>> favorable >>>> approach. >>>> >>>> These integrations usually share a common code pattern and in longer >>>> vision we could possibly implement payment/shipping integration >>>> frameworks >>>> with a lot lesser and cleaner code that makes introducing new payment >>>> processor or shipping solution a lot easier with the help of >>>> configurations >>>> and little code. Most of us seems to be fine with three new components >>>> for >>>> payment processor, tax integration and shipping integration and that >>>> would >>>> leave us room for further refactoring. >>>> >>>> I think many on this thread has already given approval for three new >>>> components so that’s the way we should go. >>>> >>>> -- >>>> Thanks & Regards, >>>> Mridul Pathak >>>> HotWax Systems >>>> http://www.hotwaxsystems.com >>>> >>>> On Jun 17, 2016, at 12:37 PM, Pierre Smits >>>>> >>>> wrote: >>>> >>>>> Hi all, >>>>> >>>>> Moving all 3rd party related integrations solutions from accounting, >>>>> product and order into 1 special purpose component makes is worse to >>>>> maintain. Moving those from accounting into one in special purpose, >>>>> those >>>>> from product into one and those from order into another just shifts the >>>>> problem from the base applications stack to a a
[jira] [Created] (OFBIZ-7936) Move 3rd party tax integrations from order application to sepcialpurpose
Mridul Pathak created OFBIZ-7936: Summary: Move 3rd party tax integrations from order application to sepcialpurpose Key: OFBIZ-7936 URL: https://issues.apache.org/jira/browse/OFBIZ-7936 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Trunk Reporter: Mridul Pathak Assignee: Mridul Pathak This is a placeholder issue to capture all sub tasks for removing 3rd party tax integrations from order application and moving to a new component in special purpose. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7935) Move 3rd party shipping integrations from product application to sepcialpurpose
[ https://issues.apache.org/jira/browse/OFBIZ-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak updated OFBIZ-7935: - Description: This is a placeholder issue to capture all sub tasks for removing 3rd party shipping integrations from product application and moving to a new component in special purpose. > Move 3rd party shipping integrations from product application to > sepcialpurpose > --- > > Key: OFBIZ-7935 > URL: https://issues.apache.org/jira/browse/OFBIZ-7935 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk > Reporter: Mridul Pathak >Assignee: Mridul Pathak > > This is a placeholder issue to capture all sub tasks for removing 3rd party > shipping integrations from product application and moving to a new component > in special purpose. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7415) Move 3rd party payment integrations from accounting application to sepcialpurpose
[ https://issues.apache.org/jira/browse/OFBIZ-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak updated OFBIZ-7415: - Description: This is a placeholder issue to capture all sub tasks for removing 3rd party payment integrations from accounting application and moving to a new component in special purpose. (was: This is a placeholder issue to capture all sub tasks for removing 3rd party payment integrations from accounting application to a new component in special purpose.) > Move 3rd party payment integrations from accounting application to > sepcialpurpose > - > > Key: OFBIZ-7415 > URL: https://issues.apache.org/jira/browse/OFBIZ-7415 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Mridul Pathak > > This is a placeholder issue to capture all sub tasks for removing 3rd party > payment integrations from accounting application and moving to a new > component in special purpose. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7935) Move 3rd party shipping integrations from product application to sepcialpurpose
Mridul Pathak created OFBIZ-7935: Summary: Move 3rd party shipping integrations from product application to sepcialpurpose Key: OFBIZ-7935 URL: https://issues.apache.org/jira/browse/OFBIZ-7935 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: Trunk Reporter: Mridul Pathak Assignee: Mridul Pathak -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7415) Move 3rd party payment integrations from accounting application to sepcialpurpose
[ https://issues.apache.org/jira/browse/OFBIZ-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak updated OFBIZ-7415: - Description: This is a placeholder issue to capture all sub tasks for removing 3rd party payment integrations from accounting application to a new component in special purpose. (was: This is a placeholder issue to capture all sub tasks regarding the disentanglement of 3rd party payment and shipment solutions from base applications into separate components in the special purpose stack to offer adopters more flexibility and decrease development complexity.) > Move 3rd party payment integrations from accounting application to > sepcialpurpose > - > > Key: OFBIZ-7415 > URL: https://issues.apache.org/jira/browse/OFBIZ-7415 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Mridul Pathak > > This is a placeholder issue to capture all sub tasks for removing 3rd party > payment integrations from accounting application to a new component in > special purpose. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7415) Move 3rd party payment integrations from accounting application to sepcialpurpose
[ https://issues.apache.org/jira/browse/OFBIZ-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak updated OFBIZ-7415: - Component/s: (was: product) (was: order) > Move 3rd party payment integrations from accounting application to > sepcialpurpose > - > > Key: OFBIZ-7415 > URL: https://issues.apache.org/jira/browse/OFBIZ-7415 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Mridul Pathak > > This is a placeholder issue to capture all sub tasks regarding the > disentanglement of 3rd party payment and shipment solutions from base > applications into separate components in the special purpose stack to offer > adopters more flexibility and decrease development complexity. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7415) Move 3rd party payment integrations from accounting application to sepcialpurpose
[ https://issues.apache.org/jira/browse/OFBIZ-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak updated OFBIZ-7415: - Summary: Move 3rd party payment integrations from accounting application to sepcialpurpose (was: Disentangle 3rd party solution integrations from base app stack) > Move 3rd party payment integrations from accounting application to > sepcialpurpose > - > > Key: OFBIZ-7415 > URL: https://issues.apache.org/jira/browse/OFBIZ-7415 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Mridul Pathak > > This is a placeholder issue to capture all sub tasks regarding the > disentanglement of 3rd party payment and shipment solutions from base > applications into separate components in the special purpose stack to offer > adopters more flexibility and decrease development complexity. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-7415) Disentangle 3rd party solution integrations from base app stack
[ https://issues.apache.org/jira/browse/OFBIZ-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak reassigned OFBIZ-7415: Assignee: Mridul Pathak > Disentangle 3rd party solution integrations from base app stack > --- > > Key: OFBIZ-7415 > URL: https://issues.apache.org/jira/browse/OFBIZ-7415 > Project: OFBiz > Issue Type: Improvement > Components: accounting, order, product >Affects Versions: Trunk >Reporter: Pierre Smits > Assignee: Mridul Pathak > > This is a placeholder issue to capture all sub tasks regarding the > disentanglement of 3rd party payment and shipment solutions from base > applications into separate components in the special purpose stack to offer > adopters more flexibility and decrease development complexity. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Removing multiple commands and related files for OFBiz server
+1 to the proposal. -- Thanks & Regards, Mridul Pathak Senior Manager HotWax Systems http://www.hotwaxsystems.com > On Jul 21, 2016, at 3:08 PM, Taher Alkhateeb > wrote: > > Hello Everyone, > > This is a proposal to _remove_ the following commands from the OFBiz server > (invoked with ./gradlew "ofbiz --commandHere" > > 1- --both > 2- --pos > 3- --testlist > > Reasons: > - The POS component is a specialpurpose component and should not have code > existing in the start component. Instead logic for starting the POS > component should reside inside the POS component and away from framework > - After lots of investigation I realized the testlist OFBiz command is a > weird command that used to create an ant file that just iterates over the > existing integration test suites and run them one by one, which is slower > vs just running them all. It is deprecated and to my knowledge no one is > using it. I think it used to serve some deprecated cobertura tasks. > > This would imply deleting the following files: > - > framework/start/src/main/java/org/apache/ofbiz/base/start/testlist.properties > - > framework/testtools/src/main/java/org/apache/ofbiz/testtools/TestListContainer.java > - > framework/base/src/main/java/org/apache/ofbiz/base/splash/SplashLoader.java > > and modifying the following files: > - framework/start/src/main/java/org/apache/ofbiz/base/start/Config.java > - > framework/start/src/main/java/org/apache/ofbiz/base/start/StartupCommandUtil.java > - (move it to POS) > framework/base/src/main/java/org/apache/ofbiz/base/splash/SplashScreen.java > > Agreed? > > Regards,
[jira] [Closed] (OFBIZ-7435) Create Custreq from CommEvent shows error on screen
[ https://issues.apache.org/jira/browse/OFBIZ-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak closed OFBIZ-7435. > Create Custreq from CommEvent shows error on screen > --- > > Key: OFBIZ-7435 > URL: https://issues.apache.org/jira/browse/OFBIZ-7435 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Trunk >Reporter: Vishal Chhabria > Assignee: Mridul Pathak > Fix For: Upcoming Branch > > Attachments: OFBIZ-7435.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-7821) Remove unused system generated fields from all data files
[ https://issues.apache.org/jira/browse/OFBIZ-7821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15380766#comment-15380766 ] Mridul Pathak edited comment on OFBIZ-7821 at 7/16/16 2:32 PM: --- I agree with [~jacques.le.roux], data cleanup will only improve existing data in OFBiz and doesn't directly impact or is impacted by conclusion of OFBIZ-7781. was (Author: mridul.pathak): I agree with [~jacques.le.roux], data cleanup will only improve existing data in OFBiz and doesn't directly impact or is impact by conclusion of OFBIZ-7781. > Remove unused system generated fields from all data files > - > > Key: OFBIZ-7821 > URL: https://issues.apache.org/jira/browse/OFBIZ-7821 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Suraj Khurana >Priority: Minor > > There are four system generated fields for every entity as lastUpdatedStamp, > lastUpdatedTxStamp, createdStamp and createdTxStamp > To increase readability of data files, these fields are not necessary to be > there in data files, as it gets generated every time when data load occurs. > This ticket will be served as a parent ticket and I will be creating child > tickets component wise for all affected components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7700) File Not Found exception in export to ebay
[ https://issues.apache.org/jira/browse/OFBIZ-7700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15380779#comment-15380779 ] Mridul Pathak commented on OFBIZ-7700: -- Sure [~jacques.le.roux], I usually close the issues, I might have missed this one. > File Not Found exception in export to ebay > -- > > Key: OFBIZ-7700 > URL: https://issues.apache.org/jira/browse/OFBIZ-7700 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/ebay >Affects Versions: Trunk >Reporter: Ankit Joshi >Assignee: Mridul Pathak > Fix For: Upcoming Branch > > Attachments: OFBIZ-7700.patch > > > Steps to regenerate - > Navigate to ebay component and perform advanced search in category. > Here is the reference link - > https://ofbiz-vm.apache.org:8443/ebay/control/keywordsearch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7663) FromDate and ThruDate shows empty for WorkEffort Children
[ https://issues.apache.org/jira/browse/OFBIZ-7663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak closed OFBIZ-7663. > FromDate and ThruDate shows empty for WorkEffort Children > -- > > Key: OFBIZ-7663 > URL: https://issues.apache.org/jira/browse/OFBIZ-7663 > Project: OFBiz > Issue Type: Bug > Components: workeffort >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 >Reporter: Ankit Joshi >Assignee: Mridul Pathak >Priority: Minor > Fix For: 14.12.01, 15.12.01, 13.07.04 > > Attachments: OFBIZ-7663.patch > > > Steps to regenerate - > 1) Navigate to workeffort -> workeffort > 2) Go to workeffort Details Page. > 3) Select Children tab and click on Add existing Workeffort Child. > 4)Add workeffort child with FromDate, thruDate and other required details. > 5) Now, again select Children tab to view all associated workeffort children. > 6) Workeffort children listed in tree structure. Select recently created > workeffort child. > Issue - FromDate and thruDate shows empty value when we navigate to child > details page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7821) Remove unused system generated fields from all data files
[ https://issues.apache.org/jira/browse/OFBIZ-7821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15380766#comment-15380766 ] Mridul Pathak commented on OFBIZ-7821: -- I agree with [~jacques.le.roux], data cleanup will only improve existing data in OFBiz and doesn't directly impact or is impact by conclusion of OFBIZ-7781. > Remove unused system generated fields from all data files > - > > Key: OFBIZ-7821 > URL: https://issues.apache.org/jira/browse/OFBIZ-7821 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk >Reporter: Suraj Khurana >Priority: Minor > > There are four system generated fields for every entity as lastUpdatedStamp, > lastUpdatedTxStamp, createdStamp and createdTxStamp > To increase readability of data files, these fields are not necessary to be > there in data files, as it gets generated every time when data load occurs. > This ticket will be served as a parent ticket and I will be creating child > tickets component wise for all affected components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7663) FromDate and ThruDate shows empty for WorkEffort Children
[ https://issues.apache.org/jira/browse/OFBIZ-7663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak updated OFBIZ-7663: - Affects Version/s: Release Branch 15.12 > FromDate and ThruDate shows empty for WorkEffort Children > -- > > Key: OFBIZ-7663 > URL: https://issues.apache.org/jira/browse/OFBIZ-7663 > Project: OFBiz > Issue Type: Bug > Components: workeffort >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 >Reporter: Ankit Joshi >Assignee: Mridul Pathak >Priority: Minor > Attachments: OFBIZ-7663.patch > > > Steps to regenerate - > 1) Navigate to workeffort -> workeffort > 2) Go to workeffort Details Page. > 3) Select Children tab and click on Add existing Workeffort Child. > 4)Add workeffort child with FromDate, thruDate and other required details. > 5) Now, again select Children tab to view all associated workeffort children. > 6) Workeffort children listed in tree structure. Select recently created > workeffort child. > Issue - FromDate and thruDate shows empty value when we navigate to child > details page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-7663) FromDate and ThruDate shows empty for WorkEffort Children
[ https://issues.apache.org/jira/browse/OFBIZ-7663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak reassigned OFBIZ-7663: Assignee: Mridul Pathak > FromDate and ThruDate shows empty for WorkEffort Children > -- > > Key: OFBIZ-7663 > URL: https://issues.apache.org/jira/browse/OFBIZ-7663 > Project: OFBiz > Issue Type: Bug > Components: workeffort >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk >Reporter: Ankit Joshi > Assignee: Mridul Pathak >Priority: Minor > Attachments: OFBIZ-7663.patch > > > Steps to regenerate - > 1) Navigate to workeffort -> workeffort > 2) Go to workeffort Details Page. > 3) Select Children tab and click on Add existing Workeffort Child. > 4)Add workeffort child with FromDate, thruDate and other required details. > 5) Now, again select Children tab to view all associated workeffort children. > 6) Workeffort children listed in tree structure. Select recently created > workeffort child. > Issue - FromDate and thruDate shows empty value when we navigate to child > details page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7435) Create Custreq from CommEvent shows error on screen
[ https://issues.apache.org/jira/browse/OFBIZ-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15380598#comment-15380598 ] Mridul Pathak commented on OFBIZ-7435: -- I'll be committing this patch but this is also a dependency of party component on special purpose projectmgr component which needs to be fixed. Another ticket can be created for that. > Create Custreq from CommEvent shows error on screen > --- > > Key: OFBIZ-7435 > URL: https://issues.apache.org/jira/browse/OFBIZ-7435 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Trunk >Reporter: Vishal Chhabria >Assignee: Mridul Pathak > Attachments: OFBIZ-7435.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7829) hhfacility: Remove unused imports from Groovy files for code optimization
[ https://issues.apache.org/jira/browse/OFBIZ-7829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak closed OFBIZ-7829. > hhfacility: Remove unused imports from Groovy files for code optimization > - > > Key: OFBIZ-7829 > URL: https://issues.apache.org/jira/browse/OFBIZ-7829 > Project: OFBiz > Issue Type: Sub-task > Components: specialpurpose/hhfacility >Affects Versions: Trunk >Reporter: Ankit Joshi > Assignee: Mridul Pathak >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-7829-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-7829) hhfacility: Remove unused imports from Groovy files for code optimization
[ https://issues.apache.org/jira/browse/OFBIZ-7829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak reassigned OFBIZ-7829: Assignee: Mridul Pathak > hhfacility: Remove unused imports from Groovy files for code optimization > - > > Key: OFBIZ-7829 > URL: https://issues.apache.org/jira/browse/OFBIZ-7829 > Project: OFBiz > Issue Type: Sub-task > Components: specialpurpose/hhfacility >Affects Versions: Trunk >Reporter: Ankit Joshi > Assignee: Mridul Pathak >Priority: Minor > Fix For: 14.12.01, 15.12.01 > > Attachments: OFBIZ-7829-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7561) Attr Name should not be allowed to edit while updating Party Attribute record
[ https://issues.apache.org/jira/browse/OFBIZ-7561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak closed OFBIZ-7561. > Attr Name should not be allowed to edit while updating Party Attribute record > - > > Key: OFBIZ-7561 > URL: https://issues.apache.org/jira/browse/OFBIZ-7561 > Project: OFBiz > Issue Type: Bug > Components: marketing, party >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk >Reporter: Ankit Joshi > Assignee: Mridul Pathak >Priority: Minor > Fix For: 14.12.01, 15.12.01, 13.07.04 > > Attachments: OFBIZ-7561-13.07.patch, OFBIZ-7561-14.12.patch, > OFBIZ-7561-trunk.patch, UpdatePartyAttribute1.png, UpdatePartyAttribute2.png > > > Steps to regenerate - > 1) Navigate to SFA -> Contacts > 2) Select any contacts and move to detail page. > 3) There is a section to Create / Update Party Attribute. > 4) Create New Party Attribute. > 5) Click on Edit button to update Party Attribute. > Actual: All fields including AttrName is allowed to edit. Process is giving > error in case when user update the AttrName. > Expected : AttrName field should be non-editable while updating the Party > Attribute record as this field is part of the primary key. > Here is the reference link - > https://ofbiz-vm.apache.org:8443/sfa/control/editPartyAttribute?partyId=DemoCustomer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7561) Attr Name should not be allowed to edit while updating Party Attribute record
[ https://issues.apache.org/jira/browse/OFBIZ-7561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak updated OFBIZ-7561: - Component/s: marketing > Attr Name should not be allowed to edit while updating Party Attribute record > - > > Key: OFBIZ-7561 > URL: https://issues.apache.org/jira/browse/OFBIZ-7561 > Project: OFBiz > Issue Type: Bug > Components: marketing, party >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk >Reporter: Ankit Joshi > Assignee: Mridul Pathak >Priority: Minor > Attachments: OFBIZ-7561-13.07.patch, OFBIZ-7561-14.12.patch, > OFBIZ-7561-trunk.patch, UpdatePartyAttribute1.png, UpdatePartyAttribute2.png > > > Steps to regenerate - > 1) Navigate to SFA -> Contacts > 2) Select any contacts and move to detail page. > 3) There is a section to Create / Update Party Attribute. > 4) Create New Party Attribute. > 5) Click on Edit button to update Party Attribute. > Actual: All fields including AttrName is allowed to edit. Process is giving > error in case when user update the AttrName. > Expected : AttrName field should be non-editable while updating the Party > Attribute record as this field is part of the primary key. > Here is the reference link - > https://ofbiz-vm.apache.org:8443/sfa/control/editPartyAttribute?partyId=DemoCustomer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-7561) Attr Name should not be allowed to edit while updating Party Attribute record
[ https://issues.apache.org/jira/browse/OFBIZ-7561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak reassigned OFBIZ-7561: Assignee: Mridul Pathak > Attr Name should not be allowed to edit while updating Party Attribute record > - > > Key: OFBIZ-7561 > URL: https://issues.apache.org/jira/browse/OFBIZ-7561 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk >Reporter: Ankit Joshi > Assignee: Mridul Pathak >Priority: Minor > Attachments: OFBIZ-7561-13.07.patch, OFBIZ-7561-14.12.patch, > OFBIZ-7561-trunk.patch, UpdatePartyAttribute1.png, UpdatePartyAttribute2.png > > > Steps to regenerate - > 1) Navigate to SFA -> Contacts > 2) Select any contacts and move to detail page. > 3) There is a section to Create / Update Party Attribute. > 4) Create New Party Attribute. > 5) Click on Edit button to update Party Attribute. > Actual: All fields including AttrName is allowed to edit. Process is giving > error in case when user update the AttrName. > Expected : AttrName field should be non-editable while updating the Party > Attribute record as this field is part of the primary key. > Here is the reference link - > https://ofbiz-vm.apache.org:8443/sfa/control/editPartyAttribute?partyId=DemoCustomer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7525) UiLabels missing on Examples PDF
[ https://issues.apache.org/jira/browse/OFBIZ-7525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak closed OFBIZ-7525. > UiLabels missing on Examples PDF > > > Key: OFBIZ-7525 > URL: https://issues.apache.org/jira/browse/OFBIZ-7525 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/example >Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12 >Reporter: Ankit Joshi > Assignee: Mridul Pathak >Priority: Minor > Fix For: 14.12.01, 15.12.01 > > Attachments: OFBIZ-7525-14.12.patch, OFBIZ-7525-trunk.patch > > > Steps to regenerate - > 1) Navigate to example > 2) Search Examples and go to details page. > 3) View Example PDF > ExampleUiLabels class is missing from the screen. > Here is the reference link - > https://ofbiz-vm.apache.org:8443/example/control/ExampleReportPdf?exampleId=EX01 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-7525) UiLabels missing on Examples PDF
[ https://issues.apache.org/jira/browse/OFBIZ-7525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak reassigned OFBIZ-7525: Assignee: Mridul Pathak > UiLabels missing on Examples PDF > > > Key: OFBIZ-7525 > URL: https://issues.apache.org/jira/browse/OFBIZ-7525 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/example >Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12 >Reporter: Ankit Joshi > Assignee: Mridul Pathak >Priority: Minor > Attachments: OFBIZ-7525-14.12.patch, OFBIZ-7525-trunk.patch > > > Steps to regenerate - > 1) Navigate to example > 2) Search Examples and go to details page. > 3) View Example PDF > ExampleUiLabels class is missing from the screen. > Here is the reference link - > https://ofbiz-vm.apache.org:8443/example/control/ExampleReportPdf?exampleId=EX01 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7823) Product lookup should be available while adding items in the shopping list
[ https://issues.apache.org/jira/browse/OFBIZ-7823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak closed OFBIZ-7823. > Product lookup should be available while adding items in the shopping list > -- > > Key: OFBIZ-7823 > URL: https://issues.apache.org/jira/browse/OFBIZ-7823 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk >Reporter: Ankit Joshi > Assignee: Mridul Pathak >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-7823_trunk.patch > > > Steps to regenerate - > 1) Navigate to Party Component and search parties. > 2) Go to party detail page and click on shopping list tab. > 3) Create new shopping list if not exist for the party. > 4) Try to add an item to the shopping list. > There should be product lookup to add items easily to the shopping list. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7823) Product lookup should be available while adding items in the shopping list
[ https://issues.apache.org/jira/browse/OFBIZ-7823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak updated OFBIZ-7823: - Summary: Product lookup should be available while adding items in the shopping list (was: Product lookup should be there will adding items in the shopping list) > Product lookup should be available while adding items in the shopping list > -- > > Key: OFBIZ-7823 > URL: https://issues.apache.org/jira/browse/OFBIZ-7823 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk >Reporter: Ankit Joshi > Assignee: Mridul Pathak >Priority: Minor > Attachments: OFBIZ-7823_trunk.patch > > > Steps to regenerate - > 1) Navigate to Party Component and search parties. > 2) Go to party detail page and click on shopping list tab. > 3) Create new shopping list if not exist for the party. > 4) Try to add an item to the shopping list. > There should be product lookup to add items easily to the shopping list. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-7823) Product lookup should be there will adding items in the shopping list
[ https://issues.apache.org/jira/browse/OFBIZ-7823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak reassigned OFBIZ-7823: Assignee: Mridul Pathak > Product lookup should be there will adding items in the shopping list > - > > Key: OFBIZ-7823 > URL: https://issues.apache.org/jira/browse/OFBIZ-7823 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk >Reporter: Ankit Joshi > Assignee: Mridul Pathak >Priority: Minor > Attachments: OFBIZ-7823_trunk.patch > > > Steps to regenerate - > 1) Navigate to Party Component and search parties. > 2) Go to party detail page and click on shopping list tab. > 3) Create new shopping list if not exist for the party. > 4) Try to add an item to the shopping list. > There should be product lookup to add items easily to the shopping list. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7168) Run MRP shows all type of facilities
[ https://issues.apache.org/jira/browse/OFBIZ-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mridul Pathak closed OFBIZ-7168. > Run MRP shows all type of facilities > > > Key: OFBIZ-7168 > URL: https://issues.apache.org/jira/browse/OFBIZ-7168 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing >Affects Versions: Trunk >Reporter: Sanjay Yadav > Assignee: Mridul Pathak > Fix For: Upcoming Branch > > Attachments: OFBIZ-7168_trunk.patch > > > When we go to Run MRP screen, all types of facilities (including facilities > with no type) are listed here in the Facility drop down. > I think, It's better to list only WAREHOUSE or some specific type of > facilities. Basically, there is no meaning of showing facilities which don't > have proper type or type is not available for e.g. CALL_CENTER, FLOOR etc. > Let me know if anyone have any thoughts on this. Thanks! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7168) Run MRP shows all type of facilities
[ https://issues.apache.org/jira/browse/OFBIZ-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15380552#comment-15380552 ] Mridul Pathak commented on OFBIZ-7168: -- Committed this change in trunk r1752893 as no further concerns were raised. Thanks [~sanjay.ya...@hotwaxsystems.com] for reporting the issue and [~ankit.joshi] for providing the patch. > Run MRP shows all type of facilities > > > Key: OFBIZ-7168 > URL: https://issues.apache.org/jira/browse/OFBIZ-7168 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing >Affects Versions: Trunk >Reporter: Sanjay Yadav >Assignee: Mridul Pathak > Attachments: OFBIZ-7168_trunk.patch > > > When we go to Run MRP screen, all types of facilities (including facilities > with no type) are listed here in the Facility drop down. > I think, It's better to list only WAREHOUSE or some specific type of > facilities. Basically, there is no meaning of showing facilities which don't > have proper type or type is not available for e.g. CALL_CENTER, FLOOR etc. > Let me know if anyone have any thoughts on this. Thanks! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-7168) Run MRP shows all type of facilities
[ https://issues.apache.org/jira/browse/OFBIZ-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15380552#comment-15380552 ] Mridul Pathak edited comment on OFBIZ-7168 at 7/16/16 6:20 AM: --- Committed this change in trunk r1752893 as no further concerns were raised. Thanks [~sanjay.ya...@hotwaxsystems.com] for reporting the issue and [~ankit.joshi] for providing the patch. Thanks [~pfm.smits] for review. was (Author: mridul.pathak): Committed this change in trunk r1752893 as no further concerns were raised. Thanks [~sanjay.ya...@hotwaxsystems.com] for reporting the issue and [~ankit.joshi] for providing the patch. > Run MRP shows all type of facilities > > > Key: OFBIZ-7168 > URL: https://issues.apache.org/jira/browse/OFBIZ-7168 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing >Affects Versions: Trunk >Reporter: Sanjay Yadav >Assignee: Mridul Pathak > Attachments: OFBIZ-7168_trunk.patch > > > When we go to Run MRP screen, all types of facilities (including facilities > with no type) are listed here in the Facility drop down. > I think, It's better to list only WAREHOUSE or some specific type of > facilities. Basically, there is no meaning of showing facilities which don't > have proper type or type is not available for e.g. CALL_CENTER, FLOOR etc. > Let me know if anyone have any thoughts on this. Thanks! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
