- Automatic bank reconciliation: failure to acknowledge that x * -1 == -x
- Interface: hide the 'partial reconciliation' sign when matching a transaction with an already registered payment
- restored icon of modules account_check_writing and l10n_us_check_printing
- removed payment_type from account.payment tree/view since those views are already used with a domain and the type can be inferred from the name given by a sequence
- account.payment field company_id wasn't stored and, so, 'Group By' failed
- fixed extensibility of register payment wizard through method get_payment_vals()
- since register payment fully pays selected invoices, the amount should be readonly
- if payment journal is called 'Payment Mode', payment_method should not be called 'Payment Mode'
- improved batch deposit template
- check memo length when registering a check
- in check printing, sort invoices by due date
- checks get a check number attributes when registered from the payment wizard as well
- when a module extends a method from account.payment it should be careful to check the selected payment method
This commit introduces a new view type, the timeline view. This view is
intended to display messages like the previous chatter. This is now a view
like the form or list view. Like other views it will be possible to have
custom templates for some specific needs, allowing customization.
[IMP] mail: the value tracking is modified. Previously messages were created
containing the modified values. Those values are now stored, using a new
model mail.tracking.value. The message body is dynamically build based on
the values. Tests have been updated.
This version is temporary. Indeed two main modifications will come in a short
future :
- the new design will improve the display
- the slack mode will change the way the Inbox and notifications are managed
All glory to the Hypnotoad.
Special thanks to Valerie Pirenne (vpi), Jerome Maes (jem) and Richat Mathot
(rim) that did not code but said a lot of things. Martin Trigaux (mat) did
nothing, a bit like for the slides modules, but he is busy sending emails.
Now,
- event contains the HTML badge fields and the report (and report templates) to print badges
- event_sale add the ticket type on badges
- website_event allow the edition of badge throught website editor.
When the editor will be available in backend, event will be allow to edit badge report, so the action should be moved from website_Event to event module.
Thibault Delavallée