New Tryton release 4.6

Publié: 2017-10-30 18:00:00+00:00 release

We are proud to announce the 4.6 release of Tryton.

This release is enhanced by the addition of 9 new modules covering many different topics. There has been also an effort in improving the graphical user interface and the user experience by fixing many small details. It is also good to note the inclusion of the Spanish charts of accounts which required some improvements in the standard accounting modules. Of course it includes many bug fixes and performance improvements.

As usual the migration from previous series is fully supported. Some manual operation may be required, see migration from 4.4 to 4.6.

Major changes for the user

  • In addition to the user name, company and currency in the title of the clients, we have added the profile or the login details. This way, the user can find faster the right windows.

  • The order of the toolbar has been reworked to have a more logical order and grouping. The same logical has been applied also on the toolbars of the widgets.

    Tryton toolbar order
  • On previous version, the headers of the column were always centered. Now they use the same alignment as the content following the best practice. Texts columns aligned on left and numerical columns on right. Also to improve the discoverability, editable lists have a grid design instead of just stripped row. This allows the user to know directly if it is editable.

  • Similar to the redesign of the button on relation field in the release 4.2, this release improves the design of the Binary and Image widget. Only the available buttons are shown instead of being disabled. But also before having the option to upload a new file, the previous file must be cleared. This prevents confusion to some users.

    Sao non-editable list Sao editable list

Desktop

  • Under GTK+-3, a default theme has been added for read-only, required and invalid entries.
  • Also under GTK+-3, it is possible to add in the configuration folder a file theme.css which will be loaded as user theme. We have added Tryton's specific selectors: .readonly, .required, .invalid and .window.profile-<name>. The last one is useful to setup a different style to the windows depending of the profile.

Web

  • The web client has now the same keyboard shortcuts as the desktop client. You can see them with ctrl+h. This make is simple to use without mouse.

Accounting

  • A new wizard has been added to renew the fiscal year. It takes the previous fiscal year and some other parameters to create the new fiscal year automatically. The sequences can be reset automatically and the same number of periods are created.

    Sao renew fiscal year
  • On some countries, it is required to add a legal notice when some taxes are applied. This legal notice can now be configured on the tax to be included automatically and so avoid mistakes or oversights.

  • The tax rule system is the way Tryton configure the taxes to apply on an invoice for a party. This works by replacing the default tax by the one defined on the matching rule. Now it is possible to configure the rule to keep the default tax and add the rule one. It is needed to support tax mechanism from some countries like the equivalence surcharge for Spanish VAT.

  • The tax description which appear on the invoice is now translatable.

  • The payable and receivable accounts on party are no more required. This prevented the creation of parties when no default values was setup even if the values were not needed. Now, a message will be raised only when the value is needed for a particular operation.

  • It is now possible to search the amounts of the general legder. It is useful for example to get only the accounts with a balance.

  • The general ledger and the income statement can be computed for a range of date in addition to the sets of periods.

  • The configuration wizard allows to configure default receivable and payable accounts for categories and products.

account_eu

This is a new module that aims to implement common accounting requirements in Europe. The first common feature added is the EC sales list.

account_es

A new module registers two default charts of account and taxes for Spain:

  • Plan General Contable Español 2008
  • Plan Contable para PYMES 2008

Invoicing

  • The tax identifier of the party invoiced is stored on the invoice. By default it is the first tax identifier of the party that is chosen but it can be changed. This is useful for tax reporting and when a party has many tax identifiers.
  • The Belgian chart of accounts has been adapted to configure the taxes for the EC sales list.

Payment

  • The clearing of payments only worked when paying a specific line. Now it can also work if an account is defined instead of a line. The common case is when you register a deposit for which you have no line but still want to register it once the payment is succeeded.

  • The manage of payment with Stripe received many improvements:

    • The user can now create manually Stripe payments. Usage showed that it may be needed and there was indeed no technical reason to prevent.
    • It is possible to select the specific Source of the Customer.
    • It is now possible to enter an existing Customer by filling its ID.
    • Tryton supports now the two steps payment flows. It is just checkbox to uncheck to activate on this flow. The amount can be changed between the authorisation and the capture and the capture is just triggered by a button.

Statement

  • When a statement is cancelled, if the generated move lines were reconciled, they are now automatically unreconciled. This ease the task of correcting a statement as it is no more a task to do for the user.

account_statement_coda

This new module adds the automatic import of CODA file as statement. The CODA format is a standard from the Belgian Financial Sector Federation which is supported by most of the Belgian banks.

account_dunning_email

This new module allows to define for a dunning procedure level to send an email to the party. The template of the email can be different at each level. The action of sending an email is logged into the system.

Stock

  • It is possible to restrict a location to have only one level of children. This allows to apply some techniques to improve the performance of the stock quantity computation and to support chaotic storage which requires to have a huge number of locations.
  • In addition to the wizard to split stock move, there is now a wizard to split a shipment. It asks for the moves to be sent to the new shipment. This is useful if the default order can be too big for the carrier.
  • There is a warning raised when a incoming or outgoing move is done without an origin. Until now, it was raised once for each move but with this release only one global warning is raised for all moves.
  • For the perpetual stock accounting, Tryton supports now the reversed drop shipment.
  • In order to register past move, the effective date of move can be set manually by the user.
  • In version 3.6, we added a new state 'staging' on move. But the constraint, that allows to delete only 'draft' or 'cancel' move, was not updated to allow also 'staging'. This is now corrected with this release.
  • A check has been added in order to prevent the deactivation of a location if there are still products in it. This way the conservation of products is respected.

stock_consignement

This new module allows to manage consignment stock from supplier in the company warehouse and at the customer warehouse. The corresponding invoices are created automatically when products are used from such location.

stock_location_move

This new module allows to define some storage location as movable. They can be moved by an internal shipment. This can be used for example to manage palettes.

Project

  • The Drag and Drop has been activated on the project and work views.

Purchase

  • The backorder of supplier are no more planned. Before they were planned at the same date as the initial order. But indeed as the supplier has failed once, the best assumption is to not know when he will fulfill it.
  • The confirmed purchases are now automatically processed thanks to a cron task.

Sale

  • The backorder for customer are planned for today. Before they were planned at the original shipping date. But this date may be already in the past so it is better to try to fulfill it as soon as possible.
  • The confirmed sales are now automatically processed thanks to a cron task.
  • It is now possible to define a default invoice grouping and the default shipment grouping method for new party.
  • When the shipment cost is invoiced on order, it is now invoiced only when at least one shipment is done.
  • Consumable products are not checked anymore when the quantity check is activated on sale.

sale_payment

This new module allows to register payments on sale before the creation of any invoice. When the payments for full amount of the sale are authorized, the sale is automatically confirmed. For example, this module is used to manage payment from a e-commerce website.

