Tryton News: Newsletter February 2023 :
by:
blow post content copied from Planet Python
click here to view original post
A lot of new features have landed in Tryton this month. Some of them were on hold to prepare the migration to Heptapod but we are catching up quickly thanks to the new contribution workflow.
Changes for the User
Direct debit payments are no longer created for blocked receivable lines.
Rounding errors for multiple taxes applied to the same line, are now allocated between each tax line to provide a more accurate result.
A carrier is now required to quote a sale that has a shipment cost set. This avoids an incoherent setup which then misses quoting the carrier cost.
For consistency we renamed the field “Name” on account reconciliation to “Number” as it is generated from a sequence.
We now use a circle border for avatar images of individuals and a square border for groups like companies.
The country organizations can now be used as criteria for tariff codes and duty rates.
We now show all the criteria for the tariff codes on the product form.
The translate popup has been reworked to be clearer. It uses now a toggle button to start editing the translation for a language and uses a label to indicate a translation is fuzzy.
We changed the boolean operators in the search box from and
to &
and or
to |
. This way the searches are independent of the language and we do not need to have a way to escape them.
The clients do not select any more the first record of each list by default.
The default size of the desktop client has been increased.
When trying to assign shipments or productions, all the documents that can be fully assigned are now assigned instead of being all or nothing.
The sale, purchase, commission and stock report records can now be searched by name.
New Modules
Changes for the System Administrator
The weekly and monthly timesheet reports have now also access rules. The supervisor has now access to the timesheet reports of the employees he supervises.
The production creates now automatically lots for output product that requires one and whom has a sequence configured.
Changes for the Developer
Tryton will now warn when foreign relation records must be saved implicitly. This is to enforce a design pattern which groups together saving for performance.
Tryton no longer validates the domain for empty fields. This simplifies domain definitions for fields that are not required, as they do not need to care about the case when a field is empty. As side effect the clients don’t enforce the uniqueness of values in non-required fields.
The client now considers a domain that uses the in
clause with a single value to be a unique value.
The target_search
attribute of Many2One
fields has been removed in favor of an automatic decision based on the number of rows in the target table.
The ORM now uses the EXIST
operator instead of IN
to search on One2Many
fields when the target table has many rows.
Any needed tables are now locked at the beginning of the transaction. This guarantees that the latest values are read from the table. This is managed automatically by restarting the transaction if a table lock is requested during the execution of the code.
We added support for different types of borders on images and icons (but only for the web client).
The warehouse locations are now stored on the shipments at the creation. This ensures that the domain based on them stays valid during the all life of the shipment.
The cookiecutter template is now included in the monorepo. This way it will be versioned per series.
New exceptions have been added to stop the transaction but return a result which can be an action to launch for the client.
To speed-up the loading of the list of records, the clients can now retrieve in the read call the string to display for selection field.
2 posts - 1 participant
February 01, 2023 at 12:30PM
Click here for more details...
=============================
The original post is available in Planet Python by
this post has been published as it is through automation. Automation script brings all the top bloggers post under a single umbrella.
The purpose of this blog, Follow the top Salesforce bloggers and collect all blogs in a single place through automation.
============================

Post a Comment