Camunda Reviews

The flexibility characteristic in a BPMS, through BPMN and DMN, is undoubtedly the most interesting feature for our business.

Together with a Java component we develop, where we register municipal, state, and federal holidays, we then do all SLA control during the execution of a process, avoiding countermeasures and improving the relationship with the client.

I think it would be important to internationalize the Cockpit and the Admin as well as with the Tasklist.

Another important improvement would be to invest in the creation of more types of fields in the Camunda Modeler so that you could dynamically build more complex forms, such as native type arrays, and customized arrays of objects.

We have been using it for two years.

I did not encounter stability problems.

On one occasion, we did automated tests with Selenium. After, we had a fairly large number of processes running in the engine and this slowed the performance, but did not represent a case in production.

• Lightweight architecture and scalable

• Wide coverage of BPMN, CMMN and DMN standards in both modeling and execution

• Free use as open source

• Excellent tool for modeling diagrams

• Option to get enterprise services such as service level agreement, bug fixes, patch releases and priority to request features.

Some of most important Enterprise features are process instance history, graphical interface to process instance modification/migration, heatmap analysis, decision table live editing, and access for best practices documentation.

• Knowledge management

• Replacement of manual tasks by automatic decisions

• Improvement in the speed of work queues

• Orchestration of services with more precise information

• Happy customers with better services

Navigation between diagrams directly from the shapes Call Activity, Business Rules Task, Decision Task, Case Task, and Process Task.

We have used this solution since 2015.

Even in the community versions the product is very stable and with excellent scalability results.

The lightweight architecture permits us to scale better than other traditional BPM solutions. The use of Spring Boot and Docker is a modern approach to manage this scalability and high availability.

Technical support for this solution was excellent. We received support directly from the guys next to the engineering team in Berlin.

We knew that we needed to invest in a new solution due to ROI and customer satisfaction. When selecting a vendor, we look for a good road map, scalability and a stable version.

Installing the server side is easy. Just click on Download button at the site, unzip and run. The modeling tools can be downloaded and run on premises or directly from the cloud.

Camunda and Red Hat were on our shortlist.

Compare this tool with BPM and Drools.

We are doing some development around Camunda, so it is not live right now. It is for a local government organization that wants to map some specific processes on Camunda.

I am using its latest version.

The modeler is useful for creating the flow. The way to access the data through their REST API is also valuable. This is what we're using right now.

The way to create workflows is straightforward, which is one of the major benefits of the Camunda platform.

The user interface needs some polishing because it is too technical for end-users to use it.

I have been using this solution for one month.

It has been stable so far. There is no problem with it.

We have not yet scaled it or integrated it.

We just use the forums that they have.

It took a while, but I believe it was more related to us; it was not specific to Camunda.

We're using the open-source version for now.

We just roughly touched Apache Kafka.

I would rate it a seven out of 10 because the user interface lacks in some areas.

We used the Camunda Platform workflow engine for a service eCommerce platform.

Camunda Platform has a very good interface for workflow and business process design.

When trying to design rule tables the solutions graphical user interface could improve, it could be more user friendly.

I have been using the Camunda Platform for approximately three years.

Camunda Platform is stable.

Camunda Platform is best suited for enterprise-sized companies.

We have approximately 50 people using this solution. We do not plan to increase usage at this time.

I have not needed to use the support.

We have previously used JBPM.

The installation is not difficult.

I would rate the ease of install level an eight out of ten.

We pay for the license of this solution annually.

I recommend this solution to others.

I rate Camunda Platform an eight out of ten.

One valuable feature of the solution is its flexibility. Unlike low-code platforms or those with predefined design patterns, Comunda allows for custom changes, providing the freedom to customize.

I have been working with the solution for the past six months.

The initial setup is straightforward.

I have worked with Pegasystems. Primarily, Pega operates on a case-based licensing model, where each workflow incurs charges. Many customers opt for Camunda for basic workflows and case management to save costs. However, for enterprise-level needs, especially those involving CRM functionalities, Pega is retained. Some organizations have transitioned specific workflows to Camunda while keeping Pega for comprehensive CRM solutions.

Camunda primarily functions as a BPM platform. It requires development work for customization. Users accustomed to a local setup may find it less preferable. At the same time, tech-savvy developers who enjoy extensive customization options may favor the solution due to its flexibility in adapting design models based on their preferences. For such developers, this solution would be a perfect ten.