sale_shipment_tolerance

This new module adds under and over shipment tolerance on the sale. If the quantity of a sale line is under shipped but inside the tolerance percentage, then the line will be considered as fully shipped and no back-order will be created. If the quantity of a sale line is over shipped more than the tolerance percentage, then a warning is raised.

Notification

notification_email

This new module adds the generic feature to send email to parties or users of document based on trigger conditions. The email can embed as attachment any report of the document. A common usage for this module is to send automatically the invoice to the customer when it is posted.

Major changes for the developer

  • The server supports to have a JSON as column type instead of TEXT column. To active it, it just require to alter the column type after the database creation. This is useful if you plan to use JSON functions or operators on the column.
  • The SQLite backend receive the alter_type and alter_size feature. This is implemented by recreating the table with the right types and inserting the old tuples.
  • The report engine, thanks to last version of Relatorio, supports Flat OpenDocument. This is useful for development as the file can be easily inspected and reviewed. But of course as it is a format not wildly supported, the result is still a standard OpenDocument.
  • Report template can now be defined as working on a single record only. This means that when it is requested for a list of records, it generate a zip file which contains each report in a separated file. This is useful for report like invoice which must be archived as unique document.
  • A new method on get_email in trytond.report allows to retrieve an email instance with the template rendered for a record. The email can be multilingual and if the template is in HTML a plain text is generated automatically.
  • The extension for plain text is now txt. This is better for guessing mimetype using the extension.
  • To improve the security the session randomness has been increased to 32 bytes.
  • The server enforces natively the size of the requests to avoid deny. The unauthenticated requests are limited to 2MB and the authenticated ones are limited to 2GB. Of course those values are configurable. Until now it was recommended to use a reverse proxy for this protection.
  • The WSGI application support more configurations (TRYTOND_LOGGING_CONFIG and TRYTOND_DATABASE_NAMES) from environment variables.
  • The changes in sequence management of the new PostgreSQL 10 showed that we should move the queries about sequence to the back-end to provide an API independent of the back-end.
  • Just like we have a descriptor on Selection field to retrieved the translated value, there is now a descriptor for the Reference field.
  • To be able to use the cache on our new drone for continuous integration, the tests infrastructure support the cache for remote PostgreSQL.
  • The XML loader was missing the possibility to evaluate datetime values.
  • Some methods can not be called with duplicated ids. But often the developer does not think about testing this requirement. In order to prevent this category of issues, all RPC calls are checked against unique ids. Also the ModelView.button and Workflow.transition have an assert against duplicate ids to detect wrong call at development stage but without having performance impact on production.
  • In order to support testing external back-end, they can register through entry points specific tests to the standard sets of tests.
  • A new generic test has been added to check that methods for Function fields are well defined on the Model.
  • The trytond-admin command has a new option --install-dependencies which allow to automatically install the missing dependencies when updating the database.
  • When updating module list, trytond-admin will also delete missing modules not activated.
  • The URI for SMTP supports two new parameters localhost_name and timeout.
  • The ModelView removes automatically empty pages from notebook.
  • The root user can behave as any company or employee.
  • The model and record name of Reference fields can be exported.
  • The sequence field can be set on proteus ModelList by using the new method 'set_sequence'.
  • As Python 3.3 has reach it end of life, we do not support it anymore, but we support the new Python 3.6.

Accounting

  • The method Move.query_get, which generate the SQL clause from the context, handles now the from_date and to_date as date range.
  • The default value of the move line has been greatly simplified. This removes potential bugs due to the complexity. And most of the features are better managed with the template move.
  • The deposit amount on party now shows a positive amount when the party has deposit.
  • All the function fields based on the MissingFunction have been replaced by Python properties. The problem with MissingFunction was that it may be triggered for the wrong record because of the pre-computation design of Tryton. The property ensure to raise error only for the needed record.

Invoicing

  • The tax sequence is now used as default values for the invoice taxes sequence.

Payment

  • An origin field has ben added to the payment. This allows to link payment to specific model like the sale in the module sale_payment.
  • The support for Stripe webhooks has been added. Some events are handled by default: charge.succeeded, charge.failed, source.chargeable, source.failed and source.canceled but more can be added easily in custom module.

Statement

  • A generic wizard which is the common basis to import statement from a file has been added. It is already used by the account_statement_coda.
  • To allow to import statement line with partial data, a new model has been added. The origin shares most of the fields with the statement line but with minimal constraint. The origin serves as basis to create lines. It shows the amount still pending to convert into line.

Commission

  • The commission plan does not match any more line for empty product.

Product

  • The service products are enforced to have only the fixed cost method.
  • The cost price has been moved from template to product. This allows a finer grain computation and still compute an average cost for the template.

Stock

  • The performance of the average cost price computation has been greatly improved. The new algorithm minimize the number of save and take advantage of the replacement of Property by MultiValue from the previous release.
  • The constraint that enforce move location to be child of the locations of the shipment has been relaxed to apply only shipment states on which the move can be corrected.

Purchase

  • In order to easily customize the address to print on the purchase, a python property report_address has been added on purchase.
  • The required constraint on the origin of a request has been dropped. It follows the doctrine that Tryton has only constraint that are programmatically needed because it eases the customization.

Sale

  • In order to easily customize the address to print on the sale, a python property report_address has been added on sale.
  • The sale price can also be computed by the price list even if no customer is defined.
  • The shipment cost price is rounded using the precision of the field it is stored on instead of the currency.

Web

  • As done in trytond, the web user session randomness has been increased to 32 bytes.
  • The email used to login is managed as case insensitive. This is the most common and expected behavior.

New Tryton release 4.4

Publié: 2017-05-01 18:00:00+00:00 release

We are proud to announce the 4.4 release of Tryton.

This release see many work to make Tryton even more customizable by reusing or improving common design patterns of existing modules, but still continues to extend the features with new modules. There is also a good effort in improving the security of the application. It contains also many bug fixes and performance improvements.

This release see the removal of the set of DAV modules (webdav, calendar, party_vcarddav etc.). Those modules were based on the no more maintained PyWebDAV library and they did not support Python 3. The side effect is that now the full server stack is Python 3 compatible.

Of course the migration from previous series is fully supported. Some manual operation may be required, see migration from 4.2 to 4.4.

Major changes for the user

  • The URL entry that was set at the button of every tab has been replaced by a button on the toolbar. The button allow to display the URL and copy it to the clipboard. This allow to have more vertical space in the client for the lists and the forms.
  • A common need, when user customize the report template from the client, is to encode the new translations. This is now very easy thanks to the addition of two actions on the report to set and synchronize the translations. A new relate button allows to open the list of all translations linked to the report. The same feature is also available for the views.
  • The desktop client used until now the security model Trust On First Use. But today with the raise of service like Let's Encrypt, it is very easy and cheap to have a valid SSL certificate but such certificate are renewed very often. So it was no more practical to use TOFU model so the client now validate the certificate of the server using CA of the system or the one configured. The fingerprint of the server is still used as check to prevent to fallback to a plain HTTP connection.

