Camunda Reviews

The majority of my research work pertains to financial organizations, specifically, credit processes, loan origination, and appraisal of loan decisions. The majority of my clients are financial institutions.

Having knowledge of the BPM and monitoring process has proven to be very beneficial, as I am currently engaged in documenting processes for Clientele. 

The BPM has been of real help because I'm knowledgeable about the BPM and monitoring process. I've been in the process of documenting processes for Clientele. 

Although I have acquired knowledge about process automation, I am facing a challenge in implementing it for one of my clients due to various reasons such as some of them still using legacy systems or undergoing changes in their core banking software. However, I am eagerly looking forward to the opportunity to implement a process automation solution for one of my clientele.

The primary issue regarding the Camunda platform is its high cost of training. This is why I haven't discussed it extensively, as compared to other products that are more affordable in terms of developer training.

For instance, if I were to compare a Process Maker who provides free training with UiPath, which is also free, and then with the Camunda Platform, the latter requires payment for its services and verification procedures. The amount charged by Camunda is quite substantial and not negligible.

As you can see, I am unable to carry out any implementation without having received prior training, and this has been a major disadvantage of using the Camunda Platform.

I would like to see the pricing improved.

I have been using the Camunda Platform for approximately a year now.

I am working with the community edition. 

I am not aware of the version that we are using, but I don't believe that it is the most recent version.

I haven't had the opportunity to test the solution in an actual working environment yet, as it seems that you haven't deployed it either. Although I have used a modeler extensively, I haven't been able to deploy a solution to a client, so I can't speak to its stability.

It is my understanding, that the solution is highly scalable, but I haven't had the chance to test its scalability. 

I haven't encountered any issues with the solution crashing, so I don't have any experience in troubleshooting such problems. 

However, I'm willing to experiment with the different versions I have and try to find a solution if any issues arise. 

We currently have three users.

Our original plan was to implement this solution for a client. However, I found it challenging to promote the product without having the necessary technical expertise to modify the code in certain areas. I had to go through additional training, which, as I mentioned earlier, was a disadvantage since it made me hesitant to deploy the solution in a financial institution.

I don't believe I have the necessary accreditation or certification to deploy the solution. I haven't undergone the required training or been formally verified as competent in this area.

I haven't reached out to technical support since the community version doesn't offer it unless I seek assistance from the forum.

Setting up the software development process is not difficult for me because I am knowledgeable in this area.

Since the process is mostly Java-based, there is no need for me to do any training. However, the aspect of training poses a challenge due to its high cost.

The initial setup was straightforward. That was what I was able to accomplish. 

It took me approximately two to three hours to complete the task. I had to refer to tutorials and make some adjustments on my computer, which consumed some time. As a developer, I found the task relatively easy to handle.

I deployed it. But it was not a major inconvenience for me. It was deployed a year ago.

In Africa, the cost of deployment is an important factor to consider since it adds to the overall cost. This might be the only drawback to using it.

Licensing fees are paid on a yearly basis.

It's an expensive solution.

Having learned about BPM, I gained valuable insights from one of the key contributors to the ONG group, a prominent founder of the organization who is also involved in the development of Camunda. Based on my experience, I would strongly suggest this solution to anyone seeking to implement a robust Camunda Platform.

My recommendation is to ensure proper documentation of the initial processes. This is because one of the challenges faced by our clients is the lack of documentation for their processes.

The challenge lies not only in defining policies but also in documenting end-to-end processes. During the documentation process, it becomes apparent that some knowledge is retained by individuals rather than being stored in a centralized procedure. 

Before considering automation, I recommend prioritizing process documentation. This ensures that all critical information and expertise are centralized and easily accessible, resulting in a more successful automated implementation.

I would rate Camunda Platform a six out of ten.

We use Camunda to automate business processes.

The most valuable features are the workflow, the task list, and the modeler where we use VPN.

An improvement would be to support Angular 2 instead of AngularJS, which is quite old. I would also like Camunda to provide support for migrating to the new version so that my processes migrate without any problems.

I've been using Camunda for almost six months.

Stability-wise, Camunda is good, but sometimes task queries get very slow when we have a large number of tasks.

The scalability is quite good, we've had no challenges with it.

The initial setup is quite easy - I set it up in 30-35 hours.

The license is quite expensive, which is why we went with the community version.

We chose to use Camunda because it's open-source, easy to develop, and scalable, plus we were able to develop some of the enterprise features offered with the license in-house only. I would definitely recommend anyone thinking of implementing Camunda to try it out, just bear in mind that when the number of tasks increases, you need to write your own queries and that you need to keep the number of form variables low because performance decreases when it gets higher. I would rate Camunda Platform eight out of ten.

We used the solution in quite a simple manner. We were disappointed that the dictionary was missing. The hierarchy could not be shown, defined, or structured the way we like. We did not use all the features. I have used BPMN Modeler.

