Please update your systems to take care of a security bug we found last month. See the related announcement.
Soon, in just two months time, at the very beginning of November we’ll be publishing our next Long Term Supported (LTS) release of Tryton, version 7.0. Please test the current release, version 6.8, or the actual developments from our repositories.
In the last month we focused on fixing bugs, improving how things behave, speeding-up performance issues and adding new features for you. We also released bug fixes for the maintained series 5.0, 6.0, 6.6 and 6.8.
Changes for the User
All the number fields are now first sorted by length. This provides a more natural order for the most common cases where the content is just a number or a number with a prefix.
Stock, Sales, Purchase and Project
On purchase requests we’ve added new domains to filter for quoted and received records.
Tryton now uses the shipping date instead of sale date to check the stock quantities used by the planned quantity and stock forecast.
For purchases and sales we’ve added actions to trigger the creation of draft documents to make following-up manual invoice and shipment methods easier for the users. As the user may need to manually create those documents anyway, we provide an action that creates those documents as if the method On Order had been used.
In the stock_package* modules we renamed the code field to number.
Accounting, Invoicing and Payment
The account moves generated from currency exchange values are now automatically posted by the system. This prevents the need to handle forgotten unposted currency exchange moves and avoids having to deal with them manually.
A selection widget is now used for the journal field. This prevents the creation of journals directly from documents and makes it simpler for users to select them.
For consistency Tryton now no longer considers the party field when searching in the invoice record name.
User Interface
The search offset is now reset when the filter is changed. This is an improvement on the old behaviour because if a user moved to a later page (updating the offset), then changed the filter, it resulted in no records being shown. This was because not enough records were found to show any at that offset. With the new behaviour, the first page of the records will be always shown after the filter is updated.
It is now possible to copy selected records on the web-client. A new contextual menu item has been added to mimic the feature which is available on the desktop client using the keyboard shortcut.
System Data and Configuration
User applications that are created from the user’s preferences are now put directly in the validated state to improve the user experience.
The list of supported identifiers has been increased. The following identifiers have been added:
- Belgian National Number identifier
- Algerian Tax Number identifier
- Faroese Tax Number identifier
- Ghanaian Taxpayer Identification Number identifier
- Indian Voter ID identifier
- Indian VAT number identifier
- Moroccan Tax Number identifier
- Macedonian Tax Number identifier
- Pakistani Computerised National Identity Card Number identifier
- Portuguese Identity Number identifier
- Slovenian Unique Master Citizen Number identifier
- Thai Memorandum of Association Number identifier
- Thai Personal Identification Number identifier
- Thai Taxpayer Identification Number identifier
- Tunisian Tax Number identifier
New Modules
The new Product Price List Cache Module can be used to pre-compute the prices for each product and price list. This improves the performance of price lists with a large number of lines.
Documentation
Our base documentation has been greatly improved with a new chapter about the internal resource module.
Changes for the System Administrator
The account dunning email logs have been merged into the general email archives.
Changes for Implementers and Developers
The PostgreSQL backend now supports BTREE_GIN indexing . Also support for similarity expressions have been improved. Last but not least, the expressions are now filtered.
Tests can now execute the same scenario with a list of different global variables defined in a JSON list.