Community mailing list archives

community@mail.odoo.com

Re: Sale and purchase workflow

by
YannickB
- 09/16/2015 07:02:08
I have to agree with Pedro here. I'm really not a fan of the workflow of Odoo and according to me it's not that easy to extend them, any change in workflow, any added step, is a pain to mantain in custom module because you also need to adapt the core function behind which change often, and I don't even want to think if you need to migrate an odoo base which has such workflow change. At the very least according to me having a multi dimensional workflow thanks to several state fields is really needed for sale.order and purchase.order, even if this will probably lead to a loss of a lot of community modules because a lot of work was put there.

That said, I hear the worry of other members of the community regarding the extensibily of function fields (They know better than me) and the migration path (but here this is the price to pay for an evolving software).
Also... We learn such important change two weeks before the v9 release? Really? We know about the changes in accounting since one year, you should have worked with the community here, like you did for stock and accounting, to avoid another flame war. I guess you were running out of time, but this is just not a way to do it.

Either way, thanks for showing that you want to take risk to make the core evolve, even if I criticize the method, this is much needed with all the flame war around Enterprise edition.


Yannick Buron
Founder
+33 (0) 6 70 74 52 26 | yannick@goclouder.net
My blog : www.disruptingworld.me/

Clouder
Building the tools we need
98 Avenue du general pierre billotte BatD
94000 Creteil
www.goclouder.net | www.wikicompare.info
Le 16/09/2015 10:57, Pedro Manuel Baeza Romero a écrit :
<blockquote cite="mid:CACSANCBzRhb4BEPZVDKOHWzu9kQGdne21sJsAi9ksOY4EkFO3Q@mail.gmail.com" type="cite">
I don't like workflows, well, not exactly, I don't like current Odoo's workflow implementation, and we were very struggled by it on the past, so at first instance, it seems a good move to remove them and pass to a fields set/methods (orthogonal) scenario. I only see one loss with this move: we are decoupling the logic to change a state from a clear condition (workflow transition condition or signal), to a more diffuse UI button availability, so this is more error prone and difficult to test automatically (are backend UI tests already available?)

We can handle this change as always we had done, but as others have predicted, it will need to be stabilized and bugs will appear for sure. I also don't mind to adapt modules for changes in core if this is for better. The increasing test coverage in OCA modules allows us to detect what is needed to change. Training people again about the flow changes is another important issue, but again we can handle it if it's for better.

What I beg you, Fabien, is that:
  • You would be open-minded this time about hooks requests. This is the first implementation and maybe you haven't tought about some hooks that can ease the extendibility of the basic flows.
  • Be also open-minded about possible behaviour refinements. In the past, multiple PRs/issues are discarded because they mean a change of "what is expected", and stability policy doesn't allow it. I agree that setting a frozen DB layout is a must in the stability policy, but please don't discard possible amendments from community if we change behaviour in this newcomer scenario, because for sure when expanding use cases we we'll find some rough edges that you can't predict.
  • Increase the test coverage for avoiding regressions.
Regards.

2015-09-16 10:15 GMT+02:00 Stefano Sforzi <stefano.sforzi@agilebg.com>:

+1 with Nhomar.

workflow is the different between erp and a simple accounting software.
We have a lot of customer the invoice from picking. I think that they will not migrate to V9.

Il 16.09.2015 09:52, Nhomar Hernández ha scritto:
<blockquote cite="mid:CAKQwv6uP=SjJGwfNnisjdo+yRVCy_vwTjTjQE08Tve6h80fPSw@mail.gmail.com" type="cite">

2015-09-16 2:34 GMT-05:00 Ana Juaristi <ajuaristio@gmail.com>:
I think this new aproach could be better (unify the way of invoicing Services) for services companies but %90 of customers we integrate are working with "materials" so they don't use periodical invoicing, or invoice from analytics. 
Just need to see the changes and evaluate the impact. I don't know if I should be really scared or delighted with this new aproach. Let's see.

See them ASAP @ana it is worst than partner problem hugely worst..... I have 2 days without sleep...

How can they do this kind of changes without make a planning is a good question..

the workflow was our shield before to avoid stuoid inconsistencies and errors.... honestly... the worst change ever.... :-(




--
--------------------
Saludos Cordiales

CEO at Vauxoo Odoo's Gold Partner.
 
--
Nhomar Hernandez
 

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe


-- 

Sforzi Stefano
Tel (CH): +41 91 210 23 40
Tel (IT): +39 011 198 25481
http://www.agilebg.com 

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe


_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe