Community mailing list archives
Re: a word of caution about base action rules / Automated Actionsby
- the initial problem description about undesired side effects,
- a interim relief by maintaining workflows at least until v10
- the call for improvement of the existing workflow engine
- the hint to tryton's solution
as for design a combination of tryton's solution with the well known @depends() decorator could be worth a line of thought. The "why" is based on the following assumptions.
Asumption 1: depends() does not expose the undesired external effects which come with obscure writes in dirty fields, which are not handeled correctly by automated actions (yet). (Alexandre's Case Description)
Assumption 2: declare the transition field as a class attribute is indeed mimicking the current aproach of the magic 'state' field, but joining a dictionary of allowed transitions would bring back some of the desired control flow.
Assumption 3: The @workflow() decorator could hook a custom method into a better implementation of some/all of the mentioned improvements about ACL for example, once those are gathered and duely explained in a comprehensive document.
Please make sure you put some effort
on understanding this approach, as only refutating the core weeknesses of this approach (as in Grahan's Pyramid of refutation) are most useful, for what it's worth promoting towards solution. ;-)
Thanks for the clarification Fabien, but this is besides the point I was making before this thread was hijacked... Alexandre On 23/06/2016 15:49, Fabien Pinckaers wrote: > Workflow engine will stay in Odoo 10. > > On 23 Jun 2016 01:42, "Dominique KON SUN TACK" > > wrote: > > Do we know if the workflow engine will survive in v10 ? > > *Dominique KON-SUN-TACK * /[Project Manager]/ > *Elico Solutions *(Singapore/Shanghai/Shenzhen) > > /*Odoo Gold Partner, best Odoo Partner 2014 for APAC*/ > /* > */ > Mobile: + 65 8502 2399 > Skype: dominique_elico > Email: email@example.com > <mailto:firstname.lastname@example.org> > Website: www.elico-corp.com> > On 23 June 2016 at 16:32, Nhomar Hernandez <email@example.com > <mailto:firstname.lastname@example.org>> wrote: > > > On Thu, Jun 23, 2016 at 3:12 AM, Alexandre Fayolle > <email@example.com > <mailto:firstname.lastname@example.org>> 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. > > regards. > > > -- > Nhomar Hernandez > CEO Vauxoo. > Site: http://vauxoo.com> Twitter: @nhomar > Blog: http://nhomar.com > Github User: https://github.com/nhomar > Odoo Gold Partner > Skype: nhomar00 (Envia mail previo no lo superviso siempre). > HangOut: email@example.com <mailto:firstname.lastname@example.org> > Móvil Venezuela: > +58 4144110269> Móvil México: > +52 1 4773933942> > _______________________________________________ > Mailing-List: https://www.odoo.com/groups/community-59> Post to: mailto:email@example.com > <mailto:firstname.lastname@example.org> > Unsubscribe: https://www.odoo.com/groups?unsubscribe > > > _______________________________________________ > Mailing-List: https://www.odoo.com/groups/community-59> Post to: mailto:email@example.com <mailto:firstname.lastname@example.org> > Unsubscribe: https://www.odoo.com/groups?unsubscribe> > _______________________________________________ > Mailing-List: https://www.odoo.com/groups/community-59 > Post to: mailto:email@example.com > Unsubscribe: https://www.odoo.com/groups?unsubscribe >-- Alexandre Fayolle Chef de Projet Tel : +33 4 58 48 20 30 Camptocamp France SAS Savoie Technolac, BP 352 73377 Le Bourget du Lac Cedex http://www.camptocamp.com
Camptocamp France SAS, Alexandre Fayolle - Camptocamp