Accounting

  • The period and the fiscal year can be locked definitively. It was already possible to close them to prevent to post anything on them but it was always possible to re-open them. Some countries (like French) has a requirement to have a mechanism that can not be re-open. This is why we have added the lock.
  • The invoice sequences have been simplified. They now use a list of extensible criteria to choose which sequence to use for an invoice. This design is very flexible and allow to implement the country specific requirements very easily.
  • It is now possible to mark a supplier has having direct debit access. In this case its payable lines will not be shown in the list of lines to pay. This prevents to pay them by mistake while the supplier will issue a direct debit.
  • Often a company has only one payment journal. In this case now it will be directly filled in the payment wizard.
  • To ease the task of reviewing the account entries, the statements put the line number and description in respectively move and line description.
  • The analytic accounting has now a rule engine. It allows to apply rules when posting accounting moves without any analytics. The rules can be based on the account, the journal and the party, but of course as usual, those criteria can be easily extended.

account_invoice_correction

This new module allow to correct the price of a posted invoice line. It adds a new wizard which allow the user to select the line to correct and create a new invoice with for each line two opposite ones. This way the user can change the price of the positive line and keep the statistics and the anglo-saxon accounting correct.

account_payment_stripe

This new module adds the support of Stripe as receivable payment method. The module support many Stripe accounts, one per payment journal. It provides checkout method via browser form for payment or to register a party as Stripe customer. The processing of the payment is done asynchronously by a cron task.

Commission

  • It is now possible to use product category as criteria to match a commission plan.

Product

  • The price list has now a new criteria based on the category. It matches products that are linked to the category (standard or accounting).

product_price_list_dates

This new module adds a start and end date to the price list lines like that the price list change can be planned in advance. There is a relate from the price list to open the lines like that the user can use the filter.

Production

  • A new producible checkbox is added to the product. This allow to restrict the product that can have a BOM.

Purchase

  • The purchase price is now displayed on the product search list from the purchase line.
  • It is now possible to edit the delivery date of a purchase line. The computation from the supplier lead time is not always possible, but often the supplier can provide an accurate delivery date. So it is good for the supply planning to have a good accuracy of the planned deliver dates.
  • It is now possible to see the requests from which a purchase line was created. This gives more information to the purchaser in case he has to negotiate the quantity for example.

Sale

  • The sale price is now displayed on the product search list from the sale line. This allow the salesman to discuss the prices of similar product with the customer.
  • It is allowed now to leave the lead time of a product empty. There are cases where a company can not define a lead time for selling a product. Then the generated stock move will not have any planned date.

sale_subscription

This new module defines the basics to support subscription of recurring services. And periodically invoice them based on consumption created recurrence rules.

sale_advance_payment

This new module allows to manage advance payment on the sale. An advance payment term can be linked to a sale which will create advance invoices when it is processed. The payment of those advance payments can condition the execution of the supply and the shipping of the sale. The amount of each invoice is computed using a formula based the sale amount.

Stock

  • The shipments now record the employee responsible for some states. For example the employee who received the supplier shipment; the employee who picked and packed the customer shipment etc.
  • The internal shipment has now a request state. This allows to have similar design as for production by creating request long time in advance and recompute them as far as they stay in request state.
  • The customer shipment can have the same picking/storage location and output location. This allows to support more warehouse workflow. For example, using grouped internal shipment for the picking, this is often known as wave picking.
  • If an order point exists for a specific type (purchase, production etc.), this disable the other supply methods.
  • The internal shipments are now generated recursively because creating an internal shipment can generate a new need of another internal shipment. Now the generation is looping as long as it is needed.
  • All the different wizards that created supply records for each type have been merged into a single wizard. This allow to ensure that all supply records are created at once, leaving the system in a coherent state.
  • The order point has now a maximum quantity. If this quantity is reached by the location then the extra quantity will be shipped to the defined overflowing location.
  • Just like there is a warning on the supply wizard for late supplier moves, there is also now a warning for late customer moves. By default Tryton consider that customer moves not performed on time, will not be done and so they are no more supplied. This warning ensure the user will take care of those late moves by canceling or replanning them before computing the stock supply.

stock_shipment_measurements

This new module adds the computation of the weight and volume of the shipments and packages. This is a central place where this computation can be shared between different modules.

Major changes for the developer

  • The Property fields have been removed in favor of the MultiValue based on the MultiValueMixin and ValueMixin. The Property fields were used mainly to provide multi-company capabilities but the API is based on context attribute only which makes them very difficult to use without having record rules to ensure not mixing between company. The new API allows to get values without using context and this will allow us to remove the multi-company record rule in future release.

  • The col attribute in the view can have a negative value to create an infinite number of column. This is very useful for group that are designed to get an undetermined number of field.

  • A new domain has been added to the window action. This domain evaluation is reevaluated when the context is changed. This creates more dynamic windows.

  • All the domain computation can be override by a method domain_<field name> on the Model with until now the exception of the Function fields. This makes the API more coherent and allow to create more performant SQL query for Function fields by using for example joins.

  • Two new capabilities check methods have been added to the Database back-end:

    • has_select_for which allows to use the SELECT ... FOR to lock specific rows instead of the all table.
    • has_window_functions which allows to use the SQL window functions.
  • A better independence between the fields and the backend has been implemented in this version. This allow external modules to define new kind of fields. For example, a set of GIS fields is under development based on those improvements.

    • The fields define now which methods should be configured for RPC
    • A generic SQL type is defined by the fields and it is on the back-end responsibility to convert into its specific version.
  • The order definition for a column support the extra keywords for ordering null values. The available keywords are: NULLS FIRST and NULLS LAST. For SQL back-end that does not support the keywords, the order is converted into an equivalent SQL query thanks to python-sql.

  • The Many2One fields on ModelSQL can now target just ModelStorage. Tryton will not try to create a foreign key constraint on the table in that case.

  • A new filter attribute has been added to all xxx2Many fields. This filter is used to limit the records returned by the getter of the fields. So it is like domain but without being a constraint for the setter. This allows to replace some Function into plain fields. This review still needs to be done for all modules.

  • The cache management is automatically done now in the Transaction. This allows to ensure the consistency and integrity of the cache but also ease the usage of trytond in Python script.

  • A new security measure against brute force attack on the login has been implemented. A new max_attempt parameter in the configuration determine the number of attempt before the server answers unconditionally Too Many Requests for new login attempts. This lasts for the timeout period.

  • Some constraints have been added to the user password to enforce good security practice. Those constraints are:

    • a configurable minimal length which is 8 by default.
    • a list of forbidden password. This list is stored into a file defined in the configuration. By default there is no list but it is useful for example to forbid the name of the company etc.
    • a minimal ratio of non repeated characters.
    • the password must be different of the login, email and name of the user.

