Community mailing list archives
Re: Sale and purchase workflowby
Pedro M. Baeza
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:Regards.
- 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.
2015-09-16 10:15 GMT+02:00 Stefano Sforzi <email@example.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 <firstname.lastname@example.org>:
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.... :-(
-- Sforzi Stefano Tel (CH): +41 91 210 23 40 Tel (IT): +39 011 198 25481 http://www.agilebg.com