Re: Welcome to Devanshu Vyas as new committer!
Many Congratulations Devanshu!! Regards, Ratnesh Upadhyay HotWax Systems | www.hotwaxsystems.com On Wed, Aug 19, 2020 at 2:32 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: Welcome Rishi Solanki as new PMC member
Many Congratulations Rishi. Regards, Ratnesh Upadhyay www.hotwaxsystems.com On 28-Apr-2020 7:53 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: Welcome to Girish Vasmatkar as new committer!
Many Congratulations Girish!! Regards, Ratnesh Upadhyay www.hotwaxsystems.com On Wed, Apr 22, 2020 at 5:36 PM Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > Sorry I missed Girish 1st name in subject :/ > > Le 22/04/2020 à 11:37, Jacques Le Roux a écrit : > > 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: Welcome Swapnil M Mane as new PMC member
Many Congratulations Swapnil. Regards, Ratnesh Upadhyay www.hotwaxsystems.com 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: ReturnContactMech is not used
+1 Good catch, Vaibhav! Thanks! Regards, Ratnesh Upadhyay On Sat, Apr 27, 2019 at 12:33 PM Vaibhav Jain < vaibhav.j...@hotwaxsystems.com> wrote: > *Bottom line:* > ReturnContactMech entity is not used in OFBiz > > *Story:* > ContactMech of parties involved in an order is captured in OrderContactMech > entity. > ContactMech of parties involved in the return is not captured in > ReturnContactMech entity. > > Kind Regards, > *Vaibhav Jain* | Senior Enterprise Software Engineer > HotWax Systems <http://www.hotwaxsystems.com/> > Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center, > Indore, > M.P 452010 > Linkedin: *Vaibhav Jain* <https://www.linkedin.com/in/vaibhav-jain-170793/ > > > > [image: Mailtrack] > < > https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&; > > > Sender > notified by > Mailtrack > < > https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&; > > > 04/27/19, > 12:23:48 PM
Re: OFBiz as Marketplace
Greetings to All, FYI, we have started preparing user stories for marketplace and planning to locate them at Home > Documentation > OFBiz Features > Proposed Features > Marketplace. Suggestions are always welcome. Thanks! Regards, Ratnesh Upadhyay HotWax Systems | www.hotwaxsystems.com On Sat, Dec 8, 2018 at 7:35 PM Rishi Solanki wrote: > Thank you Ratnesh for nicely summarizing all the details. And yes we can go > with this plan and will change it as we move forward. > > -- > Rishi Solanki > Sr Manager, Enterprise Software Development > HotWax Systems Pvt. Ltd. > Direct: +91-9893287847 > http://www.hotwaxsystems.com > www.hotwax.co > > > On Fri, Dec 7, 2018 at 6:27 PM Ratnesh Upadhyay < > upadhyay.ratn...@gmail.com> > wrote: > > > Hi Devs, > > > > Thanks everyone for such a valuable discussion and inputs. Before we > start > > on user stories I would like to share the basic plan based upon inputs on > > this thread. Ideally we should have three main actors Customers, Sellers > > and Marketplace Operators in system and now we can define the user > stories > > on the basis these actors.Here are features/workflows that we are > targeting > > to implement for all these three actors : > > > > 1) Marketplace For Customers: > > > >- Customer should be able to see different sellers selling same > product > >and prices offered. > >- Customer should be able to purchase product from range of sellers. > >- Customer should be able to see all offers and promotions by sellers > >and best offer with lower price or promoted seller on marketplace > > should be > >on top. > >- Customer should be able to see shipping rates and return policy of > the > >seller. > >- Customer can see seller profile with following information. > > - Launch date > > - Return and Warranties > > - Shipping > > - Policies > > - Rating > > - Products (Other products sale by seller) > >- Customer can purchase products from different sellers in single > order. > > > > 2) Marketplace For Seller: > > > >- Seller profile registration. > >- Seller profile approval or listing process, > >- Seller can add other users to access account like catalog manager, > >order manager etc by permission. > >- User permission management. > >- Manage Seller Profile > >- Product Management > > - Add product new/existing. > > - Inventory management. > > - Price management for product. > > - Activate and Deactivate product listing. > > - Add promotion to products. > >- Manage Order > > - Approve > > - Cancel > >- Shipment Management > > - Ship by marketplace flow > > - Ship by seller flow > >- Inventory Mangement > > - By marketplace > > - By seller > >- Manage Return > > - Issue refund for the cancel order by customer. That means get > > shipped product back if not accepted at customer end due to some > > reason. > > - Receive item and issue refund amount. On receiving the item tell > > marketplace to issue refund. > > > > 3) Marketplace Operator: > > > >- Manage Sellers Listing Approval process. > >- Manage Global Catalog > >- Manage seller performance. > >- Marketing Campaign > >- Manage commission setup etc > > - More items needs to be identified. > > > > Additionally we need to consider the service industry for marketplace. > For > > that we need to consider the payment term, product setting and other > > service industry related things differently. Will come up with more > > thoughts while working on user stories. > > > > Thanks Rishi for discussion and finalising the plan. I think we are good > to > > proceed with user stories as per aforementioned plan. > > > > Regards, > > Ratnesh Upadhyay > > HotWax Systems | www,hotwaxsystems.com > > > > On Tue, Dec 4, 2018 at 2:22 PM Rishi Solanki > > wrote: > > > > > Thanks Jacques for the interesting article. And yes we should consider > > the > > > service industry as well for marketplace. > > > > > > -- > > > Rishi Solanki > > > Sr Manager, Enterprise Software Development > > > HotWax Systems Pvt. Ltd. > > > Direct: +91-9893287847 > > > http://www.hotwaxsystems.com > > > www.hotwax.co > > > > > > >
Re: OFBiz as Marketplace
Hi Devs, Thanks everyone for such a valuable discussion and inputs. Before we start on user stories I would like to share the basic plan based upon inputs on this thread. Ideally we should have three main actors Customers, Sellers and Marketplace Operators in system and now we can define the user stories on the basis these actors.Here are features/workflows that we are targeting to implement for all these three actors : 1) Marketplace For Customers: - Customer should be able to see different sellers selling same product and prices offered. - Customer should be able to purchase product from range of sellers. - Customer should be able to see all offers and promotions by sellers and best offer with lower price or promoted seller on marketplace should be on top. - Customer should be able to see shipping rates and return policy of the seller. - Customer can see seller profile with following information. - Launch date - Return and Warranties - Shipping - Policies - Rating - Products (Other products sale by seller) - Customer can purchase products from different sellers in single order. 2) Marketplace For Seller: - Seller profile registration. - Seller profile approval or listing process, - Seller can add other users to access account like catalog manager, order manager etc by permission. - User permission management. - Manage Seller Profile - Product Management - Add product new/existing. - Inventory management. - Price management for product. - Activate and Deactivate product listing. - Add promotion to products. - Manage Order - Approve - Cancel - Shipment Management - Ship by marketplace flow - Ship by seller flow - Inventory Mangement - By marketplace - By seller - Manage Return - Issue refund for the cancel order by customer. That means get shipped product back if not accepted at customer end due to some reason. - Receive item and issue refund amount. On receiving the item tell marketplace to issue refund. 3) Marketplace Operator: - Manage Sellers Listing Approval process. - Manage Global Catalog - Manage seller performance. - Marketing Campaign - Manage commission setup etc - More items needs to be identified. Additionally we need to consider the service industry for marketplace. For that we need to consider the payment term, product setting and other service industry related things differently. Will come up with more thoughts while working on user stories. Thanks Rishi for discussion and finalising the plan. I think we are good to proceed with user stories as per aforementioned plan. Regards, Ratnesh Upadhyay HotWax Systems | www,hotwaxsystems.com On Tue, Dec 4, 2018 at 2:22 PM Rishi Solanki wrote: > Thanks Jacques for the interesting article. And yes we should consider the > service industry as well for marketplace. > > -- > Rishi Solanki > Sr Manager, Enterprise Software Development > HotWax Systems Pvt. Ltd. > Direct: +91-9893287847 > http://www.hotwaxsystems.com > www.hotwax.co > > > On Thu, Nov 29, 2018 at 2:56 PM Jacques Le Roux < > jacques.le.r...@les7arts.com> wrote: > > > Somehow related I stumbled upon this article recently > > > > > https://andrewchen.co/how-marketplaces-will-reinvent-the-service-economy/ > > > > Jacques > > > > > > Le 22/11/2018 à 06:43, Rishi Solanki a écrit : > > > Thank you all for your votes and I think now most of us agree with the > > > idea. So I'll proceed with the plan and start preparing user stories > > around > > > it. Thank you very much Michael for clarifying the understanding. > > > > > > @Taher, I really tried very hard to connect both ideas and wanted to > run > > > them in parallel :-). Please feel free to include me in your idea where > > you > > > feel I can help and you can use. > > > > > > +1 from my side for plugin marketplace, I would be happy to be part of > > that > > > effort. > > > > > > > > > -- > > > Rishi Solanki > > > Sr Manager, Enterprise Software Development > > > HotWax Systems Pvt. Ltd. > > > Direct: +91-9893287847 > > > http://www.hotwaxsystems.com > > > www.hotwax.co > > > > > > > > > On Thu, Nov 22, 2018 at 10:29 AM Aditya Sharma < > > > aditya.sha...@hotwaxsystems.com> wrote: > > > > > >> Nice initiative. > > >> > > >> +1 for the marketplace as a new OFBiz plugin > > >> > > >> Thanks and Regards, > > >> > > >> *Aditya Sharma* | Enterprise Software Engineer > > >> HotWax Commerce
Re: [Proposal] Return History Feature in eCommerce
Thanks everyone!! Here is the jira ticket for the same. < https://issues.apache.org/jira/browse/OFBIZ-10630> Regards, Ratnesh Upadhyay HotWax Systems | www.hotwaxsystems.com On Sat, Oct 27, 2018 at 6:21 PM Yogesh Naroliya < yogesh.narol...@hotwaxsystems.com> wrote: > +1 > > > Thanks & Regards, > > Yogesh Naroliya > > > On Mon, Apr 30, 2018 at 5:34 PM Arun Patidar < > arun.pati...@hotwaxsystems.com> > wrote: > > > +1 > > > > Thanks & Regards > > --- > > Arun Patidar > > Director of Information SystemsHotWax Commerce <http://www.hotwax.co> > > > > > > On Mon, Apr 30, 2018 at 4:48 PM, Devanshu Vyas < > vyas.devansh...@gmail.com> > > wrote: > > > > > +1 > > > > > > Thanks & Regards, > > > Devanshu Vyas. > > > > > > > > > On Sat, Apr 28, 2018 at 7:13 PM Ratnesh Upadhyay < > > > upadhyay.ratn...@gmail.com> > > > wrote: > > > > > > > Hi Devs, > > > > > > > > I have gone through eCommerce application and noticed that we have > > order > > > > history section there but we don't have return history. So I would > like > > > to > > > > propose "Return History" feature in eCommerce application. Please let > > me > > > > know your views on it. > > > > > > > > Thanks!! > > > > > > > > Regards, > > > > Ratnesh Upadhyay > > > > HotWax Systems | www.hotwaxsystems.com > > > > > > > > >
Re: New ASF Member from OFBiz Community
Many Congratulations Deepak!! Regards, Ratnesh Upadhyay HotWax Systems | www.hotwaxsystems.com On Wed, May 2, 2018 at 9:08 PM, Jacopo Cappellato < jacopo.cappell...@hotwaxsystems.com> wrote: > Hi Everyone, > > today the ASF has published the list of newly nominated members and "our" > Deepak Dixit is one of them: > > https://blogs.apache.org/foundation/entry/the-apache- > software-foundation-welcomes2 > <https://www.google.com/url?q=https://blogs.apache.org/ > foundation/entry/the-apache-software-foundation-welcomes2& > sa=D&source=hangouts&ust=1525357595561000&usg= > AFQjCNHXDpgnyJ1wgnbZ06kEPTsbXs9MDQ> > > Congratulations Deepak! > > Jacopo
[Proposal] Return History Feature in eCommerce
Hi Devs, I have gone through eCommerce application and noticed that we have order history section there but we don't have return history. So I would like to propose "Return History" feature in eCommerce application. Please let me know your views on it. Thanks!! Regards, Ratnesh Upadhyay HotWax Systems | www.hotwaxsystems.com
Re: Welcome Paul Foxworthy as a new PMC member
Many Congratulations Paul..!! Regards, Ratnesh Upadhyay On Wed, Mar 21, 2018 at 2:12 PM, Jacopo Cappellato < jacopo.cappell...@gmail.com> wrote: > The OFBiz PMC has invited Paul Foxworthy to become a new member of the > committee and we are glad to announce that Paul has accepted the > nomination. > > Welcome on board Paul! > > Jacopo Cappellato (on behalf of the OFBiz PMC) >
Re: Adding new company detail. ?
Hi Juan, As per the logs it seems that a contactMech with Id "10002" has already been persisted in your database. You can fix it by setting up maximum count in SequenceValueItem entity for contactMech and restart the server to get the next sequence Id. Thanks! Regards, Ratnesh Upadhyay HotWax Systems | www.hotwaxsystems.com On Mon, Jan 22, 2018 at 2:05 PM, Julian Smith wrote: > The Following Errors Occurred: > > Exception thrown while creating the "newValue" GenericValue: > org.apache.ofbiz.entity.GenericEntityException: Error while inserting: > [GenericEntity:ContactMech][contactMechId,10002(java.lang. > String)][contactMechTypeId,WEB_ADDRESS(java.lang.String)] > [createdStamp,2018-01-22 > 19:30:51.839(java.sql.Timestamp)][createdTxStamp,2018-01-22 > 19:30:51.788(java.sql.Timestamp)][infoString,https://blockfreight.com > (java.lang.String)][lastUpdatedStamp,2018-01-22 19:30:51.839(java.sql. > Timestamp)][lastUpdatedTxStamp,2018-01-22 19:30:51.788(java.sql. > Timestamp)] > (SQL Exception while executing the following:INSERT INTO CONTACT_MECH > (CONTACT_MECH_ID, CONTACT_MECH_TYPE_ID, INFO_STRING, LAST_UPDATED_STAMP, > LAST_UPDATED_TX_STAMP, CREATED_STAMP, CREATED_TX_STAMP) VALUES (?, ?, ?, ?, > ?, ?, ?) ((conn=1857) Duplicate entry '10002' for key 'PRIMARY')) (Error > while inserting: [GenericEntity:ContactMech][ > contactMechId,10002(java.lang. > String)][contactMechTypeId,WEB_ADDRESS(java.lang.String)] > [createdStamp,2018-01-22 > 19:30:51.839(java.sql.Timestamp)][createdTxStamp,2018-01-22 > 19:30:51.788(java.sql.Timestamp)][infoString,https://blockfreight.com > (java.lang.String)][lastUpdatedStamp,2018-01-22 19:30:51.839(java.sql. > Timestamp)][lastUpdatedTxStamp,2018-01-22 19:30:51.788(java.sql. > Timestamp)] > (SQL Exception while executing the following:INSERT INTO CONTACT_MECH > (CONTACT_MECH_ID, CONTACT_MECH_TYPE_ID, INFO_STRING, LAST_UPDATED_STAMP, > LAST_UPDATED_TX_STAMP, CREATED_STAMP, CREATED_TX_STAMP) VALUES (?, ?, ?, ?, > ?, ?, ?) ((conn=1857) Duplicate entry '10002' for key 'PRIMARY'))) >
Re: Proposal to remove the "Special Notice" section from the OFBiz download page
+1 Regards, Ratnesh Upadhyay HotWax Systems | www.hotwaxsystems.com On Fri, Jan 5, 2018 at 3:32 PM, Jacopo Cappellato < jacopo.cappell...@hotwaxsystems.com> wrote: > Hi all, > > I think we should now remove the section titled "Special Notice Regarding > Branches 14.12 and 15.12" from the OFBiz download page: > > https://ofbiz.apache.org/download.html > > The page should only list the most recent release from each actively > maintained branch; the section has been useful while we were migrating our > scripts but I think that now only adds confusion. > > Any objections? > > Jacopo >
Re: Purchase Order Cancel status
Hi Renuka,
I would also prefer to remove this condition as it's not making sense to
keep order in created status when all the order items get canceled.
Thanks!!
Regards,
Ratnesh Upadhyay
HotWax Systems | www.hotwaxsystems.com
On Fri, Oct 6, 2017 at 12:52 PM, Deepak Dixit <
deepak.di...@hotwaxsystems.com> wrote:
> Hi Renuka,
>
> I see no reason to keen this condition. we can remove this.
> As I know there is no business scenario around this. If all order item
> cancelled than order should be cancel either its Sales or Purchase order.
>
>
>
> Thanks & Regards
> --
> Deepak Dixit
> www.hotwaxsystems.com
> www.hotwax.co
>
> On Thu, Oct 5, 2017 at 7:17 PM, Renuka Srishti >
> wrote:
>
> > Hello Devs,
> >
> > This is reference to
> > http://markmail.org/message/wggbvdumrndpkxrj
> >
> > In "applications/order/src/org/ofbiz/order/order/OrderServices.java",
> > under
> > "checkItemStatus" service, there is one check for all item cancelled:
> >
> > if (!"PURCHASE_ORDER".equals(orderTypeId)) {
> > newStatus = "ORDER_CANCELLED";
> > }
> >
> > I was trying to find out the reason behind it but did not get any.
> >
> > When we cancel all the items of an order, Order should cancel at the
> header
> > level too. Then why we have added this special check for purchase order?
> >
> > Becuase of this check, after canceling of all the items, purchase order
> do
> > not get canceled at the header level. Currently, we need to cancel the
> > purchase order manually.
> >
> >
> > Thanks
> > Renuka Srishti
> >
>
Re: [ANNOUNCE] The Big Book for Apache OFBiz Data Model 2017 Released
Nice Work. Thanks, everyone! Regards, Ratnesh Upadhyay On Wed, Oct 4, 2017 at 7:16 PM, Aditya Sharma < aditya.sha...@hotwaxsystems.com> wrote: > My Bad. Just missed something important. > > Thanks to Sonal Patwari for all the effort she put in this whole task. > > Thanks to Pranay Pandey and Deepak Dixit for the guidance provided. > > Thanks and Regards, > > *Aditya Sharma* | Enterprise Software Engineer > HotWax Systems <http://www.hotwaxsystems.com/> > <https://www.linkedin.com/in/aditya-sharma-78291810a/> > > On Wed, Oct 4, 2017 at 6:03 PM, Michael Brohl > wrote: > > > That's really great, thank you very much for your efforts, Aditya! > > > > Best regards, > > > > Michael > > > > > > Am 04.10.17 um 13:15 schrieb Aditya Sharma: > > > >> Hello All, > >> > >> It gives me immense pleasure informing you all that we have updated *The > >> Big > >> Book of Apache OFBiz Data Model* according to the latest trunk version. > >> > >> The key features: > >> * Colored content with titles according to the internal color pattern. > >> * Addition of a separate page for integration specific entities. > >> * Removal of technical process diagrams, making it specific for > entities. > >> * Addition of 77 new entities. > >> * Removal of 8 entities. > >> * Addition of around 200+ new fields in entities (Though major portion > >> includes the addition of description or attrDescription fields in > >> *Attribute or *TypeAttr entities). > >> * Removal of 24 fields. > >> > >> I have uploaded the files on Data Model Diagrams page. Here is the link > >> <https://cwiki.apache.org/confluence/x/8ILK>. > >> > >> Cheers! > >> > >> *Aditya Sharma* | Enterprise Software Engineer > >> HotWax Systems <http://www.hotwaxsystems.com/> > >> <https://www.linkedin.com/in/aditya-sharma-78291810a/> > >> > >> > > > > >
Re: [Proposal] Ability to Record Return Communication
Hi Jacques, Thanks for the response. I was thinking that retrieval gets slow down when we have a lot of data in communication event entity. Actually, I've prepared this proposal based on the current implementation of CommunicationEventOrder on this assumption that it's an approved feature that's its there in the system. I am also in agreement with you and Deepak to use the existing (generic) data model to achieve this. I'll give it another thought and further analyze it to fit in existing data model. Thanks!! Regards, Ratnesh Upadhyay HotWax Systems | www.hotwaxsystems.com On Sat, Sep 23, 2017 at 5:37 PM, Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > Le 23/09/2017 à 13:14, Ratnesh Upadhyay a écrit : > >> Imagine if we use the generic data model to record each kind of >> communication and when the system tries to pull a specific email or >> specific type email communication from this model then system has to >> browse >> a lot of data and due to this most of the time, it gets ended up with slow >> query/browsing issue. So to avoid such performance issue instead of >> extending CommunicationEvent entity, I proposed to make a separate entity. >> > Hi Ratnesh, > > Are you sure about that? What would the bottleneck? If you think the DB > would slow down I don't think it's an issue. > > My take is that I prefer a generic data model rather than sacrificing for > hypothetical performance and end up with data model like competitors with > thousands of entities (OFBiz is currently still around 800+) > > Jacques >
Re: [Proposal] Ability to Record Return Communication
Your assumption is correct, Rishi thanks for the inputs. Regards, Ratnesh Upadhyay HotWax Systems | www.hotwaxsystems.com On Sat, Sep 23, 2017 at 4:05 PM, Rishi Solanki wrote: > +1 for the proposal, I'll be happy to discuss and finalizing the things. > > Assuming that you have already consider ProductStoreEmailSetting and > EmailTemplateSetting for sending the different notification for return. > > Rishi Solanki > Sr Manager, Enterprise Software Development > HotWax Systems Pvt. Ltd. > Direct: +91-9893287847 > http://www.hotwaxsystems.com > www.hotwax.co > > On Sat, Sep 23, 2017 at 3:44 PM, Ratnesh Upadhyay < > upadhyay.ratn...@gmail.com> wrote: > > > Hi Devs, > > > > In OOTB we are having the ability to record order specific communication > in > > *CommunicationEventOrder* and the user can retrieve/review them from > party > > > communications screen but we don't have such support for return > > communications. So It would be great to have an ability to record return > > specific communication in the system. > > > > We have to implement following items to establish this feature : > > > > *Data Model Details:* > > - We will have to create new entity *CommunicationEventReturn* to record > > return communication. It should have returnId and communicationEventId > > along with other necessary fields. > > - We have to implement following view *CommunicationEventAndReturn* to > > fetch return communications over screens as needed. > > > > *New Implementation Details:* > > - We have to add *CRUD* services for the new entity. > > > > *Existing Implementation Details:* > > - We have to extend *createCommunicationEvent* service definition with > > retunId field and extend the existing implementation to create the record > > in *CommunicationEventReturn* based on supplied returnId parameter. > > - Also, we have to extend return related email services to provide > returnId > > in service context. > > > > *User Interface Details:* > > - In the current system we have Party > Communications > Find > Communication > > By Order screen, in the same way, we can add another screen to find > > communication by return. > > - We can add return communication screenlet over Order Manager > Return > > > Return History screen or we can add communication tab under Order > > Return > > screen, this is just a thought still thinking on it. > > - We can also provide communication tab in order component as well. > > > > Please have a look at details and let me know your inputs. I'll log Jira > > ticket to implement this feature soon. > > > > Thanks!! > > > > Regards, > > Ratnesh Upadhyay > > HotWax Systems | www.hotwaxsystems.com > > >
Re: [Proposal] Ability to Record Return Communication
Thanks for your inputs Deepak. Agreed that CommunicationEvent is way generic and this is the main use case to keep the order and return separately from this model as they are using most frequently in each business. Imagine if we use the generic data model to record each kind of communication and when the system tries to pull a specific email or specific type email communication from this model then system has to browse a lot of data and due to this most of the time, it gets ended up with slow query/browsing issue. So to avoid such performance issue instead of extending CommunicationEvent entity, I proposed to make a separate entity. Definitely, we can think more on it to find the more generic way to record this information in the system. Regards, Ratnesh Upadhyay HotWax Systems | www.hotwaxsystems.com On Sat, Sep 23, 2017 at 4:05 PM, Deepak Dixit wrote: > Hi Ratnesh, > > I like you idea, but instead of adding new entity can we define some > generic way to use CommunicationEvent along with all kind of activity. > Like CommunicationEvent is generic DataModel, it applicable for invoice, > workEffort, marketing campaign, contact list, order , return, etc. > > As per current implementation some values are exists in CommunicationEvent > entity and some are in assoc pattern. > > So creating new entity for each model will be too much. Any other opinion? > > > Thanks & Regards > -- > Deepak Dixit > www.hotwaxsystems.com > www.hotwax.co > > On Sat, Sep 23, 2017 at 3:44 PM, Ratnesh Upadhyay < > upadhyay.ratn...@gmail.com> wrote: > > > Hi Devs, > > > > In OOTB we are having the ability to record order specific communication > in > > *CommunicationEventOrder* and the user can retrieve/review them from > party > > > communications screen but we don't have such support for return > > communications. So It would be great to have an ability to record return > > specific communication in the system. > > > > We have to implement following items to establish this feature : > > > > *Data Model Details:* > > - We will have to create new entity *CommunicationEventReturn* to record > > return communication. It should have returnId and communicationEventId > > along with other necessary fields. > > - We have to implement following view *CommunicationEventAndReturn* to > > fetch return communications over screens as needed. > > > > *New Implementation Details:* > > - We have to add *CRUD* services for the new entity. > > > > *Existing Implementation Details:* > > - We have to extend *createCommunicationEvent* service definition with > > retunId field and extend the existing implementation to create the record > > in *CommunicationEventReturn* based on supplied returnId parameter. > > - Also, we have to extend return related email services to provide > returnId > > in service context. > > > > *User Interface Details:* > > - In the current system we have Party > Communications > Find > Communication > > By Order screen, in the same way, we can add another screen to find > > communication by return. > > - We can add return communication screenlet over Order Manager > Return > > > Return History screen or we can add communication tab under Order > > Return > > screen, this is just a thought still thinking on it. > > - We can also provide communication tab in order component as well. > > > > Please have a look at details and let me know your inputs. I'll log Jira > > ticket to implement this feature soon. > > > > Thanks!! > > > > Regards, > > Ratnesh Upadhyay > > HotWax Systems | www.hotwaxsystems.com > > >
[Proposal] Ability to Record Return Communication
Hi Devs, In OOTB we are having the ability to record order specific communication in *CommunicationEventOrder* and the user can retrieve/review them from party > communications screen but we don't have such support for return communications. So It would be great to have an ability to record return specific communication in the system. We have to implement following items to establish this feature : *Data Model Details:* - We will have to create new entity *CommunicationEventReturn* to record return communication. It should have returnId and communicationEventId along with other necessary fields. - We have to implement following view *CommunicationEventAndReturn* to fetch return communications over screens as needed. *New Implementation Details:* - We have to add *CRUD* services for the new entity. *Existing Implementation Details:* - We have to extend *createCommunicationEvent* service definition with retunId field and extend the existing implementation to create the record in *CommunicationEventReturn* based on supplied returnId parameter. - Also, we have to extend return related email services to provide returnId in service context. *User Interface Details:* - In the current system we have Party > Communications > Find Communication By Order screen, in the same way, we can add another screen to find communication by return. - We can add return communication screenlet over Order Manager > Return > Return History screen or we can add communication tab under Order > Return screen, this is just a thought still thinking on it. - We can also provide communication tab in order component as well. Please have a look at details and let me know your inputs. I'll log Jira ticket to implement this feature soon. Thanks!! Regards, Ratnesh Upadhyay HotWax Systems | www.hotwaxsystems.com
Re: OFBiz Core Dependency on Plugins
Thanks, Rishi, Michael and Taher for the inputs.
I'll review the shared Jira tickets and update them as needed.
Regards,
Ratnesh Upadhyay
HotWax Systems | www.hotwaxsystems.com
On Sun, Sep 10, 2017 at 12:45 AM, Michael Brohl
wrote:
> Yeah right, that was the missing Jira.
>
> Thanks Taher!
>
> Am 09.09.17 um 21:12 schrieb Taher Alkhateeb:
>
> Not sure but maybe below would help. If you follow the links you will find
>> our discussion regarding default email templates.
>>
>> https://issues.apache.org/jira/browse/OFBIZ-9322
>>
>> On Sep 9, 2017 10:08 PM, "Michael Brohl"
>> wrote:
>>
>> Hi Ratnesh,
>>
>> thanks for bringing this up again.
>>
>> I'm pretty sure that we have discussed this before and there may already
>> exist a Jira for it.
>>
>> I think it should be relatively easy to move the email screens from
>> ecommerce to the order component.
>>
>> Thanks and regards,
>>
>> Michael
>>
>>
>> Am 09.09.17 um 17:10 schrieb Ratnesh Upadhyay:
>>
>> Devs,
>>
>>> While reviewing email services, I noticed that we are still having
>>> references of plugins component (ecommerce) in core components.
>>>
>>> Here is the quick references : (order/data/DemoProduct.xml)
>>> >> emailType="PRDS_ODR_CONFIRM"
>>> bodyScreenLocation="component://ecommerce/widget/EmailOrderS
>>> creens.xml#OrderConfirmNotice"
>>> xslfoAttachScreenLocation="component://ecommerce/widget/Emai
>>> lOrderScreens.xml#OrderConfirmNoticePdf"
>>> subject="OFBiz Demo - Order Confirmation #${orderId}" bccAddress="
>>> ofbizt...@example.com" fromAddress="ofbizt...@example.com"/>
>>>
>>> There are some more occurrences (in controller, screens, menus), I'll
>>> log a
>>> Jira ticket and share all the details there to resolve all such
>>> dependencies.
>>> I'm pretty sure that it's not intentional as the community did big effort
>>> to resolve dependencies while creating plugins but still Its good to get
>>> confirmation from the community.
>>>
>>> Thanks!!
>>>
>>> Regards,
>>> Ratnesh Upadhyay
>>> HotWax Systems | www.hotwaxsystems.com
>>>
>>>
>>>
>
OFBiz Core Dependency on Plugins
Devs, While reviewing email services, I noticed that we are still having references of plugins component (ecommerce) in core components. Here is the quick references : (order/data/DemoProduct.xml) There are some more occurrences (in controller, screens, menus), I'll log a Jira ticket and share all the details there to resolve all such dependencies. I'm pretty sure that it's not intentional as the community did big effort to resolve dependencies while creating plugins but still Its good to get confirmation from the community. Thanks!! Regards, Ratnesh Upadhyay HotWax Systems | www.hotwaxsystems.com
Re: OrderHeader And WebSite Relationship
Thanks, Chandan!! Regards, Ratnesh Upadhyay HotWax Systems | www.hotwaxsystems.com On Thu, Aug 31, 2017 at 1:37 PM, Chandan Khandelwal < chandan.khandel...@hotwaxsystems.com> wrote: > Hi All, > > I have created parent ticket to manage this effort throughout the > application > > Ticket: https://issues.apache.org/jira/browse/OFBIZ-9671 > > -- > Thanks & Regards, > Chandan Khandelwal > HotWax Systems > Direct: +91-9893481076 > http://www.hotwaxsystems.com/ > > On Wed, Aug 30, 2017 at 9:20 PM, Ratnesh Upadhyay < > upadhyay.ratn...@gmail.com> wrote: > > > Thanks everyone for your inputs. I'll add record for "OrderEntry" website > > and relationship. > > > > @Jacques, I reviewed the usage of OrderTestData.xml and found that it's > > using by test-suite "ordertests" and I think it will work as we have > entry > > for this suite in order/ofbiz-component.xml. > > > > Regards, > > Ratnesh Upadhyay > > HotWax Systems | www.hotwaxsystems.com > > > > On Sun, Aug 27, 2017 at 12:24 AM, Jacques Le Roux < > > jacques.le.r...@les7arts.com> wrote: > > > > > Hi Ratnesh, > > > > > > About 1 and 2, in such cases I always try to find the roots. > > > > > > 1. It's https://issues.apache.org/jira/browse/OFBIZ-290 look for > > > webSiteId,OrderEntry > > > 2. http://svn.apache.org/viewvc?view=revision&revision=1128984 > > > > > > Unfortunately seems that this not add much. I also wonder if the data > in > > > OrderTestData.xml are ever used (else tests would fail, right?) > > > > > > Anyway, I agree with your conclusion. > > > > > > My 2cts > > > > > > Jacques > > > > > > > > > > > > Le 26/08/2017 à 14:48, Ratnesh Upadhyay a écrit : > > > > > >> Devs, > > >> > > >> I've noticed few things that needs to be discussed : > > >> > > >> 1. We have few order in DemoOrderTestData.xml and OrderTestData.xml > > that > > >> are having webSiteId="OrderEntry" but we don't have any record in > > WebSite > > >> entity for "OrderEntry" webSiteId. > > >> 2. We have "setCustRequestStatus" and "setCustRequestStatus" ecas > where > > we > > >> are having following condition : > > >> value="OrderEntry"/> > > >> Although we don't have this webSite record in entity then these ecas > are > > >> no > > >> more of use as system never meet this condition. > > >> 3. There is no "webSiteId" is being set for orders placed from > ordermgr > > >> application, so IMO we should setup webSiteId parameter in > > servletConetext > > >> of ordermgr app to get it setup. I can see its usage to get the > > >> information > > >> of orders placed from store front as well as from backend application. > > >> > > >> To apply FK constraint either we have to add record in WebSite entity > or > > >> remove the references of "OrderEntry" webSiteId from order demo data. > > Also > > >> please let me know your thoughts to set webSiteId for backend apps. > > >> > > >> IMO, we should add record in WebSite entity for "OrderEntry". > > >> > > >> Thanks!! > > >> > > >> Regards, > > >> Ratnesh Upadhyay > > >> HotWax Systems | www.hotwaxsystems.com > > >> > > >> > > >> > > >> > > >> > > >> On Sat, Aug 26, 2017 at 1:08 PM, Ratnesh Upadhyay < > > >> upadhyay.ratn...@gmail.com> wrote: > > >> > > >> Thanks everyone for your inputs. > > >>> Here is the jira ticket : https://issues.apache.org/jira > > >>> /browse/OFBIZ-9647 > > >>> > > >>> Regards, > > >>> Ratnesh Upadhyay > > >>> HotWax System | www.hotwaxsystems.com > > >>> > > >>> > > >>> On Sat, Aug 26, 2017 at 11:54 AM, Arun Patidar < > > >>> arun.pati...@hotwaxsystems.com> wrote: > > >>> > > >>> Nice catch Ratnesh, we can take this as an improvement. > > >>>> > > >>>> > > >>>> > > >>>> -- > > >>>> Thanks & Regards > > >>>> --- > > >>>> Arun Patidar > > >>>> Manager, Enterprise Software Development > > >>>> > > >>>> > > >>>> HotWax Systems Pvt Ltd.www.hotwaxsystems.com > > >>>> > > >>>> > > >>>> On Thu, Aug 24, 2017 at 7:50 PM, Ratnesh Upadhyay < > > >>>> upadhyay.ratn...@gmail.com> wrote: > > >>>> > > >>>> Hello Devs, > > >>>>> > > >>>>> I just walked though from OrderHeader entity and noticed that we > have > > >>>>> webSiteId field there but we don't have any FK constraint for it > from > > >>>>> OrderHeader.webSiteId to WebSite.webSiteId. I was expecting that it > > >>>>> > > >>>> must be > > >>>> > > >>>>> there. > > >>>>> > > >>>>> So just curious to know why it was not there, was it intentional? > > >>>>> Please > > >>>>> let me know if anyone have any information on it else I would > > provide a > > >>>>> patch to get it fixed. > > >>>>> > > >>>>> Thanks!! > > >>>>> > > >>>>> Regards, > > >>>>> Ratnesh Upadhyay > > >>>>> HotWax Systems | www.hotwaxsystems.com > > >>>>> > > >>>>> > > > > > >
Re: OrderHeader And WebSite Relationship
Thanks everyone for your inputs. I'll add record for "OrderEntry" website and relationship. @Jacques, I reviewed the usage of OrderTestData.xml and found that it's using by test-suite "ordertests" and I think it will work as we have entry for this suite in order/ofbiz-component.xml. Regards, Ratnesh Upadhyay HotWax Systems | www.hotwaxsystems.com On Sun, Aug 27, 2017 at 12:24 AM, Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > Hi Ratnesh, > > About 1 and 2, in such cases I always try to find the roots. > > 1. It's https://issues.apache.org/jira/browse/OFBIZ-290 look for > webSiteId,OrderEntry > 2. http://svn.apache.org/viewvc?view=revision&revision=1128984 > > Unfortunately seems that this not add much. I also wonder if the data in > OrderTestData.xml are ever used (else tests would fail, right?) > > Anyway, I agree with your conclusion. > > My 2cts > > Jacques > > > > Le 26/08/2017 à 14:48, Ratnesh Upadhyay a écrit : > >> Devs, >> >> I've noticed few things that needs to be discussed : >> >> 1. We have few order in DemoOrderTestData.xml and OrderTestData.xml that >> are having webSiteId="OrderEntry" but we don't have any record in WebSite >> entity for "OrderEntry" webSiteId. >> 2. We have "setCustRequestStatus" and "setCustRequestStatus" ecas where we >> are having following condition : >> >> Although we don't have this webSite record in entity then these ecas are >> no >> more of use as system never meet this condition. >> 3. There is no "webSiteId" is being set for orders placed from ordermgr >> application, so IMO we should setup webSiteId parameter in servletConetext >> of ordermgr app to get it setup. I can see its usage to get the >> information >> of orders placed from store front as well as from backend application. >> >> To apply FK constraint either we have to add record in WebSite entity or >> remove the references of "OrderEntry" webSiteId from order demo data. Also >> please let me know your thoughts to set webSiteId for backend apps. >> >> IMO, we should add record in WebSite entity for "OrderEntry". >> >> Thanks!! >> >> Regards, >> Ratnesh Upadhyay >> HotWax Systems | www.hotwaxsystems.com >> >> >> >> >> >> On Sat, Aug 26, 2017 at 1:08 PM, Ratnesh Upadhyay < >> upadhyay.ratn...@gmail.com> wrote: >> >> Thanks everyone for your inputs. >>> Here is the jira ticket : https://issues.apache.org/jira >>> /browse/OFBIZ-9647 >>> >>> Regards, >>> Ratnesh Upadhyay >>> HotWax System | www.hotwaxsystems.com >>> >>> >>> On Sat, Aug 26, 2017 at 11:54 AM, Arun Patidar < >>> arun.pati...@hotwaxsystems.com> wrote: >>> >>> Nice catch Ratnesh, we can take this as an improvement. >>>> >>>> >>>> >>>> -- >>>> Thanks & Regards >>>> --- >>>> Arun Patidar >>>> Manager, Enterprise Software Development >>>> >>>> >>>> HotWax Systems Pvt Ltd.www.hotwaxsystems.com >>>> >>>> >>>> On Thu, Aug 24, 2017 at 7:50 PM, Ratnesh Upadhyay < >>>> upadhyay.ratn...@gmail.com> wrote: >>>> >>>> Hello Devs, >>>>> >>>>> I just walked though from OrderHeader entity and noticed that we have >>>>> webSiteId field there but we don't have any FK constraint for it from >>>>> OrderHeader.webSiteId to WebSite.webSiteId. I was expecting that it >>>>> >>>> must be >>>> >>>>> there. >>>>> >>>>> So just curious to know why it was not there, was it intentional? >>>>> Please >>>>> let me know if anyone have any information on it else I would provide a >>>>> patch to get it fixed. >>>>> >>>>> Thanks!! >>>>> >>>>> Regards, >>>>> Ratnesh Upadhyay >>>>> HotWax Systems | www.hotwaxsystems.com >>>>> >>>>> >
Re: [PROPOSAL] Short Messaging Service(SMS) Gateway Integration
+1 good idea. Regards, Ratnesh Upadhyay HotWax Systems | www.hotwaxsystems.com On Sat, Aug 26, 2017 at 5:01 PM, Pritam Kute wrote: > Hi Devs, > > Many e-commerce businesses (especially operating in Asian countries) > nowadays use short messaging service (SMS) in mobile phones to notify and > update customers about order details, shipment statuses etc. > > I would like to propose an SMS Gateway Integration in Ofbiz. I will share > proposed design details with you all soon. Till then, I would like to know > your thoughts on this idea. > > Thanks and Regards > -- > Pritam Kute >
Re: OrderHeader And WebSite Relationship
Devs, I've noticed few things that needs to be discussed : 1. We have few order in DemoOrderTestData.xml and OrderTestData.xml that are having webSiteId="OrderEntry" but we don't have any record in WebSite entity for "OrderEntry" webSiteId. 2. We have "setCustRequestStatus" and "setCustRequestStatus" ecas where we are having following condition : Although we don't have this webSite record in entity then these ecas are no more of use as system never meet this condition. 3. There is no "webSiteId" is being set for orders placed from ordermgr application, so IMO we should setup webSiteId parameter in servletConetext of ordermgr app to get it setup. I can see its usage to get the information of orders placed from store front as well as from backend application. To apply FK constraint either we have to add record in WebSite entity or remove the references of "OrderEntry" webSiteId from order demo data. Also please let me know your thoughts to set webSiteId for backend apps. IMO, we should add record in WebSite entity for "OrderEntry". Thanks!! Regards, Ratnesh Upadhyay HotWax Systems | www.hotwaxsystems.com On Sat, Aug 26, 2017 at 1:08 PM, Ratnesh Upadhyay < upadhyay.ratn...@gmail.com> wrote: > Thanks everyone for your inputs. > Here is the jira ticket : https://issues.apache.org/jira/browse/OFBIZ-9647 > > Regards, > Ratnesh Upadhyay > HotWax System | www.hotwaxsystems.com > > > On Sat, Aug 26, 2017 at 11:54 AM, Arun Patidar < > arun.pati...@hotwaxsystems.com> wrote: > >> Nice catch Ratnesh, we can take this as an improvement. >> >> >> >> -- >> Thanks & Regards >> --- >> Arun Patidar >> Manager, Enterprise Software Development >> >> >> HotWax Systems Pvt Ltd.www.hotwaxsystems.com >> >> >> On Thu, Aug 24, 2017 at 7:50 PM, Ratnesh Upadhyay < >> upadhyay.ratn...@gmail.com> wrote: >> >> > Hello Devs, >> > >> > I just walked though from OrderHeader entity and noticed that we have >> > webSiteId field there but we don't have any FK constraint for it from >> > OrderHeader.webSiteId to WebSite.webSiteId. I was expecting that it >> must be >> > there. >> > >> > So just curious to know why it was not there, was it intentional? Please >> > let me know if anyone have any information on it else I would provide a >> > patch to get it fixed. >> > >> > Thanks!! >> > >> > Regards, >> > Ratnesh Upadhyay >> > HotWax Systems | www.hotwaxsystems.com >> > >> >
Re: OrderHeader And WebSite Relationship
Thanks everyone for your inputs. Here is the jira ticket : https://issues.apache.org/jira/browse/OFBIZ-9647 Regards, Ratnesh Upadhyay HotWax System | www.hotwaxsystems.com On Sat, Aug 26, 2017 at 11:54 AM, Arun Patidar < arun.pati...@hotwaxsystems.com> wrote: > Nice catch Ratnesh, we can take this as an improvement. > > > > -- > Thanks & Regards > --- > Arun Patidar > Manager, Enterprise Software Development > > > HotWax Systems Pvt Ltd.www.hotwaxsystems.com > > > On Thu, Aug 24, 2017 at 7:50 PM, Ratnesh Upadhyay < > upadhyay.ratn...@gmail.com> wrote: > > > Hello Devs, > > > > I just walked though from OrderHeader entity and noticed that we have > > webSiteId field there but we don't have any FK constraint for it from > > OrderHeader.webSiteId to WebSite.webSiteId. I was expecting that it must > be > > there. > > > > So just curious to know why it was not there, was it intentional? Please > > let me know if anyone have any information on it else I would provide a > > patch to get it fixed. > > > > Thanks!! > > > > Regards, > > Ratnesh Upadhyay > > HotWax Systems | www.hotwaxsystems.com > > >
Re: Running my first application in ofbiz
Please ask such type of questions on user list. Please refer : https://ofbiz.apache.org/mailing-lists.html Regards, Ratnesh Upadhyay On 24-Aug-2017 8:42 PM, "Vivek" wrote: Hello Devs, I just started OFBIZ. i am going through this link .. https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+ Tutorial+-+A+Beginners+Development+Guide#OFBizTutorial-ABegi nnersDevelopmentGuide-CreateYourFirstApplication(HelloWorld...) Create Your First Application (Hello World...) i have complete 1st step . at 2nd Now you will need to restart OFBiz by reloading data($ ./ant load-demo start). It's required as you have created a new component with some security data for you component (Setup by default in your component data directory as OfbizDemoSecurityGroupDemoData.xml) and as you will restart it, ofbizdemo component will also be loaded. i have problem in that . want to know - How to (Setup by default in your component data directory as OfbizDemoSecurityGroupDemoData.xml) currently i am not able to view this link because i don't complete 2nd yet. http://localhost:8080/ofbizdemo ( cant view) Also - can i ask this type of query here? Thanks!!
OrderHeader And WebSite Relationship
Hello Devs, I just walked though from OrderHeader entity and noticed that we have webSiteId field there but we don't have any FK constraint for it from OrderHeader.webSiteId to WebSite.webSiteId. I was expecting that it must be there. So just curious to know why it was not there, was it intentional? Please let me know if anyone have any information on it else I would provide a patch to get it fixed. Thanks!! Regards, Ratnesh Upadhyay HotWax Systems | www.hotwaxsystems.com
Re: Inconsistent String Comparisons
+1 for the initiation, also we can enforce it as best practice for future
implementations and patches.
Thanks!!
Regards,
Ratnesh Upadhyay
HotWax Systems
www.hotwaxsystems.com
On Mon, Jan 9, 2017 at 2:52 PM, Devanshu Vyas
wrote:
> Hello Devs,
>
> I found an inconsistency in the code for string comparison
> *statusId.equals("PRUN_COMPLETED")* whereas it should be written as
> *"PRUN_COMPLETED".equals(statusId)*
> cause the former can throw NullPointerException if the variable found to be
> NULL.
>
> This code pattern can be found at several places and if you all agree with
> this I can provide a patch for correcting code.
>
> Let me know your thoughts.
>
> Thanks & Regards,
> Devanshu Vyas.
>
--
--
--------
Cheers,
Thanks and Regards,
Ratnesh Upadhyay
Senior Business Analyst (Enterprise Software Solutions)
HotWax Media, Inc.
http://www.hotwaxmedia.com
E-mail : ratnesh.upadh...@hotwaxmedia.com
Mobile : +919826886909
Re: Welcome Swapnil Shah as a New Committer!
Many Congratulations Swapnil. Regards, Ratnesh Upadhyay On Tue, Feb 14, 2017 at 4:30 PM, Sharan Foga wrote: > The OFBiz PMC has invited Swapnil Shah to become a new committer and are > happy to announce that he has accepted. > > Swapnil has been involved in OFBiz for a few years and has been active on > both the development and user mailing lists responding to some quite > technical functional questions. > > Some of the key factors considered for inviting him were as follows: > > - He has very good functional knowledge about OFBiz and this is a valuable > skill that is useful to developers and users > - He is polite, positive, friendly and collaborative when dealing the > community discussions on the mailings lists or Jira > - He has raised Jiras, performed testing on patches and new other > functionality > - The PMC would like to see a wide range of people from the community > (developers and non-developers) recognised for their contributions to the > project. > > Please join me in welcoming and congratulating Swapnil. > > Thanks > Sharan > -- -- -------- Cheers, Thanks and Regards, Ratnesh Upadhyay Senior Business Analyst (Enterprise Software Solutions) HotWax Media, Inc. http://www.hotwaxmedia.com E-mail : ratnesh.upadh...@hotwaxmedia.com Mobile : +919826886909
[jira] [Created] (OFBIZ-7739) OFBIZ-7471: Improve all the service level error messages for missing required field for catalog component
Ratnesh Upadhyay created OFBIZ-7739: --- Summary: OFBIZ-7471: Improve all the service level error messages for missing required field for catalog component Key: OFBIZ-7739 URL: https://issues.apache.org/jira/browse/OFBIZ-7739 Project: OFBiz Issue Type: Sub-task Components: product Affects Versions: Upcoming Branch Reporter: Ratnesh Upadhyay Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7737) OFBIZ-7471: Improve all the service level error messages for missing required field for accounting component
Ratnesh Upadhyay created OFBIZ-7737: --- Summary: OFBIZ-7471: Improve all the service level error messages for missing required field for accounting component Key: OFBIZ-7737 URL: https://issues.apache.org/jira/browse/OFBIZ-7737 Project: OFBiz Issue Type: Sub-task Components: accounting Affects Versions: Upcoming Branch Reporter: Ratnesh Upadhyay Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7738) OFBIZ-7471: Improve all the service level error messages for missing required field for workeffort component
Ratnesh Upadhyay created OFBIZ-7738: --- Summary: OFBIZ-7471: Improve all the service level error messages for missing required field for workeffort component Key: OFBIZ-7738 URL: https://issues.apache.org/jira/browse/OFBIZ-7738 Project: OFBiz Issue Type: Sub-task Components: workeffort Affects Versions: Upcoming Branch Reporter: Ratnesh Upadhyay Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7736) OFBIZ-7471: Improve all the service level error messages for missing required field for order component
Ratnesh Upadhyay created OFBIZ-7736: --- Summary: OFBIZ-7471: Improve all the service level error messages for missing required field for order component Key: OFBIZ-7736 URL: https://issues.apache.org/jira/browse/OFBIZ-7736 Project: OFBiz Issue Type: Sub-task Components: order Affects Versions: Upcoming Branch Reporter: Ratnesh Upadhyay Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7735) OFBIZ-7471: Improve all the service level error messages for missing required field for party component
Ratnesh Upadhyay created OFBIZ-7735: --- Summary: OFBIZ-7471: Improve all the service level error messages for missing required field for party component Key: OFBIZ-7735 URL: https://issues.apache.org/jira/browse/OFBIZ-7735 Project: OFBiz Issue Type: Sub-task Components: party Affects Versions: Upcoming Branch Reporter: Ratnesh Upadhyay Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7667) Framework/Webtools: Correct all the checkboxes and radio buttons in all the webtools FTLs.
[ https://issues.apache.org/jira/browse/OFBIZ-7667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay updated OFBIZ-7667: Attachment: OFBIZ-7667.patch Thanks [~Mohammad K] for reporting the patch. Please see attached patch to fix checkbox and radio buttons for webtools. > Framework/Webtools: Correct all the checkboxes and radio buttons in all the > webtools FTLs. > -- > > Key: OFBIZ-7667 > URL: https://issues.apache.org/jira/browse/OFBIZ-7667 > Project: OFBiz > Issue Type: Sub-task > Components: ALL APPLICATIONS >Affects Versions: Upcoming Branch >Reporter: Mohammad Kathawala >Assignee: Mohammad Kathawala >Priority: Minor > Attachments: OFBIZ-7667.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7651) OFBIZ-7649: Display From date with default now() on all screens under Party Application
[ https://issues.apache.org/jira/browse/OFBIZ-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay updated OFBIZ-7651: Attachment: OFBIZ-7651.patch Thanks [~swash78] for reporting the issue. Attaching patch to fix reported issue for party application. > OFBIZ-7649: Display From date with default now() on all screens under Party > Application > --- > > Key: OFBIZ-7651 > URL: https://issues.apache.org/jira/browse/OFBIZ-7651 > Project: OFBiz > Issue Type: Sub-task > Components: party >Affects Versions: 14.12.01, 15.12.01 >Reporter: Swapnil Shah >Priority: Minor > Attachments: OFBIZ-7651.patch > > > To begin with let's start fixing it under > # "Add Party Content" form on > https://ofbiz-vm.apache.org:18443/partymgr/control/EditPartyContents?partyId=DemoCustCompany > # "Edit Product Store Roles" from on > https://ofbiz-vm.apache.org:18443/partymgr/control/ViewProductStoreRoles?partyId=DemoCustCompany -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Track user for status change
+1 for logical thinking and proposed enhancement. Regards, Ratnesh Upadhyay On Fri, Jun 24, 2016 at 6:56 PM, Nameet Jain wrote: > Hello everyone, > > Currently in OFBiz, 'changedByUserLoginId' field is missing from status > entities (like: ShipmentStatus). Using this field we can maintain the > history for each status change made by user. > > I will recommend here to add 'changedByUserLoginId' field to track the > userlogin detail. Here is the list of entities with missing such type of > field. > > 1. BudgetStatus > 2. ContactListCommStatus > 3. CustRequestStatus > 4. ExampleStatus > 5. FinAccountStatus > 6. InventoryItemStatus > 7. InvoiceStatus > 8. PartyStatus > 9. RequirementStatus > 10. ShipmentStatus > > Please let me know your thoughts. If it looks good I will open a ticket for > the same. > > Thanks > > -- > Regards, > Nameet Jain
Re: Use of utility method for checking null GenericValue
Thanks everyone for your valuable inputs on it. I'll create logical sub tickets to establish this practice in OFBiz. Regards, Ratnesh Upadhyay HotWax Systems | www.hotwaxsystems.com On Mon, Jun 20, 2016 at 3:04 PM, Scott Gray wrote: > +1, good idea thanks Ratnesh > > Regards > Scott > > On 18 June 2016 at 02:30, Ratnesh Upadhyay > wrote: > > > Hello community, > > > > There are lots of places in code where we have used > > UtilValidate.isNotEmpty() or UtilValidate.isEmpty() for GenericValue > object > > . GenericValue is never empty. Its always null or not null. So should we > > use directly null or not null check instead of UtilValidate.isNotEmpty() > > and UtilValidate.isEmpty() for GenericValue objects ? > > > > Basically these validation methods should preferably be used on Strings > or > > Lists and normal Maps. > > > > Thanks!! > > > > Regards, > > Ratnesh Upadhyay > > HotWax Systems | www.hotwaxsystems.com > > >
[jira] [Created] (OFBIZ-7517) Checkbox and Radio buttons should get selected on clicking upon their labels.
Ratnesh Upadhyay created OFBIZ-7517: --- Summary: Checkbox and Radio buttons should get selected on clicking upon their labels. Key: OFBIZ-7517 URL: https://issues.apache.org/jira/browse/OFBIZ-7517 Project: OFBiz Issue Type: Improvement Components: ALL APPLICATIONS Affects Versions: Upcoming Branch Reporter: Ratnesh Upadhyay This is a placeholder ticket to change the interaction of check box and radio button. We will create application wise sub task. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7471) Improve all the service level error messages for missing required field
[
https://issues.apache.org/jira/browse/OFBIZ-7471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15337924#comment-15337924
]
Ratnesh Upadhyay commented on OFBIZ-7471:
-
Thanks Deepak, Your suggestion is same as solution I planned for this ticket.
;-)
> Improve all the service level error messages for missing required field
> ---
>
> Key: OFBIZ-7471
> URL: https://issues.apache.org/jira/browse/OFBIZ-7471
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL COMPONENTS
>Affects Versions: Upcoming Branch
>Reporter: Ratnesh Upadhyay
> Attachments: ErrorMsgReturnedByServiceEngine.png, ImprovedUFMsgs.png
>
>
> Currently when a user submits a form with missing required fields, for
> instance creating a contactMech (Postal Address) from party profile screen.
> Here, in such scenarios the service engine returns missing field error
> message as:
> {code}
> The Following Errors Occurred:
> The following required parameter is missing:
> [createPartyPostalAddress.city]
> The following required parameter is missing:
> [createPartyPostalAddress.address1]
> The following required parameter is missing:
> [createPartyPostalAddress.postalCode]
> {code}
> Such error messages can be improved across the application by making it more
> user friendly like:
> {code}
> Required Field Missing : Address Line 1.
> Required Field Missing : City.
> Required Field Missing : Postal Code.
> {code}
> I'll review similar scenarios across the application.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OFBIZ-7471) Improve all the service level error messages for missing required field
[
https://issues.apache.org/jira/browse/OFBIZ-7471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ratnesh Upadhyay updated OFBIZ-7471:
Attachment: ErrorMsgReturnedByServiceEngine.png
> Improve all the service level error messages for missing required field
> ---
>
> Key: OFBIZ-7471
> URL: https://issues.apache.org/jira/browse/OFBIZ-7471
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL COMPONENTS
>Affects Versions: Upcoming Branch
>Reporter: Ratnesh Upadhyay
> Attachments: ErrorMsgReturnedByServiceEngine.png, ImprovedUFMsgs.png
>
>
> Currently when a user submits a form with missing required fields, for
> instance creating a contactMech (Postal Address) from party profile screen.
> Here, in such scenarios the service engine returns missing field error
> message as:
> {code}
> The Following Errors Occurred:
> The following required parameter is missing:
> [createPartyPostalAddress.city]
> The following required parameter is missing:
> [createPartyPostalAddress.address1]
> The following required parameter is missing:
> [createPartyPostalAddress.postalCode]
> {code}
> Such error messages can be improved across the application by making it more
> user friendly like:
> {code}
> Required Field Missing : Address Line 1.
> Required Field Missing : City.
> Required Field Missing : Postal Code.
> {code}
> I'll review similar scenarios across the application.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OFBIZ-7471) Improve all the service level error messages for missing required field
[
https://issues.apache.org/jira/browse/OFBIZ-7471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ratnesh Upadhyay updated OFBIZ-7471:
Attachment: ImprovedUFMsgs.png
> Improve all the service level error messages for missing required field
> ---
>
> Key: OFBIZ-7471
> URL: https://issues.apache.org/jira/browse/OFBIZ-7471
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL COMPONENTS
>Affects Versions: Upcoming Branch
>Reporter: Ratnesh Upadhyay
> Attachments: ImprovedUFMsgs.png
>
>
> Currently when a user submits a form with missing required fields, for
> instance creating a contactMech (Postal Address) from party profile screen.
> Here, in such scenarios the service engine returns missing field error
> message as:
> {code}
> The Following Errors Occurred:
> The following required parameter is missing:
> [createPartyPostalAddress.city]
> The following required parameter is missing:
> [createPartyPostalAddress.address1]
> The following required parameter is missing:
> [createPartyPostalAddress.postalCode]
> {code}
> Such error messages can be improved across the application by making it more
> user friendly like:
> {code}
> Required Field Missing : Address Line 1.
> Required Field Missing : City.
> Required Field Missing : Postal Code.
> {code}
> I'll review similar scenarios across the application.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (OFBIZ-7471) Improve all the service level error messages for missing required field
Ratnesh Upadhyay created OFBIZ-7471:
---
Summary: Improve all the service level error messages for missing
required field
Key: OFBIZ-7471
URL: https://issues.apache.org/jira/browse/OFBIZ-7471
Project: OFBiz
Issue Type: Improvement
Components: ALL COMPONENTS
Affects Versions: Upcoming Branch
Reporter: Ratnesh Upadhyay
Currently when a user submits a form with missing required fields, for instance
creating a contactMech (Postal Address) from party profile screen.
Here, in such scenarios the service engine returns missing field error message
as:
{code}
The Following Errors Occurred:
The following required parameter is missing:
[createPartyPostalAddress.city]
The following required parameter is missing:
[createPartyPostalAddress.address1]
The following required parameter is missing:
[createPartyPostalAddress.postalCode]
{code}
Such error messages can be improved across the application by making it more
user friendly like:
{code}
Required Field Missing : Address Line 1.
Required Field Missing : City.
Required Field Missing : Postal Code.
{code}
I'll review similar scenarios across the application.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Use of utility method for checking null GenericValue
Hello community, There are lots of places in code where we have used UtilValidate.isNotEmpty() or UtilValidate.isEmpty() for GenericValue object . GenericValue is never empty. Its always null or not null. So should we use directly null or not null check instead of UtilValidate.isNotEmpty() and UtilValidate.isEmpty() for GenericValue objects ? Basically these validation methods should preferably be used on Strings or Lists and normal Maps. Thanks!! Regards, Ratnesh Upadhyay HotWax Systems | www.hotwaxsystems.com
[jira] [Updated] (OFBIZ-7190) Multiple ship group qty are not allowed to cancel
[ https://issues.apache.org/jira/browse/OFBIZ-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay updated OFBIZ-7190: Attachment: CancelQtyShipGrp.png MultipleShipGrpCancellation.png > Multiple ship group qty are not allowed to cancel > - > > Key: OFBIZ-7190 > URL: https://issues.apache.org/jira/browse/OFBIZ-7190 > Project: OFBiz > Issue Type: Bug > Reporter: Ratnesh Upadhyay > Attachments: CancelQtyShipGrp.png, MultipleShipGrpCancellation.png > > > Order item split in multiple ship group qty are not allowed to cancel in > sales order workflow. Please refer to attach screenshot for more details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7190) Multiple ship group qty are not allowed to cancel
Ratnesh Upadhyay created OFBIZ-7190: --- Summary: Multiple ship group qty are not allowed to cancel Key: OFBIZ-7190 URL: https://issues.apache.org/jira/browse/OFBIZ-7190 Project: OFBiz Issue Type: Bug Reporter: Ratnesh Upadhyay Order item split in multiple ship group qty are not allowed to cancel in sales order workflow. Please refer to attach screenshot for more details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7180) Completed Service Order Items are being allowed to be edited over Approved PO
[ https://issues.apache.org/jira/browse/OFBIZ-7180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay updated OFBIZ-7180: Attachment: OFBIZ-7180.patch Swapnil thanks for reporting the issue. Please see attached patch to fix the issue. We have now prevented any completed and cancelled items being edited and validated the same. > Completed Service Order Items are being allowed to be edited over Approved PO > -- > > Key: OFBIZ-7180 > URL: https://issues.apache.org/jira/browse/OFBIZ-7180 > Project: OFBiz > Issue Type: Bug >Reporter: Swapnil Shah >Assignee: Divesh Dutta >Priority: Critical > Attachments: OFBIZ-7180.patch, SV_1.png, SV_2.png, SV_3.png > > > Currently PO line items having service type products are completed on > Approval itself. But system still allows the Completed service items to be > edited over any Approved PO (e.g. if PO has both service and finished good > items that still need to be received). This lead to difference in invoice and > order valuation. > We could possibly restrict the editing for any completed order items via Edit > Items option over Order view. > Please refer to attached screenshot for reference -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7087) Material/Component requirement is not available for 'Confirmed' Production Runs
[ https://issues.apache.org/jira/browse/OFBIZ-7087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay updated OFBIZ-7087: Attachment: MaterialScreenOnConfirmedStatus.png OFBIZ-7087.patch Thanks Swapnil for suggesting the improvement. Attaching patch to fix reported issue. After applying this patch material screen started appearing for confirmed production run as well. Also attaching screen shot for quick verification and reference. > Material/Component requirement is not available for 'Confirmed' Production > Runs > --- > > Key: OFBIZ-7087 > URL: https://issues.apache.org/jira/browse/OFBIZ-7087 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing >Reporter: Swapnil Shah > Attachments: Confirmed_PR_1.png, MaterialScreenOnConfirmedStatus.png, > OFBIZ-7087.patch, Unconfirmed_PR_1.png > > > All the material/component requirements are rightly visible as soon as any > production run gets created but once its Confirmed then there is no way to > see the specific material/components that are required for any task from any > tab/screen against the given production run (even its not listed on Actual > Material screen) > To begin with, let's add back the same 'Material' section (as visible for any > Created/Scheduled production runs) just below the production run task section > listing task-wise component requirement along with respective quantity -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7102) Fix the Approve button label for newly added item to the existing PO
[ https://issues.apache.org/jira/browse/OFBIZ-7102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15294987#comment-15294987 ] Ratnesh Upadhyay commented on OFBIZ-7102: - Pierre, there is no functional changes required to fix this issue. UI label needs to be change from "Approve Order" to "Approve Item" which is misleading the user. > Fix the Approve button label for newly added item to the existing PO > > > Key: OFBIZ-7102 > URL: https://issues.apache.org/jira/browse/OFBIZ-7102 > Project: OFBiz > Issue Type: Improvement > Components: order >Reporter: Ratnesh Upadhyay >Priority: Minor > Attachments: ApproveButtonLabel.png > > > Upon Adding new item to existing approved purchase order creates a new line > item to the existing order in CREATED state but it shows the button label as > 'APPROVE ORDER' instead of 'APPROVE ITEM'. > Please refer to attached screenshot for more details -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7102) Fix the Approve button label for newly added item to the existing PO
[ https://issues.apache.org/jira/browse/OFBIZ-7102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay updated OFBIZ-7102: Attachment: ApproveButtonLabel.png > Fix the Approve button label for newly added item to the existing PO > > > Key: OFBIZ-7102 > URL: https://issues.apache.org/jira/browse/OFBIZ-7102 > Project: OFBiz > Issue Type: Improvement > Components: order > Reporter: Ratnesh Upadhyay >Priority: Minor > Attachments: ApproveButtonLabel.png > > > Upon Adding new item to existing approved purchase order creates a new line > item to the existing order in CREATED state but it shows the button label as > 'APPROVE ORDER' instead of 'APPROVE ITEM'. > Please refer to attached screenshot for more details -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7102) Fix the Approve button label for newly added item to the existing PO
Ratnesh Upadhyay created OFBIZ-7102: --- Summary: Fix the Approve button label for newly added item to the existing PO Key: OFBIZ-7102 URL: https://issues.apache.org/jira/browse/OFBIZ-7102 Project: OFBiz Issue Type: Improvement Components: order Reporter: Ratnesh Upadhyay Priority: Minor Upon Adding new item to existing approved purchase order creates a new line item to the existing order in CREATED state but it shows the button label as 'APPROVE ORDER' instead of 'APPROVE ITEM'. Please refer to attached screenshot for more details -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6895) Product price rule with no conditions.
[
https://issues.apache.org/jira/browse/OFBIZ-6895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15294823#comment-15294823
]
Ratnesh Upadhyay commented on OFBIZ-6895:
-
@Jacques, I've reviewed issue details and it seems this is intended behavior of
system, if there is no condition available then apply action for all. In this
case merchandising manager should be smart enough to take this decision or
business can train him to use price rule in this way. We can't prevent user to
create such rules as many time business required to perform abc action without
any condition.
I think we can keep the functionality intact and instead we can train our staff
on workflow of OFBiz price rule workflow. Lets see what community think about
it.
> Product price rule with no conditions.
> ---
>
> Key: OFBIZ-6895
> URL: https://issues.apache.org/jira/browse/OFBIZ-6895
> Project: OFBiz
> Issue Type: Improvement
> Components: product
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
> Fix For: Upcoming Branch
>
>
> I'm currently closing pending stuff, here is one
> Skip reported this 2 years ago on user ML:
> {quote}
> I recently had a user accidentially create a product price rule with no
> conditions. This resulted in all products sold afterwards getting the
> discounted price (-5% price) set by the action.
> After tracking this down, I added some code in PriceServices.java to check
> if there were no price conditions and if so, set the local variable alltrue
> to false. This fixes it for me.
> I am debating whether or not to add a Jira for this issue. Was this
> intended and can anyone see any value in this behavior?
> Skip
> {quote}
> I then answered
> {quote}
> I'd create a Jira. It looks like a miss to me, the check you do seems good.
> I'd
> also prevent users to create such rules from UI
> Maybe we could add a properties, in case someone would like to use a such
> scenario (could be used for temporarily give a percent on all products)?
> {quote}
> Jacques
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-5878) Order Manager: when an item is cancelled, its fields should be deactivated
[
https://issues.apache.org/jira/browse/OFBIZ-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15103125#comment-15103125
]
Ratnesh Upadhyay edited comment on OFBIZ-5878 at 1/16/16 11:35 AM:
---
Thanks Jacques and Swapnil for the details. I've tried to replicate reported
issue over trunk, for sale order workflow but it seems the issue is no more
persist there, may be got fixed under OFBIZ-4954 , I think we can proceed to
close this ticket.
was (Author: upadhyay.ratnesh):
Thanks Jacques and Swapnil for the details. I've tried to replicate reported
issue over trunk, for sale order workflow but it seems it's no more persist
there, may be got fixed under OFBIZ-4954 , I think we can proceed to close this
ticket.
> Order Manager: when an item is cancelled, its fields should be deactivated
> --
>
> Key: OFBIZ-5878
> URL: https://issues.apache.org/jira/browse/OFBIZ-5878
> Project: OFBiz
> Issue Type: Improvement
> Components: order
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Priority: Trivial
>
> This has been 1st reported at OFBIZ-5808, quoting mysef:
> {quote}
> A cancelled item still shows a input to change its price and another for the
> quantity (set to 0). They both don't make any sense ...
> {quote}
> Ingo added:
> {quote}
> They do not have any function as they are completely ignored in code.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-5878) Order Manager: when an item is cancelled, its fields should be deactivated
[
https://issues.apache.org/jira/browse/OFBIZ-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15103125#comment-15103125
]
Ratnesh Upadhyay commented on OFBIZ-5878:
-
Thanks Jacques and Swapnil for the details. I've tried to replicate reported
issue over trunk, for sale order workflow but it seems it's no more persist
there, may be got fixed under OFBIZ-4954 , I think we can proceed to close this
ticket.
> Order Manager: when an item is cancelled, its fields should be deactivated
> --
>
> Key: OFBIZ-5878
> URL: https://issues.apache.org/jira/browse/OFBIZ-5878
> Project: OFBiz
> Issue Type: Improvement
> Components: order
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Priority: Trivial
>
> This has been 1st reported at OFBIZ-5808, quoting mysef:
> {quote}
> A cancelled item still shows a input to change its price and another for the
> quantity (set to 0). They both don't make any sense ...
> {quote}
> Ingo added:
> {quote}
> They do not have any function as they are completely ignored in code.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OFBIZ-817) Require Inventory of Marketing Package Product can't be shipped
[ https://issues.apache.org/jira/browse/OFBIZ-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay updated OFBIZ-817: --- Attachment: OFBIZ-817.patch Attaching patch to fix this issue. Patch is supplied from Ankush Upadhyay. > Require Inventory of Marketing Package Product can't be shipped > --- > > Key: OFBIZ-817 > URL: https://issues.apache.org/jira/browse/OFBIZ-817 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk > Environment: February 2007 svn >Reporter: Daniel Kunkel >Priority: Minor > Attachments: OFBIZ-817.patch > > > Setting Require Inventory for a Marketing Product and (or ???) its Marketing > Component causes the shiping system to fail. The shipping system reports > nothing is ready to ship, ( [0 + 0 = 0] < 1 ). > exception report > -- > [TransactionUtil.setRollbackOnly] Calling transaction setRollbackOnly; this > stack trace shows where this is happening: > Exception: java.lang.Exception > Message: Error in simple-method [Quick ships an entire order from multiple > facilities [file:/wrk/ofbiz/ofbiz/applications/ > product/script/org/ofbiz/shipment/shipment/ShipmentServices.xml#quickShipEntireOrder]]: > ; [Warning: no shipments created; > could not find anything ready and needing to be shipped.] > stack trace > --- > java.lang.Exception: Error in simple-method [Quick ships an entire order from > multiple facilities [file:/wrk/ofbiz/ofbiz/ > applications/product/script/org/ofbiz/shipment/shipment/ShipmentServices.xml#quickShipEntireOrder]]: > ; [Warning: no shipments > created; could not find anything ready and needing to be shipped.] > org.ofbiz.entity.transaction.TransactionUtil.setRollbackOnly(TransactionUtil.java:285) > org.ofbiz.entity.transaction.TransactionUtil.rollback(TransactionUtil.java:235) > org.ofbiz.minilang.SimpleMethod.exec(SimpleMethod.java:697) > org.ofbiz.minilang.SimpleMethod.runSimpleMethod(SimpleMethod.java:105) > org.ofbiz.minilang.SimpleMethod.runSimpleService(SimpleMethod.java:87) > org.ofbiz.minilang.SimpleServiceEngine.serviceInvoker(SimpleServiceEngine.java:76) > org.ofbiz.minilang.SimpleServiceEngine.runSync(SimpleServiceEngine.java:51) > org.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:340) > org.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:211) > org.ofbiz.service.GenericDispatcher.runSync(GenericDispatcher.java:113) > org.ofbiz.webapp.event.ServiceEventHandler.invoke(ServiceEventHandler.java:290) > org.ofbiz.webapp.control.RequestHandler.runEvent(RequestHandler.java:409) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5680) DataResource mapping to survey generates error
[ https://issues.apache.org/jira/browse/OFBIZ-5680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228701#comment-14228701 ] Ratnesh Upadhyay commented on OFBIZ-5680: - Hi All, We have reviewed reported issue and found that we don't have code support in OOTB to render SURVEY type data resource. So it is recommended to change type of this issue from bug to new feature or improvement to exclude it from bugs list. In meantime we will do some more research on it and share notes to add this support. Thanks!! > DataResource mapping to survey generates error > --- > > Key: OFBIZ-5680 > URL: https://issues.apache.org/jira/browse/OFBIZ-5680 > Project: OFBiz > Issue Type: Bug > Components: content, specialpurpose/cmssite >Affects Versions: Release Branch 12.04, Release Branch 13.07, Trunk >Reporter: Pierre Smits > > When creating a new DataResource record in content mgr with > dataResourceTypeId set to 'SURVEY' following error is thrown when accessing > it in cmssite: > Error calling event: org.ofbiz.webapp.event.EventHandlerException: Problems > processing event: org.ofbiz.base.util.GeneralRuntimeException: Error > rendering content: org.ofbiz.base.util.GeneralException: The > dataResourceTypeId [SURVEY] is not supported in renderDataResourceAsText (The > dataResourceTypeId [SURVEY] is not supported in renderDataResourceAsText) > (Error rendering content: org.ofbiz.base.util.GeneralException: The > dataResourceTypeId [SURVEY] is not supported in renderDataResourceAsText (The > dataResourceTypeId [SURVEY] is not supported in renderDataResourceAsText)) > I have the following : > # Content record: CMSS_SURVEY_DEMO, that points to: > # DataResource record CMSS_SURVEY_DEMO > The DataResource record has: > * dataResourceId = CMSS_SURVEY_DEMO > * dataResourceTypeId = SURVEY > * surveyId = 1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5283) Inventory report shows different counts after a warehouse transfer.
[ https://issues.apache.org/jira/browse/OFBIZ-5283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228669#comment-14228669 ] Ratnesh Upadhyay commented on OFBIZ-5283: - [~jacopoc] We have reviewed the reported issue and able to reproduce it thanks for sharing details. Apart from this we anlayzed further on it, sharing my notes here to get this issue into the next level: 1. Initial inventory for product id: GZ-2644 || ProductId || InventoryItemId || Facility || ATP || QOH || Comments || | GZ-2644 | 9000 | WebStoreWarehouse | 4 | 4 | Currently this is on bulk location. | 2. Locate this inventory item in facility and transfer 2 quantity to MyRetailstore facility, transfer is still in requested status, so now invenoty item looks like: || ProductId || InventoryItemId || Facility || ATP || QOH || Comments || | GZ-2644 | 9000 | WebStoreWarehouse | 2 | 2 | Currently this is on bulk location. | | GZ-2644 | 10020 | WebStoreWarehouse | 0 | 2 | Currently this is on bulk location. | At the same time system has created following records in inventory item details: || ProductId || InventoryItemId || QuantityOnHandDiff || AvailableToPromiseDiff || AccountingQuantityDiff || Comments || | GZ-2644 | 9000 | -2 | -2 | 0 | | | GZ-2644 | 10020 | 0 | 0 | 0 | | | GZ-2644 | 10020 | 2 | 2 | 0 | | | GZ-2644 | 10020 | 0 | -2 | 0 | | 3. Now changed transfer from requested to complete and now the invenotry recods are following: || ProductId || InventoryItemId || Facility || ATP || QOH || Comments || | GZ-2644 | 9000 | WebStoreWarehouse | 2 | 2 | Currently this is on bulk location. | | GZ-2644 | 10020 | MyRetailStore | 2 | 2 | System updated existing invenotry item and changed facility id and invenotry counts.| Inventorey items details records after completing transfer: || ProductId || InventoryItemId || QuantityOnHandDiff || AvailableToPromiseDiff || AccountingQuantityDiff || Comments || | GZ-2644 | 9000 | -2 | -2 | 0 | remains unchanged as it was earlier. | | GZ-2644 | 10020 | 0 | 0 | 0 | remains unchanged as it was earlier. | | GZ-2644 | 10020 | 2 | 2 | 0 | remains unchanged as it was earlier. | | GZ-2644 | 10020 | 0 | -2 | 0 | remains unchanged as it was earlier. | | GZ-2644 | 10020 | 0 | 2 | 0 | added during complete transfer process.| As we can this in this process no where accouting quantity diff is getting updated but the inventory valuation report is populating information based on acccounting quantity diff and its value grouped by facilityid and unit cost, so the transferred quantity is not reflecting in inventory valuation report. To fix this issue, we can add following inventory item details entries to balanced out transfered quantities in their original services. || ProductId || InventoryItemId || QuantityOnHandDiff || AvailableToPromiseDiff || AccountingQuantityDiff || Comments || | GZ-2644 | 9000 | -2| -2 | -2 | Added at the time of initiation of transfer. | | GZ-2644 | 10020 | 2 | 2 | 2 | Added at the time of initiation of transfer. | Please review these notes and provide your inputs. > Inventory report shows different counts after a warehouse transfer. > --- > > Key: OFBIZ-5283 > URL: https://issues.apache.org/jira/browse/OFBIZ-5283 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk >Reporter: Hans Bakker > Attachments: accounting.diff > > > A customer reported the following problem where the inventory report shows > different counts after a warehouse transfer. > Steps to replicate problem > 1. Choose Facility - Web Store Warehouse > 2. Select Inventory Items and filter by product id GZ-2644 > 3. You should see all the items for that product make a note of the Quantity > on Hand > 6. On any of the Product ID's GZ-2644 click Transfer(Right hand side of the > screen) > 7. Change the To Facility / Container to be My Retail Store > 8. Transfer only quantity of 1 > 9. Click on Complete Requested Transfer > 10. Select the item using the checkbox and click submit > 11. Repeat steps 2 to 3 - Taking note of the Quantity on Hand which should > have changed > Next > 1. Click on Accounting > 2. Click on Organization GL Settings > 3. Click Accounting for Your Company Name Here > 4. Click Reports > 5. Click Inventory Valuation > 6. Select Web Store Warehouse and click submit > 7. Note Quantities against GZ-2644 are the Accounting Quantity Total not the > Quantity on Hand. - -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] [RELEASE] Apache OFBiz 12.04.01
+1 Thanks!! Regards, Ratnesh Upadhyay Hotwax Media | www.hotwaxmedia.com On Tue, Mar 26, 2013 at 10:02 PM, Jacopo Cappellato < jacopo.cappell...@hotwaxmedia.com> wrote: > This is the vote thread to approve the first release for the 12.04 branch. > This new release, "Apache OFBiz 12.04.01" (major release number: "12.04"; > minor release number: "01") is the first release of the 12.04 series and > contains all the features of the trunk up to April 2012 and since then has > been stabilized with bug fixes. It will become the OFBiz current "stable" > release and users of the 11.04 series will be encouraged to migrate to this > release. > > The candidate release files can be downloaded from here: > > https://dist.apache.org/repos/dist/dev/ofbiz/ > > (committers only) or from here: > > http://people.apache.org/~jacopoc/dist/ > > (everyone else) > > and are: > > * apache-ofbiz-12.04.01.zip: the release package, based on the 12.04 > branch at revision 1461136 (latest as of now) > * KEYS: text file with keys > * apache-ofbiz-12.04.01.zip.asc: the detached signature file > * apache-ofbiz-12.04.01.zip.md5, apache-ofbiz-12.04.01.zip.sha: hashes > > Please download the zip file and check its signatures (for instructions on > testing the signatures see http://www.apache.org/info/verification.html), > then test the release. > > Vote: > > [ +1] release as Apache OFBiz 12.04.01 > [ -1] do not release > > This vote will be closed in Monday, 1st of April. > For more details about this process please read > http://www.apache.org/foundation/voting.html > > The following text is quoted from the above url: > "Votes on whether a package is ready to be released use majority approval > -- i.e. at least three PMC members must vote affirmatively for release, and > there must be more positive than negative votes. Releases may not be > vetoed. Generally the community will cancel the release vote if anyone > identifies serious problems, but in most cases the ultimate decision, lies > with the individual serving as release manager." > > Jacopo Cappellato > >
Re: [VOTE] [BRANCH] Creation of the Release Branch "release10.04"
+1 Regards, -- Ratnesh Upadhyay HotWax Media http://www.hotwaxmedia.com On Thu, Apr 29, 2010 at 12:35 PM, Vikas Mayur wrote: > +1 > > Regards > Vikas > > On Wed, Apr 28, 2010 at 1:40 PM, Jacopo Cappellato < > jacopo.cappell...@hotwaxmedia.com> wrote: > > > This is the vote thread to create a new release branch (not a release > yet) > > named "release10.04". > > This branch will represent a feature freeze and releases will be created > > over time out of it: all the commits in this branch will be for bug > fixes > > only, no new features. > > > > Vote: > > > > [ +1] create the branch "release10.04" > > [ -1] do not create the branch > > > > We will use the same rules for votes on releases (vote passes if there > are > > more binding +1 than -1 and if there are at least 3 binding +1) > > For more details about this process please read this > > http://www.apache.org/foundation/voting.html > > > > Kind Regards, > > > > Jacopo > > >
[jira] Created: (OFBIZ-3339) Enhance Find Billing Account Screen to follow standard Find/List screen pattern
Enhance Find Billing Account Screen to follow standard Find/List screen pattern --- Key: OFBIZ-3339 URL: https://issues.apache.org/jira/browse/OFBIZ-3339 Project: OFBiz Issue Type: Improvement Components: accounting Affects Versions: SVN trunk Reporter: Ratnesh Upadhyay Priority: Minor Fix For: SVN trunk Enhance https://demo.ofbiz.org/accounting/control/FindBillingAccount. Add Search form where user can enter search criteria. The screen should follow standard Find/List screen decorator. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Require Java 6
+1 Regards, - Ratnesh Upadhyay | HotWax Media http://www.hotwaxmedia.com On Tue, Dec 1, 2009 at 3:10 AM, David E Jones wrote: > > Please vote on whether or not we should require Java 6 (aka Java 1.6) for > OFBiz going forward. This basically means that we would allow code that > relies on Java 6 APIs, and that because of those OFBiz would no longer run > on Java 5 (aka Java 1.5). Note that this change would be for the trunk only > and would not apply to any release branch. > > [+1] Java 6 or later > [+0] Abstain > [-1] Continue to support Java 5 > >
[jira] Commented: (OFBIZ-3077) Error for productStoreId when click on productId link from showcart of purchase order
[ https://issues.apache.org/jira/browse/OFBIZ-3077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770010#action_12770010 ] Ratnesh Upadhyay commented on OFBIZ-3077: - Thanks Joe for your comment. Please let us know, if its all over from your side or do you have any specific notes for the same. Will help us to start work on it. -- Ratnesh Upadhyay > Error for productStoreId when click on productId link from showcart of > purchase order > - > > Key: OFBIZ-3077 > URL: https://issues.apache.org/jira/browse/OFBIZ-3077 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: SVN trunk >Reporter: Brajesh Patel > Fix For: SVN trunk > > > Steps regenerate error: > 1) Hit url: https://localhost:8443/ordermgr/control/orderentry > 2) Select purchase order with supplier > 3) Add product for order > 4) Click on the productId from showcart page > it will generate error as following > org.ofbiz.widget.screen.ScreenRenderException: Error rendering screen > [component://order/widget/ordermgr/OrderEntryCatalogScreens.xml#productdetail]: > java.lang.NullPointerException: Cannot get property 'productStoreId' on null > object (Cannot get property 'productStoreId' on null object) > Thanks Rishi, Mridul and Ratnesh for discussion. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-3079) NPE appears on create customer from order entry screens.
NPE appears on create customer from order entry screens. Key: OFBIZ-3079 URL: https://issues.apache.org/jira/browse/OFBIZ-3079 Project: OFBiz Issue Type: Bug Components: order Affects Versions: Release Branch 9.04, SVN trunk Reporter: Ratnesh Upadhyay Fix For: Release Branch 9.04, SVN trunk Got NPE, during create new customer from order entry screen. Steps to regenerate the error: 1). Browse following link : https://demo.ofbiz.org/ordermgr/control/orderentry , serve require inputs and click on continue link. 2). Now wait for some time on add item screen and click on create customer button available in shortcuts block. (shown in right bar) Note : It seems that, its a session issue, so some time it works fine but some time this screen is broken due to NPE. -- Ratnesh Upadhyay -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3039) Last inventory count field should not be editable.
[ https://issues.apache.org/jira/browse/OFBIZ-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay updated OFBIZ-3039: Attachment: OFBiz_3039.patch Patch to fix mentioned issue. - Ratnesh Upadhyay > Last inventory count field should not be editable. > -- > > Key: OFBIZ-3039 > URL: https://issues.apache.org/jira/browse/OFBIZ-3039 > Project: OFBiz > Issue Type: Bug > Components: product >Affects Versions: SVN trunk >Reporter: Ratnesh Upadhyay > Fix For: SVN trunk > > Attachments: OFBiz_3039.patch > > > Last inventory count field should not be editable, It will update > automatically by a schedule service. > Steps to reach the affected area : > 1. Go to catalog component. > 2. Insert product Id - GZ-2644 in text box available in search products > screen. > 3. Select Facilities in product jump drop down. > 4. System will redirect the user on edit product facility screen, where you > can find last inventory count field editable in Add and Edit product facility > form. > Note : "setLastInventoryCount" service is responsible to update it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-3039) Last inventory count field should not be editable.
Last inventory count field should not be editable. -- Key: OFBIZ-3039 URL: https://issues.apache.org/jira/browse/OFBIZ-3039 Project: OFBiz Issue Type: Bug Components: product Affects Versions: SVN trunk Reporter: Ratnesh Upadhyay Fix For: SVN trunk Last inventory count field should not be editable, It will update automatically by a schedule service. Steps to reach the affected area : 1. Go to catalog component. 2. Insert product Id - GZ-2644 in text box available in search products screen. 3. Select Facilities in product jump drop down. 4. System will redirect the user on edit product facility screen, where you can find last inventory count field editable in Add and Edit product facility form. Note : "setLastInventoryCount" service is responsible to update it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2918) Added Opening Balance field in Bank Reconciliation entity, Also added a calculated field (Closing Balance) on GlReconciliation Screen.
[ https://issues.apache.org/jira/browse/OFBIZ-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay updated OFBIZ-2918: Attachment: OFBiz-2918.patch Here is the patch to serve this functionality. Thanks Sumit and Chirag for discussion. Regards, -- Ratnesh Upadhyay > Added Opening Balance field in Bank Reconciliation entity, Also added a > calculated field (Closing Balance) on GlReconciliation Screen. > -- > > Key: OFBIZ-2918 > URL: https://issues.apache.org/jira/browse/OFBIZ-2918 > Project: OFBiz > Issue Type: New Feature > Components: accounting >Affects Versions: SVN trunk > Reporter: Ratnesh Upadhyay > Fix For: SVN trunk > > Attachments: OFBiz-2918.patch > > > Added Opening Balance field to GlReconciliation entity. In Bank > reconciliation process it allows user to edit value of this field. Once > reconciliation is completed this field shown as read only. Added calculated > field on GlReconcilation screen to show closing balance (opening balance + > reconciled amount + running total). Updated value of closing amount on change > of opening balance field and running total field. > Regards, > -- Ratnesh Upadhyay > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-2918) Added Opening Balance field in Bank Reconciliation entity, Also added a calculated field (Closing Balance) on GlReconciliation Screen.
Added Opening Balance field in Bank Reconciliation entity, Also added a calculated field (Closing Balance) on GlReconciliation Screen. -- Key: OFBIZ-2918 URL: https://issues.apache.org/jira/browse/OFBIZ-2918 Project: OFBiz Issue Type: New Feature Components: accounting Affects Versions: SVN trunk Reporter: Ratnesh Upadhyay Fix For: SVN trunk Added Opening Balance field to GlReconciliation entity. In Bank reconciliation process it allows user to edit value of this field. Once reconciliation is completed this field shown as read only. Added calculated field on GlReconcilation screen to show closing balance (opening balance + reconciled amount + running total). Updated value of closing amount on change of opening balance field and running total field. Regards, -- Ratnesh Upadhyay -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2914) Improved Inventory Average Cost Valuation Algorithm.
[ https://issues.apache.org/jira/browse/OFBIZ-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay updated OFBIZ-2914: Attachment: OFBiz-2914.patch Attached patch for improved algorithm. Thanks Sumit and Anil for discussion on it. I would like to give special Thanks to Eva for providing example process. Regards, -- Ratnesh Upadhyay > Improved Inventory Average Cost Valuation Algorithm. > > > Key: OFBIZ-2914 > URL: https://issues.apache.org/jira/browse/OFBIZ-2914 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: SVN trunk >Reporter: Ratnesh Upadhyay > Fix For: SVN trunk > > Attachments: OFBiz-2914.patch > > > Now this calculation will be done by following formula : ( (old average cost > * total old stock) + (new purchase price * new qty received) ) / (total old > stock + new qty received). > You can verify calculated result from Accounting > Organization GL Settings > > Reports > Inventory valuation report screen. > Regards, > -- Ratnesh Upadhyay -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-2914) Improved Inventory Average Cost Valuation Algorithm.
Improved Inventory Average Cost Valuation Algorithm. Key: OFBIZ-2914 URL: https://issues.apache.org/jira/browse/OFBIZ-2914 Project: OFBiz Issue Type: Improvement Components: accounting Affects Versions: SVN trunk Reporter: Ratnesh Upadhyay Fix For: SVN trunk Now this calculation will be done by following formula : ( (old average cost * total old stock) + (new purchase price * new qty received) ) / (total old stock + new qty received). You can verify calculated result from Accounting > Organization GL Settings > Reports > Inventory valuation report screen. Regards, -- Ratnesh Upadhyay -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2896) Added menus in AR and AP web applications to show payment groups of their specific type.
[ https://issues.apache.org/jira/browse/OFBIZ-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay updated OFBIZ-2896: Attachment: OFBiz-2896.patch Attached patch to serve mentioned functionality. Thanks! Regards, -- Ratnesh Upadhyay > Added menus in AR and AP web applications to show payment groups of their > specific type. > > > Key: OFBIZ-2896 > URL: https://issues.apache.org/jira/browse/OFBIZ-2896 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: SVN trunk > Reporter: Ratnesh Upadhyay >Priority: Minor > Fix For: SVN trunk > > Attachments: OFBiz-2896.patch > > > Implemented following functionalities in AR & AP web applications : > - Added a screen in AP to find and view Payment Group of type Check Run. > - Added a screen in AR to find and view Payment Group of type (Batch Payment) > Deposits to financial account. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-2896) Added menus in AR and AP web applications to show payment groups of their specific type.
Added menus in AR and AP web applications to show payment groups of their specific type. Key: OFBIZ-2896 URL: https://issues.apache.org/jira/browse/OFBIZ-2896 Project: OFBiz Issue Type: Improvement Components: accounting Affects Versions: SVN trunk Reporter: Ratnesh Upadhyay Priority: Minor Fix For: SVN trunk Implemented following functionalities in AR & AP web applications : - Added a screen in AP to find and view Payment Group of type Check Run. - Added a screen in AR to find and view Payment Group of type (Batch Payment) Deposits to financial account. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2893) Displayed gl account transactions for Bank Reconciliation.
[ https://issues.apache.org/jira/browse/OFBIZ-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay updated OFBIZ-2893: Attachment: ReconciliationScreen.png Attached the correct one. Regards, -- Ratnesh Upadhyay > Displayed gl account transactions for Bank Reconciliation. > -- > > Key: OFBIZ-2893 > URL: https://issues.apache.org/jira/browse/OFBIZ-2893 > Project: OFBiz > Issue Type: New Feature > Components: accounting >Affects Versions: SVN trunk >Reporter: Ratnesh Upadhyay > Fix For: SVN trunk > > Attachments: PopupGlTransactions.png, ReconciliationScreen.png, > ShowGlTransactions.patch > > > Added link [Gl Transactions] on Bank Reconciliation view screen. On click of > link pop up a window that shows above gl transactions. I have also added > screen shots to see resultant screens of this feature. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2893) Displayed gl account transactions for Bank Reconciliation.
[ https://issues.apache.org/jira/browse/OFBIZ-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay updated OFBIZ-2893: Attachment: PopupGlTransactions.png ReconciliationScreenpng Attached screen shots of resultant screens. Regards, -- Ratnesh Upadhyay > Displayed gl account transactions for Bank Reconciliation. > -- > > Key: OFBIZ-2893 > URL: https://issues.apache.org/jira/browse/OFBIZ-2893 > Project: OFBiz > Issue Type: New Feature > Components: accounting >Affects Versions: SVN trunk >Reporter: Ratnesh Upadhyay > Fix For: SVN trunk > > Attachments: PopupGlTransactions.png, ShowGlTransactions.patch > > > Added link [Gl Transactions] on Bank Reconciliation view screen. On click of > link pop up a window that shows above gl transactions. I have also added > screen shots to see resultant screens of this feature. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2893) Displayed gl account transactions for Bank Reconciliation.
[ https://issues.apache.org/jira/browse/OFBIZ-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay updated OFBIZ-2893: Attachment: (was: ReconciliationScreenpng) > Displayed gl account transactions for Bank Reconciliation. > -- > > Key: OFBIZ-2893 > URL: https://issues.apache.org/jira/browse/OFBIZ-2893 > Project: OFBiz > Issue Type: New Feature > Components: accounting >Affects Versions: SVN trunk >Reporter: Ratnesh Upadhyay > Fix For: SVN trunk > > Attachments: PopupGlTransactions.png, ShowGlTransactions.patch > > > Added link [Gl Transactions] on Bank Reconciliation view screen. On click of > link pop up a window that shows above gl transactions. I have also added > screen shots to see resultant screens of this feature. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2893) Displayed gl account transactions for Bank Reconciliation.
[ https://issues.apache.org/jira/browse/OFBIZ-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay updated OFBIZ-2893: Attachment: ShowGlTransactions.patch Here is the patch for mentioned feature. Thanks to Rishi, Awdesh for their support and Mridul and Sumit for discussing process. Regards, -- Ratnesh Upadhyay > Displayed gl account transactions for Bank Reconciliation. > -- > > Key: OFBIZ-2893 > URL: https://issues.apache.org/jira/browse/OFBIZ-2893 > Project: OFBiz > Issue Type: New Feature > Components: accounting >Affects Versions: SVN trunk >Reporter: Ratnesh Upadhyay > Fix For: SVN trunk > > Attachments: ShowGlTransactions.patch > > > Added link [Gl Transactions] on Bank Reconciliation view screen. On click of > link pop up a window that shows above gl transactions. I have also added > screen shots to see resultant screens of this feature. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-2893) Displayed gl account transactions for Bank Reconciliation.
Displayed gl account transactions for Bank Reconciliation. -- Key: OFBIZ-2893 URL: https://issues.apache.org/jira/browse/OFBIZ-2893 Project: OFBiz Issue Type: New Feature Components: accounting Affects Versions: SVN trunk Reporter: Ratnesh Upadhyay Fix For: SVN trunk Added link [Gl Transactions] on Bank Reconciliation view screen. On click of link pop up a window that shows above gl transactions. I have also added screen shots to see resultant screens of this feature. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2863) Purchase order get back ordered.
[ https://issues.apache.org/jira/browse/OFBIZ-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay updated OFBIZ-2863: Priority: Minor (was: Major) > Purchase order get back ordered. > > > Key: OFBIZ-2863 > URL: https://issues.apache.org/jira/browse/OFBIZ-2863 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: SVN trunk >Reporter: Ratnesh Upadhyay >Priority: Minor > Fix For: SVN trunk > > Attachments: PO_BackOrdered.patch, PO_BackorderedScreenshot.png > > > While creating a purchase order, If we add product quantity is more then ATP, > it shows exceeded quantity get backordered in order items block. This should > not be the case in purchase order. Also attached screen shot for the same. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2863) Purchase order get back ordered.
[ https://issues.apache.org/jira/browse/OFBIZ-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay updated OFBIZ-2863: Attachment: PO_BackorderedScreenshot.png Attached ScreenShot for the same. > Purchase order get back ordered. > > > Key: OFBIZ-2863 > URL: https://issues.apache.org/jira/browse/OFBIZ-2863 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: SVN trunk >Reporter: Ratnesh Upadhyay > Fix For: SVN trunk > > Attachments: PO_BackOrdered.patch, PO_BackorderedScreenshot.png > > > While creating a purchase order, If we add product quantity is more then ATP, > it shows exceeded quantity get backordered in order items block. This should > not be the case in purchase order. Also attached screen shot for the same. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2863) Purchase order get back ordered.
[ https://issues.apache.org/jira/browse/OFBIZ-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay updated OFBIZ-2863: Description: While creating a purchase order, If we add product quantity is more then ATP, it shows exceeded quantity get backordered in order items block. This should not be the case in purchase order. Also attached screen shot for the same. was: While creating a purchase order, If we add product quantity is more then ATP, it shows exceeded quantity get backordered in order items block. This should not be the case in sales order. Also attached screen shot for the same. > Purchase order get back ordered. > > > Key: OFBIZ-2863 > URL: https://issues.apache.org/jira/browse/OFBIZ-2863 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: SVN trunk >Reporter: Ratnesh Upadhyay > Fix For: SVN trunk > > Attachments: PO_BackOrdered.patch > > > While creating a purchase order, If we add product quantity is more then ATP, > it shows exceeded quantity get backordered in order items block. This should > not be the case in purchase order. Also attached screen shot for the same. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2863) Purchase order get back ordered.
[ https://issues.apache.org/jira/browse/OFBIZ-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay updated OFBIZ-2863: Attachment: PO_BackOrdered.patch Here is the patch to fix this issue. -- Ratnesh Upadhyay > Purchase order get back ordered. > > > Key: OFBIZ-2863 > URL: https://issues.apache.org/jira/browse/OFBIZ-2863 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: SVN trunk >Reporter: Ratnesh Upadhyay > Fix For: SVN trunk > > Attachments: PO_BackOrdered.patch > > > While creating a purchase order, If we add product quantity is more then ATP, > it shows exceeded quantity get backordered in order items block. This should > not be the case in sales order. Also attached screen shot for the same. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-2863) Purchase order get back ordered.
Purchase order get back ordered. Key: OFBIZ-2863 URL: https://issues.apache.org/jira/browse/OFBIZ-2863 Project: OFBiz Issue Type: Bug Components: order Affects Versions: SVN trunk Reporter: Ratnesh Upadhyay Fix For: SVN trunk While creating a purchase order, If we add product quantity is more then ATP, it shows exceeded quantity get backordered in order items block. This should not be the case in sales order. Also attached screen shot for the same. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2751) Improved PrintPickSheet Groovy file to get gift order specific data.
[ https://issues.apache.org/jira/browse/OFBIZ-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay updated OFBIZ-2751: Attachment: Picksheet_OFBIZ-2751.patch Attached improved patch. -- Ratneh Upadhyay > Improved PrintPickSheet Groovy file to get gift order specific data. > > > Key: OFBIZ-2751 > URL: https://issues.apache.org/jira/browse/OFBIZ-2751 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: SVN trunk >Reporter: Ratnesh Upadhyay >Priority: Minor > Fix For: SVN trunk > > Attachments: Picksheet_OFBIZ-2751.patch > > > Improved PrintPickSheet Groovy file to get gift order specific data. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-2751) Improved PrintPickSheet Groovy file to get gift order specific data.
Improved PrintPickSheet Groovy file to get gift order specific data. Key: OFBIZ-2751 URL: https://issues.apache.org/jira/browse/OFBIZ-2751 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: SVN trunk Reporter: Ratnesh Upadhyay Priority: Minor Fix For: SVN trunk Improved PrintPickSheet Groovy file to get gift order specific data. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2656) Canceling Order in Order view page of Order Manager, does not cancels inventory reservation and order items
[ https://issues.apache.org/jira/browse/OFBIZ-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay updated OFBIZ-2656: Attachment: createOrderItem_OFBiz_2656.patch Here is the updated patch for the fix. Thanks Mridul and Divesh for discussion on it. Regards, -- Ratnesh Upadhyay > Canceling Order in Order view page of Order Manager, does not cancels > inventory reservation and order items > --- > > Key: OFBIZ-2656 > URL: https://issues.apache.org/jira/browse/OFBIZ-2656 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: SVN trunk >Reporter: Divesh Dutta >Assignee: Vikas Mayur > Fix For: SVN trunk > > Attachments: createOrderItem_OFBiz_2656.patch, > createOrderItem_OFBiz_2656.patch > > > Canceling Order, does not cancels inventory reservation and order items. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r786786 - /ofbiz/trunk/applications/order/script/org/ofbiz/order/order/OrderReturnServices.xml
Hard Luck Pranay, Better luck next time ;) Great coincidence Ashish & Mridul. Regards, -- Ratnesh Upadhyay On Sat, Jun 20, 2009 at 4:29 PM, Pranay Pandey < pranay.pan...@hotwaxmedia.com> wrote: > Yes thats really a great coincidence Mridul & Ashish. > > It seems I missed it by 1 :) > > > Thanks & Regards > -- > Pranay Pandey > > > On Jun 20, 2009, at 4:23 PM, Ashish Vijaywargiya wrote: > > I am memorizing the scene of Block Buster movie "Coolie". >> Did you remember "Billa No 786" ? >> >> -- >> Ashish >> >> On Sat, Jun 20, 2009 at 4:18 PM, Mridul Pathak < >> mridul.pat...@hotwaxmedia.com> wrote: >> >> Indeed Ashish. What a great coincidence :). >>> >>> -- >>> Thanks, >>> Mridul Pathak >>> >>> >>> On 20-Jun-09, at 4:07 PM, Ashish Vijaywargiya wrote: >>> >>> Interesting revision number .. isn't it Mridul? >>> >>>> Happy to see that this number is assigned to me and you Mridul. >>>> >>>> -- >>>> Ashish >>>> >>>> On Sat, Jun 20, 2009 at 3:36 PM, wrote: >>>> >>>> Author: ashish >>>> >>>>> Date: Sat Jun 20 10:06:34 2009 >>>>> New Revision: 786786 >>>>> >>>>> URL: http://svn.apache.org/viewvc?rev=786786&view=rev >>>>> Log: >>>>> Applied patch from jira issue OFBIZ-2639 (Replacement Order against >>>>> "Wait >>>>> Replacement Reserved" Return is not being shipped) >>>>> Thanks Mridul for the contribution. >>>>> >>>>> Modified: >>>>> >>>>> >>>>> >>>>> ofbiz/trunk/applications/order/script/org/ofbiz/order/order/OrderReturnServices.xml >>>>> >>>>> Modified: >>>>> >>>>> >>>>> ofbiz/trunk/applications/order/script/org/ofbiz/order/order/OrderReturnServices.xml >>>>> URL: >>>>> >>>>> >>>>> http://svn.apache.org/viewvc/ofbiz/trunk/applications/order/script/org/ofbiz/order/order/OrderReturnServices.xml?rev=786786&r1=786785&r2=786786&view=diff >>>>> >>>>> >>>>> >>>>> == >>>>> --- >>>>> >>>>> >>>>> ofbiz/trunk/applications/order/script/org/ofbiz/order/order/OrderReturnServices.xml >>>>> (original) >>>>> +++ >>>>> >>>>> >>>>> ofbiz/trunk/applications/order/script/org/ofbiz/order/order/OrderReturnServices.xml >>>>> Sat Jun 20 10:06:34 2009 >>>>> @@ -901,6 +901,7 @@ >>>>> >>>> operator="equals" value="ORDER_HOLD"> >>>>> >>>> value="ORDER_APPROVED"/> >>>>> >>>> from-field="returnItemResponse.replacementOrderId"/> >>>>> +>>>> field="changeOrderStatusMap.setItemStatus" >>>>> value="Y"/> >>>>> >>>> in-map-name="changeOrderStatusMap"/> >>>>> >>>>> >>>> operator="equals" value="ORDER_CANCELLED"> >>>>> >>>>> >>>>> >>>>> >>>>> >>> >
[jira] Created: (OFBIZ-2635) Order notes are not displayed on sales order pdf, instead of that it gives error.
Order notes are not displayed on sales order pdf, instead of that it gives error. -- Key: OFBIZ-2635 URL: https://issues.apache.org/jira/browse/OFBIZ-2635 Project: OFBiz Issue Type: Bug Components: order Affects Versions: Release Branch 9.04, SVN trunk Reporter: Ratnesh Upadhyay Fix For: Release Branch 9.04, SVN trunk To regenerate the error : 1). Create a sales order. 2). Add notes for this order. 3). Depress on PDF link. Regards, -- Ratnesh Upadhyay -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2630) Small fix to display Item quantity history on order history page.
[ https://issues.apache.org/jira/browse/OFBIZ-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay updated OFBIZ-2630: Attachment: OrderItemHistory_OFBiz_2630.patch Uploaded patch to fix the issue also removed extra line displayed on order header information block of view order page. Regards, -- Ratnesh Upadhyay > Small fix to display Item quantity history on order history page. > - > > Key: OFBIZ-2630 > URL: https://issues.apache.org/jira/browse/OFBIZ-2630 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: SVN trunk >Reporter: Ratnesh Upadhyay >Priority: Minor > Fix For: SVN trunk > > Attachments: OrderItemHistory_OFBiz_2630.patch > > > In present scenario, if a user edits order items and he updates the item > quantity and click on view order history button, the item quantity history is > not displayed on order history page. > -- > Ratnesh Upadhyay -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-2630) Small fix to display Item quantity history on order history page.
Small fix to display Item quantity history on order history page. - Key: OFBIZ-2630 URL: https://issues.apache.org/jira/browse/OFBIZ-2630 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: SVN trunk Reporter: Ratnesh Upadhyay Priority: Minor Fix For: SVN trunk In present scenario, if a user edits order items and he updates the item quantity and click on view order history button, the item quantity history is not displayed on order history page. -- Ratnesh Upadhyay -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-2627) Clicking on expire button shows only expired record in List Contact List Party form of marketing component, it should show active records only.
Clicking on expire button shows only expired record in List Contact List Party form of marketing component, it should show active records only. Key: OFBIZ-2627 URL: https://issues.apache.org/jira/browse/OFBIZ-2627 Project: OFBiz Issue Type: Improvement Components: marketing Affects Versions: SVN trunk Reporter: Ratnesh Upadhyay Priority: Minor Fix For: SVN trunk In marketing component when a user depress on expire button against a party in List Contact List Party form, It shows expired record (recent expired) instead of showing all the active parties associated with that contact list. Regards, -- Ratnesh Upadhyay -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-2626) Edit contact list party form should not have primary key fields in editable mode.
Edit contact list party form should not have primary key fields in editable mode. -- Key: OFBIZ-2626 URL: https://issues.apache.org/jira/browse/OFBIZ-2626 Project: OFBiz Issue Type: Improvement Components: marketing Affects Versions: Release Branch 9.04, SVN trunk Reporter: Ratnesh Upadhyay Priority: Minor Fix For: Release Branch 9.04, SVN trunk It works fine in case of create contact list party but in case of edit it, shows editable primary key fields, we should restrict user to edit primary key fields. Steps to regenerate the issue : 1). Click on marketing component. 2). Click on Contact List > find list and select any one from the list. 3). Click on parties tab button > find the list of contact list parties > click on edit button. -- Ratnesh Upadhyay -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2590) Orders not filtered properly on Order List page
[ https://issues.apache.org/jira/browse/OFBIZ-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718837#action_12718837 ] Ratnesh Upadhyay commented on OFBIZ-2590: - I functional reviewed and tested patch, Its working fine. I think its ready for commit. -- Ratnesh Upadhyay > Orders not filtered properly on Order List page > --- > > Key: OFBIZ-2590 > URL: https://issues.apache.org/jira/browse/OFBIZ-2590 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Release Branch 9.04, SVN trunk > Environment: Ubuntu, FF3 >Reporter: Chirag Manocha >Priority: Minor > Fix For: Release Branch 9.04, SVN trunk > > Attachments: OrderFilterBug_OFBiz-2590.patch > > > When logged in user uncheck all the status on Order List page and select > order type = "Sales Order" only then orders are not filtered on types of > Order. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2598) Additional Shipping Charges and Sales Taxes are getting lost on clicking update item button.
[ https://issues.apache.org/jira/browse/OFBIZ-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay updated OFBIZ-2598: Attachment: FixedAdditionalAdjustments.patch Attached patch to fix the issue. Regards, -- Ratnesh Upadhyay > Additional Shipping Charges and Sales Taxes are getting lost on clicking > update item button. > - > > Key: OFBIZ-2598 > URL: https://issues.apache.org/jira/browse/OFBIZ-2598 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Release Branch 9.04, SVN trunk > Reporter: Ratnesh Upadhyay > Fix For: Release Branch 9.04, SVN trunk > > Attachments: FixedAdditionalAdjustments.patch > > > On order view page Additional Shipping Charges and Sals taxes are getting > lost on clicking on update item button. > -- Ratnesh Upadhyay -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-2598) Additional Shipping Charges and Sales Taxes are getting lost on clicking update item button.
Additional Shipping Charges and Sales Taxes are getting lost on clicking update item button. - Key: OFBIZ-2598 URL: https://issues.apache.org/jira/browse/OFBIZ-2598 Project: OFBiz Issue Type: Bug Components: order Affects Versions: Release Branch 9.04, SVN trunk Reporter: Ratnesh Upadhyay Fix For: Release Branch 9.04, SVN trunk On order view page Additional Shipping Charges and Sals taxes are getting lost on clicking on update item button. -- Ratnesh Upadhyay -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2591) Getting error while updating item from order view page.
[ https://issues.apache.org/jira/browse/OFBIZ-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay updated OFBIZ-2591: Component/s: order Fix Version/s: SVN trunk Release Branch 9.04 Affects Version/s: SVN trunk Release Branch 9.04 > Getting error while updating item from order view page. > > > Key: OFBIZ-2591 > URL: https://issues.apache.org/jira/browse/OFBIZ-2591 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Release Branch 9.04, SVN trunk >Reporter: Ratnesh Upadhyay > Fix For: Release Branch 9.04, SVN trunk > > > Getting error "The changed return is can not be greater then the cash given". > Seems that, it occurs due to duplication of default promotion associated with > Order. > May be there is wrong with recalculating cart values. > Regards, > -- Ratnesh Upadhyay -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-2591) Getting error while updating item from order view page.
Getting error while updating item from order view page. Key: OFBIZ-2591 URL: https://issues.apache.org/jira/browse/OFBIZ-2591 Project: OFBiz Issue Type: Bug Reporter: Ratnesh Upadhyay Getting error "The changed return is can not be greater then the cash given". Seems that, it occurs due to duplication of default promotion associated with Order. May be there is wrong with recalculating cart values. Regards, -- Ratnesh Upadhyay -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2581) Update communication event status as read in CommunicationEvent entity on the basis of status updated in CommunicationEventRole entity.
[ https://issues.apache.org/jira/browse/OFBIZ-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718351#action_12718351 ] Ratnesh Upadhyay commented on OFBIZ-2581: - Mridul's suggestion looks good to me. Hans what do you think about it. -- Ratnesh > Update communication event status as read in CommunicationEvent entity on the > basis of status updated in CommunicationEventRole entity. > > > Key: OFBIZ-2581 > URL: https://issues.apache.org/jira/browse/OFBIZ-2581 > Project: OFBiz > Issue Type: Improvement >Affects Versions: SVN trunk >Reporter: Ratnesh Upadhyay >Assignee: Ashish Vijaywargiya >Priority: Minor > Fix For: SVN trunk > > Attachments: com-read-status-ofbiz-2581.patch > > > - In marketing > Reports > Email Status Report > The resultant report is not showing the status of all those communication > events which are in read status. In present system it is handled in > CommunicationEventRole entity. Here we have "COM_ROLE_READ" status for all > those communication events that are opened by the user (read by the > recipient) but when we saw those communication events from report tab they > are listed as completed status, because displayed list is prepared via > "CommunicationEvent " entity and there is no any status update in case of > read. (because updated in CommunicationEventRole entity) > Apart from this if we have a look on those communication events that are in > bounced status due to invalid email address , are updated in > CommunicationEvent entity as well. > So for updating status of a communication event as read , we wrote an ECA > rule, to update CommunicationEvent entity's record to COM_READ , when the > status of CommunicationEventRole is changed to COM_ROLE_READ. So that we can > get all those communication events, that has read status from > "CommunicationEvent" entity. > Please suggest the proper approach from the above given solution. Or any > other better approach, if any. > Thanks in advance. > -- > Ratnesh Upadhyay -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2581) Update communication event status as read in CommunicationEvent entity on the basis of status updated in CommunicationEventRole entity.
[ https://issues.apache.org/jira/browse/OFBIZ-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718025#action_12718025 ] Ratnesh Upadhyay commented on OFBIZ-2581: - Hi Hans, Thanks for your comments, we are not updating the status of parent communication event here instead of that we are just update the status of all those communication events which are associated with parties. In other words we have the same communication event records in CommunicationEvent entity as we have in CommunicationEventRole entity for the same party but in case of mark as read the status will be updated only in communicationEventRole entity. Our patch will update the status of only those events in "CommunicationEvent" entity, who have statusId as "COM_ROLE_READ" in " CommunicationEventRole" entity. Here are the demo data which helps you to understand the scene : What we are doing here in above two records when status updates for communicationEventId = "10002" and partyId="1" in CommunicationEventRole entity we simply update the status in CommunicationEvent entity for the same communicationId. It means that we are updating status of communicationEventId="10002" here you can see that the partyId is also same and the old status is "COM_COMPLETE" to "COM_READ". AFAIK, that when we send the mails from contact list It will create the different communication events for all the parties who are added as recipient in the list. Suppose there are two parties are associated with contact list and mail is sent to contact list then three communication event records are created one is created as parent record with communicationEventTypeId = "AUTO_EMAIL_COM" and another two are having "COM_COMPLETE" so we are updating the status of another two records which are specific to party and not for the parent communication event. Note : I looked CommunicationEventAndRole entity, It has only three status values (entered, read and completed) all these are available from roleStatusId field but the bounce status is not available there. Suggestions are most welcome. Thanks ! Regards, -- Ratnesh Upadhyay > Update communication event status as read in CommunicationEvent entity on the > basis of status updated in CommunicationEventRole entity. > > > Key: OFBIZ-2581 > URL: https://issues.apache.org/jira/browse/OFBIZ-2581 > Project: OFBiz > Issue Type: Improvement >Affects Versions: SVN trunk >Reporter: Ratnesh Upadhyay >Assignee: Ashish Vijaywargiya >Priority: Minor > Fix For: SVN trunk > > Attachments: com-read-status-ofbiz-2581.patch > > > - In marketing > Reports > Email Status Report > The resultant report is not showing the status of all those communication > events which are in read status. In present system it is handled in > CommunicationEventRole entity. Here we have "COM_ROLE_READ" status for all > those communication events that are opened by the user (read by the > recipient) but when we saw those communication events from report tab they > are listed as completed status, because displayed list is prepared via > "CommunicationEvent " entity and there is no any status update in case of > read. (because updated in CommunicationEventRole entity) > Apart from this if we have a look on those communication events that are in > bounced status due to invalid email address , are updated in > CommunicationEvent entity as well. > So for updating status of a communication event as read , we wrote an ECA > rule, to update CommunicationEvent entity's record to COM_READ , when the > status of CommunicationEventRole is changed to COM_ROLE_READ. So that we can > get all those communication events, that has read status from > "CommunicationEvent" entity. > Please suggest the proper approach from the above given solution. Or any > other better approach, if any. > Thanks in advance. > -- > Ratnesh Upadhyay -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2581) Update communication event status as read in CommunicationEvent entity on the basis of status updated in CommunicationEventRole entity.
[ https://issues.apache.org/jira/browse/OFBIZ-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717923#action_12717923 ] Ratnesh Upadhyay commented on OFBIZ-2581: - Sure, I'll upload them shortly. Thanks ! -- Ratnesh > Update communication event status as read in CommunicationEvent entity on the > basis of status updated in CommunicationEventRole entity. > > > Key: OFBIZ-2581 > URL: https://issues.apache.org/jira/browse/OFBIZ-2581 > Project: OFBiz > Issue Type: Improvement >Affects Versions: SVN trunk >Reporter: Ratnesh Upadhyay >Assignee: Ashish Vijaywargiya >Priority: Minor > Fix For: SVN trunk > > Attachments: com-read-status-ofbiz-2581.patch > > > - In marketing > Reports > Email Status Report > The resultant report is not showing the status of all those communication > events which are in read status. In present system it is handled in > CommunicationEventRole entity. Here we have "COM_ROLE_READ" status for all > those communication events that are opened by the user (read by the > recipient) but when we saw those communication events from report tab they > are listed as completed status, because displayed list is prepared via > "CommunicationEvent " entity and there is no any status update in case of > read. (because updated in CommunicationEventRole entity) > Apart from this if we have a look on those communication events that are in > bounced status due to invalid email address , are updated in > CommunicationEvent entity as well. > So for updating status of a communication event as read , we wrote an ECA > rule, to update CommunicationEvent entity's record to COM_READ , when the > status of CommunicationEventRole is changed to COM_ROLE_READ. So that we can > get all those communication events, that has read status from > "CommunicationEvent" entity. > Please suggest the proper approach from the above given solution. Or any > other better approach, if any. > Thanks in advance. > -- > Ratnesh Upadhyay -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2581) Update communication event status as read in CommunicationEvent entity on the basis of status updated in CommunicationEventRole entity.
[ https://issues.apache.org/jira/browse/OFBIZ-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ratnesh Upadhyay updated OFBIZ-2581: Fix Version/s: SVN trunk Affects Version/s: SVN trunk > Update communication event status as read in CommunicationEvent entity on the > basis of status updated in CommunicationEventRole entity. > > > Key: OFBIZ-2581 > URL: https://issues.apache.org/jira/browse/OFBIZ-2581 > Project: OFBiz > Issue Type: Improvement >Affects Versions: SVN trunk >Reporter: Ratnesh Upadhyay >Priority: Minor > Fix For: SVN trunk > > > - In marketing > Reports > Email Status Report > The resultant report is not showing the status of all those communication > events which are in read status. In present system it is handled in > CommunicationEventRole entity. Here we have "COM_ROLE_READ" status for all > those communication events that are opened by the user (read by the > recipient) but when we saw those communication events from report tab they > are listed as completed status, because displayed list is prepared via > "CommunicationEvent " entity and there is no any status update in case of > read. (because updated in CommunicationEventRole entity) > Apart from this if we have a look on those communication events that are in > bounced status due to invalid email address , are updated in > CommunicationEvent entity as well. > So for updating status of a communication event as read , we wrote an ECA > rule, to update CommunicationEvent entity's record to COM_READ , when the > status of CommunicationEventRole is changed to COM_ROLE_READ. So that we can > get all those communication events, that has read status from > "CommunicationEvent" entity. > Please suggest the proper approach from the above given solution. Or any > other better approach, if any. > Thanks in advance. > -- > Ratnesh Upadhyay -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
