The BPMN 2.0 Specification provides the Service Task activity allowing users to invoke some application service. In this Blogpost I want to explain the difference between a synchronous and an asynchronous service invocation in camunda BPM. NOTE: this bogposts covers the topic at an abstract level. If you are looking for concrete, ready-to-use examples, have a look at our quickstart repository: quickstart on synchronous service invocations quickstart on asynchronous service invocations Synchronous Service Invocations Let’s start with synchronous service invocations.
Today we are happy to announce the new release of the camunda Modeler. This version adds official support for Eclipse Kepler. On top of that it ships with the ability to change the type of tasks, events and gateways as well as a simplified connection of elements. Eclipse Kepler Support Kepler support is finally there. Head over to the downloads site and get a fresh version of the modeler, ready for Kepler.
"I don't want to watch my camunda Tasklist all day. When there is something to do, I want to get an email containing a link that takes me directly to the respective task!" This is a typical statement by process participants (aka business users). There are numerous possible ways to implement such a requirement in your process application, e.g. using a service task: But this is not really appropriate, since it makes the process model rather verbose and therefore less valuable for business-IT-alignment.
Last Friday we had our first camunda BPM community day! It was really awesome! Thanks everybody who joined. I am really impressed that we could organize that so close after the 7.0 release and so many people already traveled to Prague just for us. I can just repeat myself: AWESOME! Today I want to share some impressions and slides with you - we recorded the sessions and hope we will get videos online soon as well.
Today we relased a new version of the camunda Modeler. It provides better property editing support for BPMN 2.0 and camunda BPM properties, improvements in pool and lane handling and fixes a number of important bugs. Property Editing Support Kristin and Roman extended the property panel to achieve partity with new engine extensions and features introduced in camunda BPM 7.0: On throwing message events and send tasks service task engine extensions may be edited On call activities passing the business key as well as all variables may be edited On call activities the called element binding and version may be specified On start events the form key may be edited independent of the event definition In addition, documentation may now be maintained for all BPMN 2.0 elements.
Apache Camel is a well known Open Source framework solving a lot of integration problems and implementing the Enterprise Integration Patterns. So combining it with camunda BPM is a perfect match: solve workflow and BPM requirements with camunda and integration requirements with Camel. Together with Rafael Cordones we took the existing Activiti Camel Module as a basis and did a huge refactoring. For everybody knowing this module I compiled the changes at the end of this article.
Once a year the whole camunda team does a ShipIt-Day (inspired by Atlassian) - developing something awesome within 24 hours. This year, Kristin, Falko and me did "camunda share" - a web application in the cloud to share and discuss BPMN 2.0 process models. And we shipped it! It is live. Try it today: http://camunda.org/share/ Why camunda share? We often discuss with colleagues, partners or customers about process models. We often send around annotated PDF files via email.
Note: this blogpost only applies to camunda BPM version < 7.1.0. Starting from camunda BPM 7.2.0 we ship Groovy as part of the pre-packaged distribution. Recently at a customer we added a ScriptTask to a process and wanted to run a Groovy script. Pretty easy with camunda BPM - but in the JBoss environment you have to know how to correctly put Groovy on the classpath - as we correctly use the JSR 223 stuff to recognize existing Scripting Languages.
We are happy to announce the first major release of camunda BPM: 7.0.0-Final. The highlights of this release are camunda cockpit: new webapplication for visual process monitoring and operations improved process engine with more flexible and better performing history (audit database), support for activity instance execution model, better clustering support REST Api based on JAX-RS Sophisticated Runtime Container Integration Container managed Threading (JBoss Threads, JCA, CommonJ), Shared Process Egnine as container managed service on all containers including Apache Tomcat.