Product

  • New methods ceil and floor have been added to the Unit of Measure. They have the same API as round.

Production

  • For better accuracy of production quantities, the input quantities are ceil and the output quantities are floored. This reflect better the really than rounding the quantities.

Stock

  • The default product location uses the MatchMixin pattern now. This makes it easier to extend with new criteria.
  • The computation of the maximum lead time has been improved to be more accurate by summing all the lead times to get the biggest path possible. It also adds extra lead times like the biggest supplier lead time.

Security Release for issue6361

Publié: 2017-04-04 18:00:00+00:00 release security

Synopsis

A vulnerability in trytond has been found by Cédric Krier.

The CVE-2017-0360 allows an authenticated user with write access to report or icon definition to make the server open any readable file under any sibling folder of the trytond installation but only if starts with trytond (for example: ../trytond_suffix). This is a remaining case from CVE-2016-1242

Workaround

The sibling folder starting with trytond could be renamed.

Resolution

All users should upgrade trytond to the latest version.

Affected versions per series: <=3.4.16, <=3.6.14, <=3.8.10, <=4.0.7 and <=4.2.2

Non affected versions per series: >=3.4.17, >=3.6.15, >=3.8.11, >=4.0.8 and >=4.2.3

Concern?

Any security concerns should be reported on the bug-tracker at https://bugs.tryton.org/ with the type security.

New Tryton release 4.2

Publié: 2016-11-28 18:00:00+00:00 release

We are proud to announce the 4.2 release of Tryton.

With this release, Tryton extends its scope to tailored user applications like Chronos and also as backend for webservice. A part of the effort was put also on closing the feature gap between the web and the desktop client. The web client is still a little bit behind in terms of features but at the current rate the gap will disappear in few releases. This release contains many bug fixes and performance improvements. Polish is now an official language of Tryton.

Of course, migration from previous series is fully supported.

Major changes for the user

  • The tabs in list view can now have a counter showing to the user the number of records under them. The feature is activated by default on tabs where the number should tend to zero thus providing some hint to the user about pending tasks.

    Tryton tab domain count Sao tab domain count
  • When creating a new record from the drop down menu of a relation, the form will have the value entered in the field as default value. This helps the user fill the form.

  • The buttons can now be configured to be clicked by a number of different users before being triggered. The user can see on the button how many clicks it already received and on the tooltip who clicked.

    Tryton button rule
  • With the recent Neso retirement the database management from the client has been removed. This improve the security of the system by removing a potential attack vector.

  • It is now possible to define for each record a different color on the calendar view. This allow to group records visually.

    Tryton calendar color
  • The icons of the relation field has been improved. The experiences have shown that the old version had drawbacks which confused some users. The result was that some users thought they were searching for a new record while actually they were editing it.

    Tryton old Many2One

    As a result the editing button has now been put in on the left and a new button to clear the current value has been put on the right of the field.

    Tryton new Many2One

The web client completes its sets of functionalities in order to be closer to desktop client. The new features implemented in this release are:

  • The CSV Import/Export.

    Sao export CSV
  • The calendar view based on the FullCalendar.

    Sao calendar view
  • Support for translated fields.

    Sao translate field
  • The Favorites menu.

    Sao favorite
  • The date picker is now locale aware.

  • Add support for column sorting.

  • Support for confirm attribute on the buttons.

Accounting

  • A comparison amount has been added on Balance Sheet and Income Statement, allowing the amounts to be compared with different date, fiscal year or periods.

    Balance Sheet comparison
  • The second currency of account is now enforced, closing the gap between the documentation and the code. Thus it is possible to compute the balance of such accounts in the account currency.

  • The creation of a tax can be quite complex. To ease the process, a testing wizard has been added allowing to see the result of the computation in order to validate the definition of the tax.

Invoicing

  • The payment term is no longer required. An invoice without payment term will create a single due line at the invoice date.
  • By default, the invoice reports are stored in the database when the invoice is posted to ensure the immutability of the document. But on large setup with a lot of invoices, the database becomes very huge and this can generate on overload and a waste of space for the backups. So a new configuration option has been added to store the invoice reports in the file store instead of the database. The option can be activated on existing databases. If the report is not found in the file store, the system will take the value found in the database as fallback.
  • The process to post invoices has been reviewed in order to have better performance when posting a large number of invoices.
  • The tax identifier of the company is stored on the invoice. This is useful when company has more than one identifier registered. By default, the system will take the first one.

Payments

  • A new group for Payment Approval has been added in order to have finer grained access to the functionalities.
  • The amount to pay of the invoice is now decreased by the amount of the related payments.
  • It is now possible to block the payment of a line.
  • It is possible to configure the module to always use the RCUR option for a SEPA mandate, as this is allowed by the European Payment Council since November 2016.
  • A statement line for an existing payment will mark the latter as succeeded or failed depending on the sign when the statement is validated. This ease the management of the payment state as some banks credit the bank account first and later if the payment fails, they debit it.
  • The statement line can also refer to payment group instead of individual payment. This is useful when the bank statement contains only one operation.

Analytic

  • Many redundant fields with the account lines have been removed on the line. This simplifies the encoding and avoids mistakes.
  • A new type of analytic account has been introduced for distribution. The analytic lines will be divided when used with such account into many lines accordingly to the distribution ratio defined per sub-accounts.
  • The move line has now an analytic state which defines if the amount of the line is correctly set in each analytic axis/roots. This applies by default only on income lines. A menu entry allow to search for all lines that needs analytic correction.
  • The analytic chart enforces now the company consistency. It is no longer possible to attach an account to an axis of a different company.
  • The supplier invoice for a depreciable asset does not create analytic lines on posting. Indeed the analytic lines creation is postponed to depreciation moves.

Party

  • A more generic address design has been added. It supports as many lines as needed for the streets instead of the previous limitation of two lines. Also the formatting of the address can be configured per country and language. The formats for about 65 countries are preconfigured.
  • A common problem with referential data like party is the duplication. It is common that the same party ended to be created twice in the system. For such issue, Tryton has now a wizard that allow to merge one party into another. The merged party is inactivated to prevent new usage and the remaining one inherits from all the documents. For example, the receivable amount will contain the sum of both parties.
  • SEPA Creditor identifier is now validated and unified into the party identifiers.
  • Phone numbers are automatically formatted now using the phonenumbers library.

