To implement that redundancy onto the OrderTerm* would eliminate the ability to model implicit terms and explicit terms. Therefore making impossible to audit term changes.
*That's assuming that you're populating the OrderTerm with the cascaded values from a store setting, BillingAccountTerm, AgreementTerm, QuoteTerm. --- Jacopo Cappellato <[EMAIL PROTECTED]> wrote: > I don't agree with this. > In my opinion the invoice should only look at the order terms (and > maybe > the billing account terms). > > Jacopo > > Chris Howe wrote: > > then..(program logic thinking) > > When an invoice is created it should determine the InvoiceTerm by > > cascading StoreSetting overridden by BillingAccountTerm setting > > overridden by AgreementTerm overridden by OrderTerm (QuoteTerm's > use > > should only be used to create the OrderTerm when creating the Order > and > > should not be used during the creation of the InvoiceTerm) > > > > > > --- Jacopo Cappellato <[EMAIL PROTECTED]> wrote: > > > >> Chris, > >> > >> yes, of course, an agreement between the company and the customer > is > >> implied, even if not stored in OFBiz, when the term is added to an > >> order. > >> > >> Jacopo > >> > >> > >> Chris Howe wrote: > >>> (Real world thinking) > >>> Doesn't the use of a term presuppose an agreement? Whether that > >>> agreement has been logged into OFBiz is a different story. > Doesn't > >> the > >>> agreement actually exist? > >>> > >> > >> > > >
