Cawemo Enterprise (SaaS) Release: Process Linking for Call Activities

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.

Link a Call Activity

When you add a new link to a Call Activity, the process ID of the child process is written to the calledElement attribute of the Call Activity. Assuming you would export both diagrams as BPMN 2.0 XML files and deploy them to the Camunda Engine, then the processes would already call each other correctly.

Showing links to the child process diagram

See all linked parent processes

In Cawemo you can now also see all other process diagrams that would call the given (child) process. We offer an easy list of all such diagrams next to the specification text of the process.

Showing links to the parent process diagram

Since multiple process diagrams can share the same process ID (e.g. when you have multiple variants of the same process within Cawemo), we do show all diagrams at the linked Call Activity or in the list of parent processes. Jumping between these diagrams is now just one click away.

See all links automatically for imported diagrams

By using the process ID, we automatically add links to imported diagrams where we read and match the calledElement attribute. This way, you can simply import all your process diagrams to Cawemo and get an easy overview of how your processes are calling each other.

Cawemo Enterprise (On-Premises)

This feature will be available to Cawemo Enterprise (On-Premises) users with the next on-premises release. It is not yet part of the current 1.2 version of Cawemo Enterprise (On-Premises).

Share your thoughts

We love being in touch with our community!

As a user in https://cawemo.com, you can send us a direct message through the “Provide feedback” form. We are also active in the Camunda forum and on twitter @Camunda.

If you are interested in the Enterprise plan of Cawemo, please reach out to us via the contact form on our website.

  • Spring Boot Starter for the External Task...

    We are happy to announce that Camunda Platform Runtime 7.15 will provide a Spring Boot Starter for the External Task Client. It allows you to implement Service Tasks decoupled from the Process Engine using Spring Boot. In seconds, you can build an executable JAR that can run almost anywhere. In 2018, Camunda released the first version of the External Task Client. Since then, our community member Oliver Steinhauer developed a Starter that combines the External Task Client with Spring Boot. With the 7.15 release, we will add the former Community Extension to the official Camunda Stack and will maintain it as part of future product releases. Let’s look at the following example to get a better understanding of the Spring...

    Read more
  • The Zeebe Community Welcomes Camunda Cloud

    The Zeebe Community Welcomes Camunda Cloud!

    The Rise of Camunda Cloud Whether you’re a current Camunda Platform user, interested in our open source software, or simply poking around our blog as a result of a tweet you saw from someone in our community, you may have noticed an increase in the number of times you’re seeing words like Camunda Cloud, SaaS, or Zeebe pop up over the past few months. As you may know, we first released Zeebe, the source-available, community-supported workflow engine, in 2017 (read the history of Zeebe in our CEO’s words). Since then, in addition to creating an amazing enterprise product with Camunda Platform, we’ve been listening to your feedback on Zeebe as well as Camunda Cloud, working hard to build a SaaS...

    Read more
  • Camunda Cloud 1.0.0-alpha2 Released

    We’re excited to announce the release of Camunda Cloud 1.0.0-alpha2, which includes Zeebe 1.0.0-alpha2 Operate 1.0.0-alpha2 Tasklist 1.0.0-alpha2 Updates in Cloud Console How to get it In this post, we’ll highlight some of the new capabilities introduced in these alpha releases. Zeebe 1.0.0-alpha2 The Zeebe team continued its work on getting ready for the 1.0 release and improving many internal components of the workflow engine and its underlying infrastructure. Nevertheless, the alpha2 release already provides an improvement for users of the Java client. The Java job worker implementation now offers a back-off mechanism if the Zeebe service is not available. Before the job worker continues to poll the unavailable service continuously, the job worker will apply an exponential back-off strategy...

    Read more