Community mailing list archives
Re: a word of caution about base action rules / Automated Actionsby
Vauxoo S.A. de C.V., Nhomar Hernandez
On Thu, Jun 23, 2016 at 3:12 AM, Alexandre Fayolle <email@example.com> wrote:
I tried that approach on a customer project and I am *not* happy with it at all. The problem is that a given automated actions can only trigger once in a transaction (apparently to avoid recursion). However, a single write on a record can trigger many other writes (because computed fields are updated for instance, or because). The consequence of this can be hard to track down inconsistencies because the action fired when the first write was made but was not called again when the dependent field was updated.
Thanks for bring it up.
We basically think thank without workflow engine behind it is almost impossible set complex validation strategies at least you touch the code and overwrite almost all methods in sale.order because the technical reason of remove the workflow was left more "free" the sales flow (which IMHO think is incorrect but I understand it is a personal opinion I am not ensuring this is an absollute true).
We have very very complex workflow already edveloped in v8.0 then those instances simply will die in v8.0 (or until the last saas-X with workflow WIP our revision yet).
The approach that Fabien mentioned action related is only when simple stuf must be done but when complex stuff are present vasically you need to overwrte a lot of methods (with all what you know it implies).
I think my biggest workflows will expect until v11-v12 (when they realize this was stupid remove the workflows as usual).
I think Odoo MUST offer the proper alternative but, well which is true also is that the people that buy the SaaS and want edit a confirmed sale order for example simply do not care at all about consistency in any place, the want a fancy SpreadSheet.
If you can link here the issues related may be we can find a proper global solution in community but for the new Odoo in terms of Sales and Purchases simply it is for little users not middle-big ones with serious control flows.
Camptocamp France SAS, Alexandre Fayolle - Camptocamp