Camunda is really useful. That is why my colleagues and I use it in the company. The solution is useful for small projects.

The product does not have a dictionary. The tool must enable users to build or design sub-processes. It must provide a more convenient and easy way to define sub-processes.

I have been using the solution for five years.

The tool is always stable. We have no troubles. I rate the stability an eight to nine out of ten.

I rate the tool’s scalability a five out of ten. We have ten users. The product is used once or twice a week.

I rate the ease of setup seven to eight out of ten.

We use a community version.

All the business process management tools are quite similar. We have to get used to each application's individual ideas, thoughts, and intentions. We use BIC for our organization and Camunda for the projects. It is easier to use Camunda for small projects. Signavio is also a competitor.

It's not possible for us to define a process as deep as it is necessary to automate it. We tested but did not use DMN capabilities. I will recommend the solution to others. I just finished studying business process management. Overall, I rate the product an eight out of ten.

We use the solution for various application workloads, including the workflow for account management applications.

Process BPMN is an important feature where you can write your code.

The latency of API could be decreased.

I have been using Camunda for two years.

The product is stable.

The solution does not have high scalability. It can be useful for complex types of projects.

I rate the solution’s scalability a seven out of ten.

The initial setup is difficult to adapt. It takes two to three days to complete.

Camunda has saved around 30-40% of developers’ time, increasing their productivity.

Overall, I rate the solution a nine out of ten.

We have implemented it for an existing production application called Click End Connect, which is used for Orange Shops. Click End Connect allows users to view available mobile devices, select the shop that best suits their needs, and collect the chosen device within two hours without having to wait in the shop. The application handles stock verification and ticket collection processes seamlessly.

We have the Camunda Platform's cockpit, which is a key component of the Camunda Platform. By utilizing the Camunda cockpit, we can define stages and collect valuable data, including key performance indicators (KPIs). This allows us to identify areas of weakness that can be improved upon. 

The BPM (Business Process Management) cycle follows a pattern of collecting data, making improvements, executing processes, and then continuously refining them with the input of the entire team. The Camunda cockpit serves as a powerful tool provided within Camunda Platform. It acts as a dashboard, offering all the necessary information and key performance indicators required for effective monitoring and decision-making.

The most important thing about Camunda is that it's open source. It's a tool that is tuned to our pro profile concept, which suits our preferences and project needs. It's been really beneficial for us. 

The connectors available on Camunda Platform have responded to all our requirements, such as sending emails, and SMS, making web service calls, API integration, and handling show requests. 

Additionally, we were able to connect it with the Docker platform, allowing us to use containers that meet our performance needs. 

There is something that could be improved, particularly the availability of a drag-and-drop front-end tool for the workflow designer. When building interfaces, there are limited tools to work with, especially when dealing with different types of tasks, such as user tasks and system tasks. It would be beneficial to have something like the latest version of Ondula, which offers more flexibility and ease of use.

I've been using Camunda for five years now. We collaborated with a company called Schema in Paris, which provided us with support when needed and integrated closely with us. Camunda was the first product we put into production, and it has been quite successful.

We are currently using the seventh version of Camunda. We haven't upgraded to the eighth version yet. However, we are studying the possibility of migrating to the new version, especially the cloud-based variant with DB platform integration, among other features.

It is a stable solution if you have a properly configured server, regardless of the server type you are using (e.g., Apache, Nginx, or others), Camunda remains stable. 

As long as you have a good configuration, you shouldn't face any significant problems.

It is a scalable solution. We use four containers for our production environment. It is scalable and easy to maintain. 

We haven't encountered any problems with scalability during both the testing and deployment phases.

It is not overly complex to set up and implement if you are already a Java developer. For Java developers, it is quite straightforward and manageable. 

However, if you are, for example, a PHP developer or someone working with a different technology stack without Java skills, it may be a bit challenging to get started with Camunda. In such cases, I would recommend seeking assistance or guidance.

Camunda is a highly documented platform. I really appreciate that aspect. When I started working with Camunda, I made sure to read all the documentation for the APIs and other related information. It's a well-documented tool.

The deployment process utilizes DevOps practices. We make use of tools like Docker, which are suitable for various platforms and easy to use.

The deployment usually takes around five minutes. This includes steps such as packaging, configuring the environment, installing the application, and allowing the server to start. The entire procedure is completed within five minutes.

Moreover, it can be managed by a single engineer or developer who has experience with CI/CD, DevOps platforms, Docker, and related technologies. 

Although not a junior developer, one knowledgeable person can handle the deployment process. In our case, we had one individual who handled the deployment for us, and for subsequent applications, each of us was responsible for maintaining our own application.

There were some features that were only available in the paid version, not in the community version we used. For instance, we implemented an interface ourselves to view the history of our process instances because the historical data functionality was not accessible.

It is available, but it is part of the enterprise edition, which requires a paid license. We didn't have the option to purchase licenses as we migrated to open-source tools. 

