Cawemo

We’re happy to announce our Cawemo Enterprise On-Premises 1.8.0 release. Sign up for a free trial of Camunda Enterprise Platform to learn more.

We’re happy to announce the 1.3 release of Cawemo Enterprise On-Premises. Cawemo is the BPMN process specification platform of the Camunda stack. Its main purpose is to enable all stakeholders to model and collaborate on business process diagrams. The main improvements in this release are: Call Activity Links are persisted in the XML as calledElement and better manageable through the UI. Related diagrams can be restored as milestones into the current diagram. Single milestones can be deleted from synced modeler diagrams and deployed engine processes. As a Camunda Enterprise customer, you can install or upgrade to version 1.3 following our on-premises installation instructions. On cawemo.com, these improvements are already available to you if you are on the enterprise plan. Link a Call Activity When...

With the latest release of Cawemo.com, we have added a new Enterprise feature: linking of a Call Activity to another process diagram now considers the implementation property calledElement.

We’re happy to announce the 1.2 release of Cawemo Enterprise On-Premises. Cawemo is the BPMN process specification platform of the Camunda stack. Its main purpose is to enable all stakeholders to model and collaborate on business process diagrams.

This week’s Cawemo release for both the SaaS and on-premises editions introduced new capabilities for all types of users. If you’ve already seen the presentation from CamundaCon 2019 “It’s All About People: Collaboration with Cawemo”, then you’re probably familiar with these updates–and if you’d like to see the features demoed in a real-world scenario, then the presentation recording is a great resource for you. In the rest of this post, we’ll discuss how Cawemo’s new features enable more seamless collaboration between engineers, business analysts, and everyone in between.

When I first stumbled upon BPMN back in 2007, I was taken aback. It looked complicated! I didn’t really understand the difference between a sequence flow and a message flow, and, more importantly, I didn’t think I should care.