Community mailing list archives
Re: BPMN 2.0 as a Workflow Engine Candidateby
axxelia GmbH & Co. KG
Confidentiality: This e-mail and any attachments are confidential and may also be privileged. They are intended solely for the recipient’s use. If you are not the named recipient please notify the sender immediately and do not disclose the contents to another person, do not use it for any purpose or store or copy the information in any medium.
Vertraulichkeit: Diese e-Mail sowie alle Anhänge sind vertraulich. Sie sind allein für den angegebenen Empfänger bestimmt. Wenn Sie nicht der angegebene Empfänger sind, informieren Sie bitte umgehend den Versender und geben Sie den Inhalt gegenüber keiner anderen Person preis, benutzen Sie die Mail nicht für andere Zwecke und speichern oder kopieren Sie die hier enthaltenen Informationen nicht auf irgendeinem Datenträger.
Am 01.12.2016 um 11:17 schrieb Alaney Dória <email@example.com>:
CEO | Odoo Consultant
tm.+244 913 728 600
Não imprima este email caso não seja estritamente necessário. A Terra agradece-lhe!On 12/01/2016 03:47 AM, David Arnold wrote:
In a perfect world, Odoo 14 would support BPMN 2.0 notation in order to implement custom workflows within Odoo. Then, we could all celebrate the comeback of goodbysap.com as it would be the ultimate killer feature for large organizations.
Imagine the wealth of consulting opportunities for strong and professional partners besides developing customization modules.
Camunda, a german based company, implemented in big german names like Allianz, DB, Lufthansa, Telekom and Zalando (chapeau!) is going one step further, and if you have a thorough look at their repositories,
Mapping scripting tasks to user provided actions and service tasks to python code actions could be a start. Manual actions could be represented just as the new MRP does provide fabrication instructions and user tasks, could simply be incorporated in a task engine, as a perfectly fitting extension to the messaging app. We would automate intra-company signaling and notifications, so the whole company can be modeled as one single control pool, well BPMN 2.0 standard thinking, after all. Cron jobs become cyclical script or service tasks, automated actions become time based or other catching events. With a new build in exception handling, this feature would be no more limited to the MRP module but applicable on all company processes. And no more python code for business rules: DMN 1.1
A complete set of templates, representing the current state of workflows and differentiating between default and standard processes would complete the pack to execute process driven adaptations on time and on budget.
Complete the actual state driven reporting with a (global!) workflow heatmap and nothing can stop Odoo.