Camunda-modeler: Task description not being saved, when chosing task type
All 4 comments
For the time being this is expected behavior. The name is only saved once you finish editing using ENTER.
philippfromme
on 6 Apr 2018
I'd like to re-open this, as it is clearly a very annoying bug from the user perspective.
We've fixed a similar behavior along with appending shapes (https://github.com/bpmn-io/bpmn-js/issues/764).
nikku
on 6 Apr 2018
@philippfromme @nikku
Hey, I'd like to stress one thing, maybe this will influence your further decisions. I develop software myself, so I know there are bugs/requests that are being prioritized as low. I'm with you. That said!!!
I am relentlessly pushing BPMN in my company. And it is hard to do. And the very first thing the employees come into contact with, is not Signavio/Adonis and fancy super duper reporting features that only the Quality Department uses. No... the very first thing the get to see is a BPMN overview and a modeling tool.
In a company, there is not much room for inefficiency. Especially not if you present BPMN as a innovation, which it is. And there is definetly no room for tedious and constant model corrections, like sequence flows going in god damn circles. People lose focus if they have to deal with shitty modelling tools.
We are probably going to sign up with signavio, because it comes with great analytic features. But camundas modeller is not going away. And I've tested enough tools. I can put a total novice onto it, and it flys. We can actually concentrate a 100% on our business processes while modelling. I do not care if it doesn't handle subprocesses at the moment or is still not handling the full OMG specs. For what it does, it slams every BPMN modeller out of the shoes. And people notice that we get shit done, instead of making jokes about reoccuring usability issues.
Camunda modeler simply works.
theelectricsoul
on 6 Apr 2018
For what it does, it slams every BPMN modeller out of the shoes. And people notice that we get shit done, instead of making jokes about reoccuring usability issues.
@theelectricsoul Thanks for that compliment. We try hard to achieve that goal every day.
I'd like to state that most of the feel good factor is attributed to the underlying bpmn.io modeling toolkits.
nikku
on 6 Apr 2018
Related issues
r-n-aliev
路
3Comments
NPDeehan
路
5Comments
slizenko
路
3Comments
sebwarnke
路
4Comments
andreasgeier
路
3Comments
Most helpful comment
@philippfromme @nikku
Hey, I'd like to stress one thing, maybe this will influence your further decisions. I develop software myself, so I know there are bugs/requests that are being prioritized as low. I'm with you. That said!!!
I am relentlessly pushing BPMN in my company. And it is hard to do. And the very first thing the employees come into contact with, is not Signavio/Adonis and fancy super duper reporting features that only the Quality Department uses. No... the very first thing the get to see is a BPMN overview and a modeling tool.
In a company, there is not much room for inefficiency. Especially not if you present BPMN as a innovation, which it is. And there is definetly no room for tedious and constant model corrections, like sequence flows going in god damn circles. People lose focus if they have to deal with shitty modelling tools.
We are probably going to sign up with signavio, because it comes with great analytic features. But camundas modeller is not going away. And I've tested enough tools. I can put a total novice onto it, and it flys. We can actually concentrate a 100% on our business processes while modelling. I do not care if it doesn't handle subprocesses at the moment or is still not handling the full OMG specs. For what it does, it slams every BPMN modeller out of the shoes. And people notice that we get shit done, instead of making jokes about reoccuring usability issues.
Camunda modeler simply works.