So we had to customize our interfaces and tools using the Camunda API to replace the functionality found in the enterprise edition. That's how we managed it.

We have compared Camunda with the Bonita platform, and Camunda came out as the preferred choice in terms of features and functionality.

I recommend developing their expertise and skills with BPM. They should have a deep understanding of architecture. Starting with good releases is important because it allows users to become familiar with powerful tools and solutions. 

If you encounter a real problem, it is crucial to have a well-configured environment, whether it's a web server or any other production platform. Implementing BPM with good practices and optimization is key. 

Overall, Camunda can be a powerful tool to work with when used in an optimized and well-implemented manner.

Overall, I would rate Camunda Platform an eight out of ten. 

We ran two proofs of concept, but it was on internal processes. Both processes were related to the human resources area. Right now, the IT central area is working on a service to optimize using Camunda.

We use the community version, and we use Cawemo Platform to start modeling and involving the areas. We pass the models to the IT central area, and they go on with the job. I work for the government of my state. I work in a central area, and we work with BPM, so we were trying to find a solution for automatization. That's when we found Camunda.

We are trying to transition the environment and trying to see the use for it in the future, but right now we are running one project specifically.

When we ran our first proof of concept, we had some aid from an external company called Memora, which is a representative here in Brazil. They have high-quality technicians. The first project was really a success.

We don't have specific key users because we are trying to understand how to use the solution in order to provide public services for the citizens of our state. They are solving some technical issues and trying to integrate the solution with our internal IT environment.

The idea is using the community version in order to provide public services, but not all services, because we have a traditional program system development. They are considering buying a local tool, and they are considering Camunda Platform.

We are using the newest version of the solution.

We like the idea of working with Cawemo because it enables us to keep on working, remotely or not. It allows us to collaborate between areas. It's easy to model and easy to use. It's a great tool for communicating at the beginning of a project.

The business model could be easier to understand.

We started using Camunda at the beginning of 2020. We started researching and using the Cawemo solution for modeling, getting the idea, and knowing the environment. That's when we decided to run a proof of concept. It happened in the middle of 2020.

During 2021, we had some issues concerning coronavirus, so things stopped for a while. Right now, the central area responsible for IT restart is considering running another proof of concept on Camunda.

It is stable.

The solution is scalable.

I tried to get some information about buying the license for the solution, but I found it kind of hard to understand the business model. That's why we're currently using the community version.

I would rate this solution 10 out of 10. 

My advice is try to understand and use it because it's really an amazing solution. I only have nice words to say about it. I really hope our central IT area runs this proof of concept, and that it becomes successful in the near future so that we really start offering public services on Camunda Platform. It's easy to use, stable, it integrates areas, and you can use the community version.

We are currently concentrating majorly on our clients in telecommunication. We are also working with new and existing federal clients and proposing Camunda Platform to them.

We are using its latest version. We are currently in the development phase. It is in our local environment, but we are planning to be cloud-based. Going forward, we will create a Jenkins Pipeline and deploy it onto the Azure cloud.

It is open-source. It supports microservice orchestration. This is what we are really interested in. We can customize our products depending on the use cases.

They have a migration plugin that can be used to migrate from one BPM to another BPM. It is in the beta stage since last year. If they can make it available in the market, it would be great. We are going to have a couple of migration projects for migrating from IBM BPM to Camunda, and this plugin would be useful. I have already discussed this with them two weeks ago and asked them to look into this and add it as a feature. We are expecting this plugin to be available in the next version. This is the only requirement we have at present. They keep on coming up with different features, which is helping us a lot. Its latest release that came out last month was awesome.

I have been using this solution for five years.

It is stable. I didn't face any issues in the production or development phase.

I have interacted with their technical support, and they are very helpful. When I have to work on any POC, I also directly work with the product team.

Its initial setup is straightforward.

I would advise others to verify the technology stack that they already have in place. They should check the orchestration part and see if they need to take care of any redesigning.

I would rate Camunda Platform a nine out of ten.

We use the product to automate business processes for our clients.

Camunda's most valuable feature is its ability to integrate with different products.

They could provide more documentation regarding the integration of different programming languages. We encounter challenges finding recommendations or online documents while developing processes.

We have been using Camunda for more than five years.

I rate the platform's stability a nine out of ten.

The platform is more suitable for medium companies. Enterprises might need more automated and customizable solutions. I rate Camunda's scalability a nine out of ten.

We encounter challenges in finding examples for particular programming languages. Apart from that, the technical support documentation is good.

Positive

The setup process is easy. It was the primary reason to opt for Camunda.

The product is expensive for a small or medium-sized company. I rate the pricing a two or three out of ten.

Setting up or translating business processes using the Camunda platform is easy. It provides flexibility for integrating with different third-party systems. We have implemented the product to optimize internal business processes and improve API communication between different units.

I rate it an eight out of ten.