Product

  • A new relate from products to variants has been added in order to ease the navigation between them.

Purchase

  • As the payment term is no longer required on the invoice, the same applies also to the purchase.

Request

  • It is now possible to create a purchase request without product. In such case, a description is required and will be used for the creation of the purchase line.
  • When converting request into purchase, the requests containing the same product with the same unit will be merged into the same purchase line. This simplifies the purchase order.

Requisition

A new module for managing purchase requisitions has been added. It allows users to create their purchase requisitions which will be approved or rejected by a member of the Approval group. On approval, purchase requests will be created.

Sale

  • As the payment term is no longer required on the invoice, the same applies also to the sale.

Stock

  • A lead time can be configured for internal shipments between warehouses. In such case the internal shipment uses a transit location during the time between the shipping and the reception.
  • A relate has been added to the location to show lots and their quantities inside the location.
  • The default location defined on the product is used in the output of production. This unifies the behaviour of this feature with incoming shipments.
  • The supply period of a supplier is configurable now. Before it was always 1 day.

Package Shipping

A new set of modules has been published. They provide integration with shipping services for printing labels and store shipping references per packages of shipments.

Two services are currently supported UPS and DPD.

Carrier

  • It is possible to restrict the usage of carriers per country of origin and destination. Other criteria can be easily added. The carrier selection is already enforced by default on sales.

Timesheet

  • A Web-Extension named Chronos has been published. It allows to quickly encode timesheet entries using the new user application API (see below). The application supports to work offline and synchronises when the user is back online.

    Chronos

    It will be available soon on the different browser markets.

  • It is now possible to define a start and an end date for the employees. In such case, they will not be allowed to encode timesheet outside the period.

  • The work has be simplified by removing the tree structure. It was considered redundant with the tree structure of the projects.

Project

  • The timesheet works are created automatically from the project form. This simplifies the management of projects.

Production

  • Thanks to the new lead time per BoM and routing, start dates can be computed for productions. This allows to have a better schedule of the production needs for long running productions.

Following the work on previous versions, the production area has received two new modules to extend its functionalities:

Work Timesheet

It allows to track the time spent per production work.

Split

Similar to the stock_split module, this module allows to split a production into several units.

Major changes for the developer

  • The desktop client support GTK-3 thanks to the pygtkcompat module. The support is still experimental and can be tested by setting GTK_VERSION=3 in the environment. The plan is to switch completely to GTK-3 in one year.
  • The server provides now a way to connect URL rules to a callable endpoint. This feature comes with a set of wrappers to simplify the work of the developer like instantiating the pool of the database name found in the URL or start the transaction with automatic retry on operational error. But the more interesting wrapper is the user_application which allows to authenticate a user with a key for a specific sets of endpoints. This feature allows to create applications that do not need to login on each use. Chronos is an example of such application.
  • The translations now support derivative languages. Most of the main language has been renamed without their country code. This allowed the merge of all the Latin American Spanish translations under one common language deriving from Spanish.
  • It is now possible to configure Binary fields to store the data in file store by setting the attribute file_id to the name of the char column which will contain the file store identifier.
  • A new level of access rights has been added targeting the buttons. It allows to define how many different users must click on the button to actually trigger it.
  • It is possible to configure a different cache than the MemoryCache. It just needs to define the fully qualified name of an alternative class in the cache configuration section.
  • A new widget has been implemented in the clients for the Char field that stores PYSON expression. The widget displays a human readable representation of the expression and uses an evaluated dump of the expression as internal value.
  • The read-only states for the fields xxx2Many is now limited only to the addition and suppression of records. The target records must manage themselves the read-only state for edition. This behavior allows for example to still edit the note field of a line of a validated sale while other fields are read-only.
  • To speed up the tests and especially the scenario, a new option has been added that allows to store clean dumps of database (per module installed). A dump will automatically be loaded instead of creating a new database, this operation is way faster. Of course, the developer is responsible for clearing the cache when the database schema definition has been modified.
  • A new mixin has been added to generalize the common pattern of ordering record with a sequence field. It is named sequence_ordered and can be customized with the name and the label of the sequence field, the default order and if null first must be used.

Authentication

The login process has been reworked to be very customizable. It is now possible to plug any authentication factors without the need to adapt the clients.

SMS

The authentication_sms module allows to send by SMS a code to the mobile phone of the user that he will have to enter to proceed with the login.

Web

The module web_user is the first of a new set of module which aims to provide facilities to developers who want to use Tryton as backend for web development.

Security Release for issue5795 and issue5808

Publié: 2016-08-31 10:00:00+00:00 release security

Synopsis

Two vulnerabilities in trytond have been found by Cédric Krier.

The CVE-2016-1241 allows an authenticated user to read the hashed password of other users. The exploitation is not easy thanks to the existing protection of Tryton against such leak. Those protections are usage of strong hash method (bcrypt or sha1) and the salt of the password with random data (protection against rainbow tables).

The CVE-2016-1242 allows an authenticated user with write access to report or icon definition to make the server opens any readable file. By default, only the administrator group has such right access.

Workaround

There is no workaround for CVE-2016-1241.

For CVE-2016-1242, the modification rights could be removed to all users for the report and icon records.

Resolution

All users should upgrade trytond to the latest version.

It is recommended that every user changes his password.

Affected versions per series: <=3.2.16, <=3.4.13, <=3.6.11, <=3.8.7 and <=4.0.3

Non affected versions per series: >=3.2.17, >=3.4.14, >= 3.6.12, >=3.8.8 and >=4.0.4

Concern?

Any security concerns should be reported on the bug-tracker at https://bugs.tryton.org/ with the type security.

Translation Release for series 4.0

Publié: 2016-05-11 10:00:00+00:00 release

Due to an issue with Pootle, the initial release of series 4.0 is missing many translations. So we decided to make new set of releases with the correct translations even if it breaks rule of no database updates for bug fix releases.

If you have already updated your server to the series 4.0, you need to also update the database for this bug fix release. Sorry for the inconvenient.

New Tryton release 4.0

Publié: 2016-05-02 18:00:00+00:00 release

We are proud to announce the 4.0 release of Tryton.

This is the first release of Tryton that adds support for Python 3. The server and most of the modules support it. The missing modules are mainly the ones using the WebDAV and LDAP. The client will be ported once GTK-3 support is added. The release sees also a large refactoring of the protocol stack which was previously based on the SimpleHTTPServer of Python. Now it uses a WSGI application running on the Werkzeug server by default. Any WSGI server can be used to run Tryton, this removes the design constraint of single threaded process and opens the way for using workers. All modules have been reviewed to enforce the naming convention about the document identification. The name "code" is used for all referential documents like parties, product. The name "number" is used for the internal identification of all operational documents like sales, purchases, invoices etc. And finally, the name "reference" is used for identifications from external systems like the sale order number of the supplier of your purchase. Two new languages are now available on default installation the Lao and the Simplified Chinese.

