Community mailing list archives
Re: a word of caution about base action rules / Automated Actionsby
Numa Extreme Systems, Gustavo Marino
Pre v9 workflow engine had also many issues (internal states not visible to the user, lack of proper debuging in case of troubles, a lot of issues with translations,..). A simple forward migration to the v10 onwards it is not wise in my opinion.
My 2 cents
The same situation was found with other main design choices coming from early design. At some point, only a complete redefinition was a sensible solution for the initial mess.
A reborn of the workflow engine is not a small task. Let's discuss a little about general direction before a big chunk of dev. hours (by any interested group) is spent. It could be a lot easier as a collective effort
My 2 cents
2016-06-23 7:07 GMT-03:00 Eric Caudal <firstname.lastname@example.org>:
True: the idea is to have the workflow engine and whenever we need it (for sales, or whatever) we can implement a different solution from the core
Eric Caudal [Founder and CEO]
Skype: elico.corp. Phone: + 86 186 2136 1670 (Cell), + 86 21 6211 8017/27/37 (Office)
Elico Shanghai (Hong Kong/Shenzhen/Singapore) Odoo Gold Partner, best Odoo Partner 2014 for APAC
On 06/23/2016 05:52 PM, Nhomar Hernandez wrote:
On Thu, Jun 23, 2016 at 4:47 AM, Eric Caudal <email@example.com> wrote:
I was talking about the workflow engine itself
That's the point.
Migrate the workflow engine is because we will mantain separately the specific workflow, if not what's the point?
CEO Vauxoo.Site: http://vauxoo.comTwitter: @nhomarBlog: http://nhomar.comGithub User: https://github.com/nhomar
Odoo Gold Partner
Skype: nhomar00 (Envia mail previo no lo superviso siempre).
+52 1 4773933942
Camptocamp France SAS, Alexandre Fayolle - Camptocamp