Community mailing list archives
Re: What happened to workflow in Odoo 9 ?by
Akretion, Raphael Valyi
old topic... Well I hope the transition will be smooth enough. In the meantime, be picky and don't ask the workflow engine too much...
But you know, this is sadly exactly what happen when a software editor tries to re-invent the wheel internally. Tomorrow the same will probably happen with qweb or the Odoo CMS... In fact may be you can use these shiny features when by luck they already fit your use case, but you cannot capitalize on such open source (telling all of Odoo is bad, there are good parts certainly with no alternative coming even close).
Now, I would like to remind the case of Spree Commerce. Spree is not an ERP, it's just an ecommerce but still a few years ago they wanted to better abstract their checkout engine, so they integrated a "BPM engine". With modern languages, a state machine engine should be a commodity now: it should be well enough coded and cost almost nothing to maintain and should be done in a community way. In the older Java enterprisey times, may be that wasn't true and things like JBoss or ProcessMaker were done: complex things so complex that they have their own crappy business model of their own that survive just because fortune500 still burn money on such consultant-ware...
So in the case of Spree they took a minimalist approach instead, they are using that state machine lib:
this is a state machine for Ruby objects with roughly the same scope as Odoo engine, but better coded and used by many...
And they use that additional layer which adds support for ActiveRecord persistence https://github.com/state-machines/state_machines-activerecord (the standard persistence layer in Ruby).
I'm not sure if Python has equivalent modular state machine libraries, but I think it's the right strategy. Well at least use a state machine lib that is NOT maintained only by Odoo SA/community. In general this is what is wrong with Odoo: the lack of synergies with other open source projects. Open source is a hard model, one cannot make it without such synergies. If these synergies are missed, if the programming language is not modular enough and make them harder to happen, then Odoo SA should maintain it all, then it costs them $$ and art the end they are trapped in the proprietary spiral where despite temporary illusions the system fails to be cheaper than proprietary software.
As long as Odoo has this NIH problem, my strategy is to use on a minimal scope where hopefully it consolidates overall. By no mean increase its scope like to the web for instance, because the same problems will explode just orders of magnitude larger.
To be followed...
On Tue, Dec 29, 2015 at 9:17 AM, Cocopapa <firstname.lastname@example.org> wrote:
Actually you should have a look on those prices too!And as Odoo promotes the one solution for all approach why should it benefitial to give customers back what they had actually before Odoo. 3- many applications only to achieve the same goal like they could have already right now with the stuff which is in Odoo community edition - if it stays in there and perhaps get improved a bit.It is no real solution processmaker for people who use AGPL Opensource
- No patch upgrades available for migration to new releases
- No software fixes or patches provided
- No workflow templates
- No enterprise features
- No support or indemnificationThis actually shows that Processmaker again is actually only a worm on the fishing root to get hold of big paying customers and glue them on the enterprise red carpet like Odoo is trying to do it to more and more.The sense of Open Source Software seems to be gone unfortunately.Looking to our customers they would prefer an integrated workflow instead of an external solution!