Comment by [email protected]: Thanks for the feedback.
I don't get the usage of dunning procedures?
Could you go into details about what is unclear?
In account.dunning.level, what is the usage of level? The number of days already give an order.
Agreed, that's redundant and will be removed.
In account.dunning.level instead of text, I will use a link to the report to use.
You mean a Many2One to "ir.action.report"?
In account.dunning.dunning, why storing the dunning_level as it could be computed, idem for date.
Because it could be the case that the interval between two dunning runs is longer than the time between to dunning levels. For example if no dunning run is done for some time a receivable entry could be in the second dunning level according to the days since the maturity date but you nevertheless don't want to skip the first dunning level and politely remind the customer before ultimately threaten with legal measures.
I would prefer to not extend account.move.line and put all in the dunning lines.
But the dunning procedure to be applied to the receivable is a property of the move line itself. What would be the advantage of having an additional object mapping move lines to dunning procedures?
For more information: http://code.google.com/p/tryton/wiki/DunningModule -- -- [email protected] mailing list
