Today I had a presentation about camunda in our company and I highlighted the fact that Camunda is very active supporting its comunity with knowledge and tutorials … and bam! New interesting video is out! Thank you!
Awesome video! Having thoughts about KPIs when modeling business processes totally combines best of both worlds, business and operation, and is lifting the value of the model itself to a next-level. Often it even helps having a better understanding about the current state of a process by using "milestones", especially for people who are new to BPMN.
@@CamundaTeam I am just finishing an assignment for the Police forensic services in Hobart, Australia. I have some a state machine as well as business processes. The state machine finds its way into the process as you have described
I am not happy with the solution of "waiting for the bill" at about 12:50. Because after "Go to counter and remind staff about bill" the process does not end, actually it continues with "waiting for bill". Probably that was not the issue that wanted to be pointed out. But I always like complete and best way correct examples otherwise it get's confusing because sovling one tiny issue in a whole picture might have an effect on other issues.
I don't get your point. I think Niall wanted to show the simple solution and visualize how escalation can be performed using few methods. Actually If I go to the counter just to remind them about the bill why should the process stop? I think I should go back to the table and wait for bill. There could be another solution that allows client to pay the bill right away but then additional gateway should be considered I think.
In the escalation model, only the Wait to long event can be triggered in the simulation, but not the Wait for a resonable time event. Is this an error in the simulation plug in?
In the escalation model, the process does not end if the Wait resonable time event is triggered in the first step, followed by the bill arrived triggered event. A token remains stuck in Go to counter and remind stuff about bill. how can this be solved?
This could be resolved by using a terminate event at the of the process. This would ensure that after we have paid - we remove any tokens on any other tasks.
Today I had a presentation about camunda in our company and I highlighted the fact that Camunda is very active supporting its comunity with knowledge and tutorials … and bam! New interesting video is out! Thank you!
I appreciate the nice lesson and learned a lot
Awesome video!
Having thoughts about KPIs when modeling business processes totally combines best of both worlds, business and operation, and is lifting the value of the model itself to a next-level. Often it even helps having a better understanding about the current state of a process by using "milestones", especially for people who are new to BPMN.
Well done. It is good to see KPIs and boundary events being used.
Thank you!
@@CamundaTeam I am just finishing an assignment for the Police forensic services in Hobart, Australia. I have some a state machine as well as business processes. The state machine finds its way into the process as you have described
@@stevebarnesmedia Sounds like a cool project! We'd love for you share more about it in our forum: bit.ly/3ypuP97
Thanks, looking forward to the next episode!
I am not happy with the solution of "waiting for the bill" at about 12:50.
Because after "Go to counter and remind staff about bill" the process does not end, actually it continues with "waiting for bill".
Probably that was not the issue that wanted to be pointed out. But I always like complete and best way correct examples otherwise it get's confusing because sovling one tiny issue in a whole picture might have an effect on other issues.
Thank you for sharing your feedback, @debastian. We will keep this in mind when creating future content. Thanks again!
I don't get your point. I think Niall wanted to show the simple solution and visualize how escalation can be performed using few methods. Actually If I go to the counter just to remind them about the bill why should the process stop? I think I should go back to the table and wait for bill. There could be another solution that allows client to pay the bill right away but then additional gateway should be considered I think.
In the escalation model, only the Wait to long event can be triggered in the simulation, but not the Wait for a resonable time event. Is this an error in the simulation plug in?
Reporting (heatmap) is ONLY in enterprise edition 😑
In the escalation model, the process does not end if the Wait resonable time event is triggered in the first step, followed by the bill arrived triggered event. A token remains stuck in Go to counter and remind stuff about bill. how can this be solved?
This could be resolved by using a terminate event at the of the process. This would ensure that after we have paid - we remove any tokens on any other tasks.
Waiting reasonble time switcher does not work at the ed of the first part of demo
Hi htere - We're sorry to hear this. We recommend heading over to our forum where our engineers and community can help troubleshoot: forum.camunda.io/