As Richard Stallman reminded to us, the migration from previous series is fully supported.

Major changes for the user

  • The new note functionality handles the management system for general textual notes on any arbitrary model in Tryton. On click it opens a notes dialog, where the user can maintain notes. The read state of every note is managed per user. Like the attachments, the icon in the tool-bar visualizes when there are notes on a model.

    Tryton note Sao note
  • The CSV import and export has been highly reworked for a better experience. The import dialog now supports drag and drop to order the selected columns like the CSV export wizard. Both wizards are able to use any of the encodings available in Python. It is now possible to configure the CSV parameters for the export result.

    Export CSV
  • The charts provided by the graph view have been improved. Now they use softer colors, thinner lines and smaller arcs. On the background, dash style is used instead normal line for axis representation. A smart transparency value is applied for filling lines to always show through it.

  • A new button in the scheduler allows running a job once, useful to run jobs on demand or to test new settings.

Accounting

  • The report design of the General Ledger, Trial Balance and Aged Balance has been re-worked. They are now based on the new dynamic views. This provides a performance burst and allows to filter the records more precisely. In addition to the previous printable output, they also gain the CSV export which is useful to perform specific operations in a spreadsheet application.

    General Ledger
  • A date field is added to the Aged Balance, to modify the date on which the calculations are based. With this feature, it is possible to generate reports based on a past date as if it would have been generated by ignoring reconciliation that happened after that date.

  • The functionality of Third Party Balance is merged into the Aged Balance. We found that the Third Party Balance computed the same data as the Aged Balance with the type Customers and Suppliers.

Party

  • The Name field on party is no longer required for input. This solves a long standing request to be able to maintain parties where the name is not known on creation.

Product

  • A configuration form is added to the product module with these options:

    • The default value for Use Category fields.
    • The default value for the Cost Price Method.
  • It was not always easy to explain the design of products with the templates, especially when it was not really relevant for the current business. So we have redesigned both views to be very similar and indeed they use the exact same design. The fields, that do not exist on the product, are automatically replaced by the value of the template.

    Product Variant
  • The field Category is replaced by a Categories field, to support the ability of adding many categories to one product. This is very useful for example to create multi-axis categories for web shop.

Classification

This new module defines the reference basis to create different kinds of classifications for products. It adds a generic field Classification on the product form.

Classification Taxonomic

This new module introduces the taxonomic classification of products as an example using the new Classification module. It includes classifications by Taxon and by Cultivar.

Purchase

  • The field Delivery Time on product supplier is replaced by Lead Time which increases the precision from days to microseconds.
  • For each warehouse, it is now possible to define the location where the goods are picked in case of supplier return. If this location is not defined, the default storage will be used.

Request

The purchase request functionalities have been decoupled from stock_supply and sale_supply modules into a new separate module named purchase_request. This is to prepare future work that will use only purchase requests without the need of other stock_supply features.

  • A new state Exception is added to the purchase request. This is useful to manage cancelled purchase when linked to drop shipments.

Sale

  • The field Delivery Date on model Sale Line is renamed into Shipping Date to avoid any confusion.
  • The field Delivery Time on product form is replaced by Lead Time which increases the precision from days to microseconds.
  • The custom history management on Sale Opportunity is replaced by the general revision functionality of the client. This increases its precision and works automatically for any new fields.

Stock

  • The address of the destination warehouse of the Internal Shipment is now displayed on the report.
  • Now it is possible to manually do a move with the new Do button. This is useful for example to get correct accounting when you have long living productions.
  • Supplier return shipments now have a supplier and a delivery address fields. Those fields will be automatically populated for shipments created from purchase.

Production

Routing

This new module defines the routings, steps and operations for productions. A routing is a list of ordered steps and each step is defined by a generic operation.

Work

This new module completes the routing module by creating the Works of a production based on its routing. A Work is linked to a Work Center which defines the cost using one of these two methods: Per Cycle or Per Hour. The cost of a work is computed using the Cycles created on it and later added to the global cost of the production.

Major changes for the developer

  • The domains are now accepting a new parent_of operator which recursively returns all the records that are parents of the searched records. This is the opposite of the existing child_of operator.
  • It is now possible to inherit from a view that already inherits another view from a different model.
  • The new where domain operator is useful when you need to search on a xxx2Many with a full sub-domain instead of separated clauses. It has the advantage to avoid to fetch an intermediary result by using a sub-query.
  • The Transaction design has been reworked to be closer to the design defined by the PEP-0249. This new design allows to support nested transactions. It also supports multiple cursors for the same transaction, reducing the memory consumption when iterating over large result sets.
  • A new context model is introduced, to save the trouble of writing simple wizards for configuring reports by setting some values in the context. With this new design, the developer can define a model for which each field will define the values of the context. The form of this model will be displayed on top of the view and the view will be automatically reloaded when the context is changed.
  • Now its possible to have reports in plain, XML, HTML and XHTML reports. With this change the report infrastructure can be reused for example to design email templates.
  • This release adds support for the Two-Phase commit protocol which allows to coordinate distributed transactions. By default, Tryton uses a single transaction from the database back-end. But when Tryton has to communicate with other systems, it is good to use TPC to keep data integrity. The implementation follows the API of the Zope Data Manager. The data managers of the Zope community can be used within Tryton.
  • Thanks to the two-phase commit protocol now mails can be sent when the transaction is committed, so if something goes wrong and the transaction is rolled back no mails are sent.

Accounting

  • The reconciliation process now stores the date of the reconciliation. By default, it is the highest date of the reconciled lines. This allows to filter reconciled lines based on this date, for example to generate a report with the unreconciled lines before a specific date.

  • The Credit Notes have been merged into the Invoices. They are now standard invoices with negative quantities. This allows to easily group both types into a single document. The numbering can still be differentiated depending on the sign of the lines.

    Note: with the merge of Invoice and Credit Note, the signs of the taxes for Credit Note must be inverted manually.

Product

  • Uom.round is now an instance method which makes more sense according to its signature.

Purchase

  • The Purchase has received a done transition like the Sale to allow extensions to perform some action when this transition is performed.
  • It is now possible to search Purchase Requests using the Purchase field.

WebDAV

WebDAV has been decoupled from trytond into a separate module which improves the modularity of the system. Indeed many setups do not use the WebDAV so it was a little bit bloated to have it into the base. Also dependencies of this module prevented to add the support of Python 3 to trytond. So, for now, the WebDAV protocol is managed by a separated process but it will probably return in the future into the main process.

Security Release for issue5167

Publié: 2015-12-17 07:00:00+00:00 release security

