Nicolas, Thank you for the detailed information. I agree on setting the trigger value on on store level so that each store may behaves as per business need, in case of multiple stores. Just one question here, orderHeader will also have the same field or it is intended to override some default behavior of store level setting.
Could you please help us here bit more, when you get chance. Thanks! Best Regards, Rishi Solanki Sr Manager, Enterprise Software Development HotWax Systems Pvt. Ltd. Direct: +91-9893287847 http://www.hotwaxsystems.com www.hotwax.co On Tue, Feb 27, 2018 at 10:30 PM, Nicolas Malin <nicolas.ma...@nereide.fr> wrote: > Hi Rishi > > On 26/02/2018 15:11, Rishi Solanki wrote: > >> Antoine, >> >> In general I observe that for a party business may want to send invoice at >> the end of month. But for that as well I think its okay to generate the >> invoice at the time of order completion and send all invoices once. >> >> Also what Taher suggested looks promising to me. That means use invoice >> status, lets say all invoices in Pending status until some user come and >> > It's a little more complicated from own different business context. In > Europe the generate invoice date it's really important for payment term and > order sequence of invoice ids. Theses problematic exclude all ideas to pre > generate invoice before sent it. > > Currently on the standard we have only the possibility to say for an order > that we bill it when a shipment is completed or the order is completed. But > we can't stop the invoice generation. > > And to complicate the picture we have some site with billing agreement > where some order can bill at the shipment, some other at the end of month > and some other related to the incoterm. It's really a pain :) > > I already exchanged with Antoine with the first implementation, because we > implement this quickly. I'm not in favor to invoicePerOrder and also to > remove invoicePerShipment to replace them by an enumeration on the > ProductStore and the OrderHeader like productStore.billingOrderProcessEnumId > and orderHeader.billingOrderProcessEnumId clearly identify where we can > implement on standard and offer the possibility to define more for custom > billing process. > > With this we can define how a product store manage them orders and if > necessary we can manage some exception by order. > > Cheers, > Nicolas > > > approve it. Then use statuses to consider invoices for business use etc. >> >> So I think what you expect for your requirement actually OFBiz offers, you >> can use the status workflow for that. Most probably no custom changes. >> >> >> >> Rishi Solanki >> Sr Manager, Enterprise Software Development >> HotWax Systems Pvt. Ltd. >> Direct: +91-9893287847 >> http://www.hotwaxsystems.com >> www.hotwax.co >> >> On Mon, Feb 26, 2018 at 4:24 PM, Taher Alkhateeb < >> slidingfilame...@gmail.com >> >>> wrote: >>> Hi Antoine, >>> >>> Thank you for your work and I hope we get to work with you more often. >>> I have a few comments / questions: >>> >>> - First of all, you added a postgres dependency to the build file >>> (probably by mistake?). >>> - perhaps others can pitch in but I'm not sure if it is useful to >>> introduce? Is this a common need or more of a specific custom >>> requirement? >>> - Also, why an indicator? Why not for example just a different status >>> workflow instead? >>> >>> On Mon, Feb 26, 2018 at 1:40 PM, Antoine Ouvrard >>> <antoine.ouvr...@nereide.fr> wrote: >>> >>>> Hello, >>>> >>>> I would like to introduce you a improvement. >>>> >>>> In some case, we need to delay billing at the end of the month for >>>> example. >>>> >>>> But to complete the order we need to disable triggering the >>>> invoice generation. >>>> >>>> Here's my proposal https://issues.apache.org/jira/browse/OFBIZ-10241 >>>> >>>> Antoine >>>> >>> >
