This is the last newsletter for the Tryton 6.6 series. You will find the latest development:
Changes for the User
A warning is raised when cancelling an account move related to an invoice, because the invoice will be marked as paid and not cancelled.
The receivable/payable lines now have a column with the cumulative balance. This helps you see the evolution of the customer/supplier debt.
We’ve added links from party to its purchase and sales lines in addition to the purchases and sales. Also all those links show the number of pending and done records.
An option to cancel a move with a reversal move has been added. So, when checked, Tryton will post the move with the debit and credit swapped over, instead of posting negative debits and credits.
Now Tryton notifies the user when they are registering a party identifier that is already in use with another party. This helps prevent duplicate parties from being created.
The stock moves and invoice lines linked to a sale or purchase line are now displayed on their form. This is useful to understand the status of an order.
Tryton now supports setting a price for a carrier cost that is based on weight even if the products have no weight.
We’ve added a new category of unit of measure for energy with some common units like the Joule and Kilowatt-hour.
And we removed the non-standard “Work day” unit because its value depends on the company’s working practices.
Changes for the System Administrator
The size of each cache can now be fine tuned using entries in the configuration file. So you no longer need to develop a new module to change the cache size for a particular usage.
Changes for the Developer
The server now includes the tools to generate barcodes and QR codes.
The product module makes use of a method that generates the barcode for a corresponding product identifier.
We’ve added two methods on the
searchable which returns
True if the field can be used in a domain expression and
sortable if the field can be used in an order expression.
list-form view now has abilities to do validation, pre-validation and automatic saving when the selected record changes. This mimics the behaviour of the editable list.
Also the selections are now restored on
New types of exceptions have been introduced:
ButtonActionException. They are used to launch an action from a button using an exception (which rolls back the transaction started by the button).
This is useful if, for example, you need to launch a wizard before executing a transition.
Now it’s easy to extend the context keys that the caches must ignore.
For the calendar view, it is possible to scroll to a time, by default, by including the
calendar_scroll_time key in the context. This is only supported by the web client for now.