Synopsis

A vulnerability in trytond has been found by Cédric Krier, that allow a malicious authenticated user to write on fields for which he doesn't have access (see issue5167).

Impact

Any authenticated user can write on field for which he doesn't have access. Other access rights are correctly enforced.

Workaround

There is no workaround.

Resolution

All users should upgrade trytond to the latest version.

Affected versions per series: <=3.8.0, <=3.6.4, <=3.4.7 and <=3.2.9

Non affected version per series: >=3.8.1, >=3.6.5, >=3.4.8 and >=3.2.10

Concern?

Any security concerns should be reported on the bug-tracker at https://bugs.tryton.org/ with the type security.

New Tryton release 3.8

Publié: 2015-11-02 18:00:00+00:00 release

We are proud to announce the 3.8 release of Tryton.

For the first time the release contains sao, the new web client of Tryton. It is the result of the Indiegogo campaign. It is developed using mainly jQuery and Bootstrap and its design is responsive. It requires a recent HTML5 compatible browser. Its usage doesn't require any modification on the server side, every modules are working out of the box with sao just like they do with the GTK client. A demo is available at http://demo.tryton.org using demo/demo as login/password. This brings to 3 the number of supported client for Tryton.

A lot of work has been done to improve the accessibility of the GTK and web clients. For the GTK client, we followed the GNOME Accessibility Developers Guide as much as possible and for the web client, we followed the Web Accessibility Initiative of the W3C. You can follow further progress on this topic on the issue3459.

And of course, this release contains many bug fixes and performance improvements.

As usual, migration from previous series is fully supported.

The following screenshots are based on sao but the same feature exists also on the GTK client.

Here is a comparison of the render of sao versus tryton:

Sao sale Tryton sale

Major changes for the user

  • The client is now able to generate meaningful error messages for all kind of validation. Those error messages use the same syntax as the search filter.

    Error message
  • For a better accessibility the custom background color on widget is replaced by 'bold' label for required fields and 'italic' label for editable fields. In the same spirit, the color of rows has been removed and can be replaced by icons.

    Label bold and italic
  • A new option for fast tabbing has been added to the client. If activated, it skips read-only fields when navigating with the tab key. This was the previous default behaviour which needed to be optional to allow users with disabilities to navigate on read-only field for reading.

  • The export feature now works only on selected records but it can export a tree structure.

Accounting

  • A new report showing the cash journal amounts over a period is added. This is useful to check closing cashier.

  • The French accounting generates the FEC (Fichier des Écritures Comptables).

  • The wizard that generates payments allows to set a date instead of the default which is today.

  • The default revenue and expense accounts can be configured from accounting configuration.

    Account configuration
  • The date of statements can be corrected after they are posted.

Party

  • The language of the party depends on the company now.

  • An extensible list of identifiers replace the field VAT.

    Party identifiers

Project

The computation of the project tree has been hugely improved by grouping the computation and use of better queries.

  • There is now a progress field on the projects and tasks and of course a total which is the sum of the children.

    Project progress
  • A new method to generate invoice from project has been added which is based on the progress field.

  • It is now possible to link purchase lines to a project which will be added to the cost field.

  • The time sheet works have now a total duration field which compute the duration of the work and its children.

    Hours per work

Sale

  • The delivery date on sale line shows the effective date once the goods are delivered.

  • It is now possible to deliver the sale to another party from the one on the invoice. This is the other side of the drop shipment which makes Tryton fully support drop shipments.

    Sale shipment party
  • The drop shipment now uses two distinct moves using an temporary drop location.

Purchase

  • The delivery date on purchase line shows the effective date once the goods are received.
  • Stock moves can be cancelled from the purchase view without having to create a supplier shipment.

Stock

  • It is possible to ask Tryton to recompute the average cost price of a product by replaying all the moves since the beginning.

  • It is possible to configure another picking location different from the storage location for the warehouses.

    Warehouse picking location
  • It is possible to set an internal provisioning per location which is used for internal order point by default for all products.

Landed Cost

Those new modules allow to record landed cost on supplier shipments after their reception. A new document is created to link supplier invoice lines with shipments and to define which method to use for cost allocation. For now, there are two methods available: By Value and By Weight. And thanks to the Update Cost Price wizard, the cost price of the products can recomputed taking into account the landed cost.

Landed cost

Customs

A new module allows to define the Tarif Code from the Harmonized System and its duty rate on the products. The duty rate is stored for a country over a period and two computation types are available: a fixed amount or an amount per quantity.

Sale Complaint

This new module is for managing customer complaint about sales or invoices. Actions can be defined to solve the complaints like returning the sale or crediting the invoice. A work flow for approval of the complaint actions is set up using the access rights.

Sale Promotion

It is now possible to apply formula based promotions on sales selected thanks to some criteria. The promotion changes the unit price of the line when the sale goes into quotation (and is restored if it goes back to draft) but only if the promotion is in favor of the customer. The available criteria are: the price list, a period, the quantity and the products.

Sale Stock Quantity

This new module checks at the quotation of the sale if there are enough quantity of products in the warehouse. It also checks that the new sale will not hurt older sale that will be shipped later.

Major changes for the developer

  • The progress bar widget works with float between 0 and 1 to ease usage as percentage.
  • The rich text widget uses now a subset of HTML to allow its implementation in sao.
  • The Many2One has a new option target_search which define the kind of query to use for dereferenced search. The options are subquery and the new join (which is the default). The join method generate a faster query in most cases.
  • The SQL constraints use a similar syntax to python-sql. This gives more flexibility to implement backend for other databases.
  • Trying to create/write/delete on a Model based on a table_query raises an exception instead of a silent error.
  • The table name of a ModelSQL can be overridden with a configuration file. This allows to work around database limitations on the length of table names.
  • The new StateReport has been added to wizards, to simplify the code of wizards that run a report.
  • The style on reports has been removed, experience show that this feature was not used.
  • The PostgreSQL backend manages now schema. This allows different instances of Tryton sharing the same database.
  • The generic foreign key to create/write user on all ModelSQL has been replaced by a rule that prevent to delete users. This greatly improves scalability in some circumstances.
  • The Property field supports now float and integer values.
  • A subdirectory locale/override is supported for modules that override translations of other modules.

Accounting

  • The charts of account are no longer translatable. Instead we provide translated charts via a template using XSLT.
  • The invoice doesn't set a unit price on the line. For this feature the purchase or sale module must be used.
  • Some fields of the invoice like the note and the origin are editable after posting the invoice.

Product

  • Conversion between units no longer results in silent failures but an explicit error is risen.
  • The volume property has been added to the products.

Project

  • The tree structure of the project and the time sheet have been separated, each object has its own one.
  • The price list uses the same decimal precision as the product.
  • The cost price of the employee is stored on the time sheet line for the date of the line. This allows to sum the costs of time sheet faster

Purchase

  • The state of the purchase request is now searchable.
  • The purchase requests are generated even if the rounded quantity is zero to allow the user to still decide to purchase more.

Stock

  • Many unnecessary restrictions on the edition of move fields have been removed.
  • The expected quantity of the inventory lines is always computed even if they are added manually.
  • It is possible to create staging and draft moves using view locations. Those locations will have to be changed to really do the move.
  • The inventory uses the grouping feature to create the moves. This allows to easily support the lot (or any other extra field).

New Tryton release 3.6

Publié: 2015-04-22 18:00:00+00:00 release

We are proud to announce the 3.6 release of Tryton.

The release shows the official support of PyPy which is an alternative implementation of Python which focuses on speed and efficiency.

As usual, migration from previous series is fully supported with the obvious exception of the ldap_connection module which was removed.

Major changes for the user

  • A new color scheme for the graphs has replaced the single brightness variance. Now the color scheme also changes the hue for each color by the golden angle (which ensure a color will not be picked twice).

    Graph color scheme
  • The dictionary widget receive completion on key searching like the other widgets.

  • The date/time widgets have been completely rewritten to be more flexible on the format to enter. But they are also more practicable when used with mouse only thanks to the real pop-up for the calendar and the drop down for the time.

    Date widget DateTime widget
  • Columns of list view that have always the same value are hidden automatically because they don't provide information. For example, the list of posted invoices will not show the state column because by definition they are all posted.

Accounting

  • It is now possible to add a description to the cancel move from the wizard.

  • A new option to only show the balance appears in the General Ledger.

  • Tax can now be configured to modify the base price for the next taxes in the list.

  • It is now possible to define templates for common moves. When running a template, the user will be asked to encode some data like an amount or a party, then an account move will be generated with those inputs.

    Move Template
  • A printable report exists now for the depreciation of assets.

  • The account charts for France and Belgium has been updated. And the Belgium one is now translated in dutch.

  • A test wizard is available now to see the result generated by the payment term. As the payment terms are quite flexible because they support to apply many deltas (instead of only one), it is not always easy to forecast the behaviour.

    Payment Term Test
  • The SEPA coverage is now extended to the pain.001.003.03 and 008.003.02 flavors which are used in Germany. And it is also possible to re-generate a SEPA message in case of wrong configuration on the first generation.

  • The statements create moves grouped by default by number, date and party. So when one statement line is split for invoice reconciliation, only one move will be created now and the origin of this move will be the group of the statement lines.

  • Tax rules can now depend on the origin and the destination country thanks to the new module account_tax_rule_country.

  • The CFONB custom (non-standard) format of SEPA is added by the new module account_payment_sepa_cfonb.

  • A new type deposit of account is added by the new module account_deposit. It allows to invoice deposit and recall later this amount on the next invoice.

Product

  • The price list can now be defined as tax included. Tryton will then compute the price without taxes based on the taxes applied.

Sale

  • A new state won was added to the sale opportunity. It goes to this state automatically when at least one of its sale is confirmed and all others are also confirmed or canceled.
  • The amount of the opportunity is updated accordantly to the amount of the linked sales. This will give more accurate reports.
  • The computation of the shipment cost is now computed only at the quotation. This lower the load on the client when the order is pretty large as the cost will be computed only once instead of each times a line is added.
  • The new module sale_extra allow to add extra line on sale based on criteria. The extra can be either a free product or an extra service cost etc.

Stock

  • There is now a relate from the product to its order points.
  • The creation of purchase request warns also on late production like it does for late incoming shipment.
  • The Shelf Live/Expiration Dates are now supported with the new module stock_lot_sled. When a lot is expired, it is no more used to compute the forecast quantity of the stock.

Commission

This new area is managed by a set of new commission modules. The commissions are created for the agent defined on a sale or invoice using a commission plan. It is also possible to define principals on the products to which commissions must be repaid.

Major changes for the developer

  • It is now allowed to have many times the same field in list/tree view.
  • There is no more a datetime widget for list/tree, two columns with one widget date and one widget time should be used instead.
  • A new field TimeDelta appears in this release to represent a duration. It replace the float_time widget which had some rounding issue. This new field is already used in the timesheet and project modules.
  • The One2Many widget can be configured to use a Cartesian product with the selections of many values for Many2One or Reference fields.
  • A method restore_history_before is added to ModelSQL which behaves like the existing restore_history but restore the records just before the datetime.
  • The on_change methods have been migrated to a behaviour more consistent with the Active Record Pattern used in Tryton. Instead of returning a dictionary with the values to change, now the instance is directly changed. This allow to chain easily the on_change methods or reuse them in other methods reducing the duplication.
  • The method save on ModelStorage is now a dualmethod which means that it can be called as usual as an instance method but also as a class method with a list of records. Saving many records at once this way improves the performance as the method will minimize the number of queries to the database and will validate the result by bunch.
  • The Dict field received a translated method to create descriptors which translate the values or the keys like the same method on Selection field.
  • It is now allowed to use the dotted notation in the order clause of a search. The ORM will automatically generate the needed joins.
  • The API of the Report class has been reworked to improve the customization of the engine. The formatting methods are now more strict to prevent silent failure.
  • The safe_eval (which was not sure to be safe) has been completely removed. In the places where the evaluated code was any way safe, the standard eval is used. For evaluated code from outside, a JSON notation is now used. Some utilities have been developed to ease the creation of JSON from XMl or in the views.
  • A new kind of button has been added which works on non-saved record. They are quite similar to on_change but they are triggered by a click on a button instead of a change of field.

Accounting

  • A new method reverse_compute has been added to Tax which allow to compute the base amount from the taxed amount.
  • The sign of the second currency amount is enforced to be the same as debit - credit.
  • The analytic account management has been reworked to use a really One2Many instead of the pseudo-field. This simplification was possible thanks to the recent new features like the usage of Reference field on One2Many.

Party

  • The vat number is now stored in its compact format.

Product

  • The number of decimal for internal price calculations is now a configuration parameter price_decimal. This parameter is used everywhere to ensure consistency between all modules.

Purchase/Sale

  • Their lines support both mixed invoice type (Invoice vs Credit Note) per line when computing the invoiced quantity.

Stock

  • A new state staging is added to the move. Such state doesn't impact at all the computation of the stock level. It is used for supply on sale, to create moves in advance.
  • Inactive products are still computed for the stock level.
  • The computation of assigned move has been improved to take only in consideration outgoing move assigned not the incoming. This result in a less optimistic for the stock level and thus prevent to assign a move with an incoming one that is just assigned but not yet done.
  • Forecasts are now automatically deactivated when their period is in the past.