We can easily define and deploy business processes. Camunda provides the tools that allow business people to design business processes. We don't have to have developers for it. It is so easy to use that our business people can go into the tool and model their business processes. We get time to do other things than just designing business processes. They are called business processes because it is the business that's driving them. So, it is better that they can design them because they're the right people to design them. The tool is great for that.

Transition-wise also, it is good. For example, if you have a defined business process with an invoice, and then for some reason, the business people decide that they want to add the business rules in their business process, they just can take the latest version of the business process, add the business rule, and easily deploy the new process to Camunda. Magically, all the new invoices will go to the new process, and the old ones will remain until all the invoices are processed. It is very easy to transition between all those business process definitions. These are the two most interesting features that Camunda provides.

The most valuable feature of the solution is that it is flexible. I want to see if the tool is good enough for my company to continue with its use or if there are some limitations. If, at our company, we are sure that it would take us to complete your business processes engineering exercise up to the level of enterprise architecture, then we would really be able to appreciate the tool. I am unsure of the product's capabilities because I am unfamiliar. I want to get someone experienced enough to suggest to me which is the best choice for a BPM tool.

The best feature related to the product is that it offers users a zero-code or no-code platform, so people can use the product without being developers or knowing Java or other microservices.

One reason we selected Camunda or Cloud/DB is that it comes with the support of the BPM notation, which helps to define processes in a standard manner. Another reason was that Camunda Cloud, as the name says, is designed for a new cloud era. That's why we went for that part. We were very early adopters of this solution. We introduced it even before version one was out. We hope that going forward, on the scalability side, we have the potential to scale the platform for future demand.

It's lightweight. It comes with a lot of flexibility, which, on the other hand, means that you have to have certain knowledge to handle features. You have the potential to change things, and it's easy to introduce new functionalities or new features to the platform. 

It's open source, which was another key factor for choosing Camunda. Its being open source helps us to understand the platform better and also integrate better with the platform.

The UI is very user-friendly compared to other products. The native, vanilla UI is very interesting and intuitive to use. It's user-friendly when it comes to modernizing a business process. 

The connectors provided by Camunda work correctly for mapping out and connecting processes. Our strategy is always to use out-of-the-box products.

It exposes a REST API that it can facilitate and make it easy to integrate with other systems.

Its flexibility stands out as the most valuable feature. I am content with its courses and the support team.

The BPMN diagram is valuable. For our use case of transferring money from one account to another, the connections have to be done in the traditional financial ways. There are a lot of unexpected errors and a lot of instability with this kind of system, and we are using Camunda in order to have clear flows. With BPMN, I can show a flow to my business partner, and the business team can easily understand what's going on. The technical team can understand what the implementation is, and we can model different errors and the process for recovering from these errors. For example, it is very common that you make a transaction, but you don't have a response from a bank. You sent the money, but the bank didn't confirm this. Such errors have to be handled because it may mean that you have to do a reverse transaction. We are able to solve a lot of orchestration problems by using Camunda. Most of them are related to payments or sending and receiving money.

The feature where you can have dynamic tables with values and actions inside the BPMN is very good when you don't have all the possible responses. We may think that the payment system is very robust, but it is not. Sometimes, we receive an error code that we weren't expecting, and this kind of solution helped a lot with that.

The integration with almost any language, product, and even human tasks, is valuable. It's very seamless to integrate into existing systems. It doesn't require you to rewrite a lot of your existing system. That's where it really stands out.

We have used a couple of connectors, including the Kafka connector a lot because we have mostly a Kafka-based architecture. The connectors are really seamless. They just fit in. They don't require you to make a lot of changes to your existing infrastructure. That's what connectors are primarily meant for, to enable enterprise-level integrations. We also build out custom connectors for our use cases.

In addition to Kafka, we can easily integrate it using any microservice or legacy microservice. All you need to do is include their library and put in a couple of annotations on your existing methods, and they can act as Camunda workers. You can transform your existing code into Zeebe components and that requires very minimal coding. We are also working on building more connectors, and that will smooth out further adoption of this technology within our ecosystem. We can orchestrate almost any remote system if it's accessible over the network and it implements any protocol. If it's reachable, we should be able to orchestrate it via the Camunda platform.

In terms of its ease of use for engineers, it's pretty easy. We have an engineer who joined us two weeks back and he has been onboarded. He's able to make changes in the BPMN. That's very important for modifying business processes.

The tool's most valuable feature is BPMN diagrams and the possibility to automate processes.

The architecture is good because it's a headless workflow. I can create my own frontend, and it's fully API-based. Our approach is more flexible, so I can use the Camunda API to generate my own workflow blueprint. 

Additionally, it's cloud-ready as we have deployed it on the Kubernetes container platform, which aligns with our cloud-first architecture. These are the aspects we like about Camunda from the IT side.

Camunda provides an easy way to integrate with the architectural environment and it offers us flexibility.  

I think that the positives of Camunda Platform are that our customers can start with the free version. I think it is the most important.

I do not recommend anybody use the free version for production without paying for a support subscription. I always recommend to use the free version only for testing and learning purposes. And I think for that purpose, it is perfect.

The most valuable feature of the solution stems from the area revolving around process modeling. It is possible to take care of the process modeling with BPMN. I think the most beneficial feature of the product is that the tool serves as a process orchestration platform and also helps in the area of process automation.

Camunda's process diagram creation and deployment is very easy. You can model the business processes very easily in Camunda.

The most valuable features are that it's lightweight, can be embedded in existing Java code, and keeps track of the workflow state and the instances that we need.

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 most valuable features are the workflow, the task list, and the modeler where we use VPN.

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

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. 

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.

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.

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

The workflow builder is valuable. The graphical interface is very beneficial. We can build whatever workflow we need. Currently, we are integrating the solution with our document management system. It acts as a repository for the documents. Inbound and outbound integrations are very easy.

The solution fulfills our implementation needs. The interface is user-friendly compared to Oracle. The solution is well-known in Egypt. Even government sectors are switching to Camunda. There are a lot of materials available. The technical team did a lot of self-study. Now, we can integrate the solution with our document management system and implement the processes we need. I rate the documentation a nine out of ten.

The ease with which I can define workflows is most valuable. The latest updates and flexibility that it provides around a task activity are interesting for me.

The collaboration capabilities have proven to be a great asset during this pandemic. We can share, discuss, and develop the model together — from a distance. It's really helped us during these times of isolation.

I love that Camunda is a very developer-friendly platform, and my customers have evaluated the pricing as reasonable. Personally, I also like that the Camunda platform as a whole helps us to easily measure the life cycle of all the relevant processes. For example, the Camunda platform includes Cawemo for business analysts, Cockpit for process engine configuration, and modeling tools for developers. Then you have Optimize, which is helpful in managing processes and continuously improving on them.

Camunda Platform is better than IBM BPM, and Azure. It is more elaborate. 

It is divided across the platform.

The integration is separated as well as the UI, and the internal work.

It also integrates well.

The headless nature of the Camunda Platform is something that has helped us to build our own logic and platforms on it.

It is simple to use. The user experience is very good.

The best feature is the automation.

Camunda supports microservices and you can do multiple things. The most important thing is that you can reuse components that you have within the product. For example, let's say that I developed a workflow for a quality review; that is a workflow that can be reused in any new process. I can just ship it, plug-and-play, copy it, and reuse all of the features and components that are there. It means that I won't be spending too much time in terms of development to put it in place. To me, that is the most valuable thing about the product.

We like the BPMN notation because it's BPMN 2.0 compliant. We like the out-of-the-box REST API features so we can build a service with Camunda, and instantly it's accessible using a REST interface, and of course, we like the REST protocol because that's much more advanced than SOAP.

The other feature that's highly advertised is the fact it's open source. We have the ability to modify the product if we need to, and that comes in handy whenever we need to add new functionality and features. One popular one is a year-end mapping feature, which is basically mapping a bunch of URLs to label in the tool, which the services can access. Instead of having to hard-code URLs, you can get the service to use the label. That is, you can configure the label in the administrator. That doesn't come with Camunda, but you can build it yourself.

The most valuable feature of Camunda Platform is its Microservices architecture, which is easily integrable with APIs.

I like the product since we are a Java-oriented company. Our solutions can be compact with Java. We found it quite useful because we can merge microservices together. It is a different kind of architecture but it is a flexible product that we can use to go live with solutions quickly.  

The features that I like the most are the drag and drop.

It is very user-friendly compared to IBM BPM. It's much simpler because it doesn't have the process admin and process inspector roles and separate pages – it's more streamlined. That means even non-technical departments can use it. 

If we don't need complex, high-level workflows but just a small form-based process, Camunda can be used by any type of client – technical or non-technical.

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 like everything about the entire BPM that comes with the BPM suite. It's more intuitive and they are enhancing the product very effectively year after year.

It's a customizable product and it's user-friendly.

There's this graphic that tells you how many lines or how many tickets are in each step. In that way, you know where you stand. I find this feature very valuable.  

These are your bottlenecks, and you can see what the tasks are, the problems, see how much time must be spent on them. Then you can propose to fix it or make some improvements to make things go faster.

One valuable feature of Camunda is that it's an open BPM, so it was easier for users and developers to work together to define the rules and define the process, given their BPM and standard architecture. This also allowed us to expose the rules and the business process itself into a standard model, which wasn't possible with other tools and softwares we've used in the past. Finally, the engine itself is lightweight so it was easier for us to handle deployments and in production it didn't have a great demand of the infrastructure.

We are using the latest version of Camunda BPM. We keep upgrading to each new release. We keep always moving with less change. There are a lot of features in Camunda BPM.

We are documenting all of the processors and VPN. Then we share it with our business users so they can approve our other process. From the technical part, what we did was exposing Camunda BPM as a web service.

We configured a split between the process and the business. If there are any changes in the business, we are changing it in the process. If there is no impact, we don't need to redeploy our configuration settings again and again. 

This was something that saved us time and improved our data center processes.

The most valuable feature is that it is easy to use. I train my colleagues and customers and I don't want them to need to learn how the solution works. I want to be the one who learns about the product and teach them BPMN. 

It's user friendly, much better than most tools I have seen.

The most valuable feature is that, with a visual system, you can try to have a process client before beginning the programming for the application. 

The most valuable features are the ease of use and the ability to streamline a process model on a BPM diagram.

We are using the BPMN engine of Camunda; we are not using the user interface. We are using just the engine, the back end of this. For us, it is working quite well.

The stability of the solution is quite good.

Technical support is good for getting alerts about bugs.

The solution is good for data models.

The number of client implementations and cross-language capabilities to support multiple frameworks is very pluggable compared to other BPM engines out there. It's also more portable than most of them. Next to being open source, the modellers are made in HTML and can be embedded in your own website with little effort.

The interface and the number of connectors that they provide are the most valuable features. The support here is kind of okay. But the main thing is with the number of connectors and the UI, the user interface.

The most valuable features are the management of internal processes, the ability to execute from design and the model for internal processes, the ability to make processes visible, and the ability to have information about the current state of each instance.

The flexibility is great. 

I appreciate the compact and clear source code.

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

I have found that this solution's applications are very competitive when it comes to some other tools, and not every tool has some front end applications for end-users. So Camunda will start with a complete application, which is quite useful, and they are ready to use directly after installation and payment. 

We are system integrators, and the value of Camunda for us is that it's easy to integrate into the products and applications we provide for our customers. The product is based on BPMN and is closely integrated with that standard. It's not complicated and generally easy to use, particularly for students and junior developers who come to learn from us as part of their studies.

Overall, the solution has been very solid.

The solution is very customizable.

We're currently using the community version, which is open-source and free to use.

The solution is stable.

The solution is easily compatible with HTML forms and HTML language programming and that is the most significant part. The data model definition in Camunda is a little complicated, so for someone with industrial engineering background it would be hard. But for someone with a computer engineering programming background Camunda is much more understandable and really easy to use.

The speed and execution of DMN was a big selling point for us. It's very good at conducting business processes that are easily modeled and presented in a way that's easy to understand. 

The most valuable feature is the ability to share the logic within the rules engine with the business, so you can put it up for everybody to read. Everybody understands what it's doing and you can make changes to it in real-time.

We found it easy to get the DMN working.

It is quicker to do things when compared to competing solutions.

I've found the active community most valuable but it also provides you with a lot of other features.

The feature that I like most is the decoupling architecture. I can use any other tools to create services and the UI, and then use them together with the Camunda BPMN engine. 

The most valuable feature is that it provides flexibility.

Also, it is easy to use. As long as you have all of the information you need on the platform, it is really not that complicated and can be used by anybody. It doesn't have to be operated by IT people.

The most valuable feature is the scheduling.

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

• 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.

It is quite easy to build a simple process without any knowledge of programming. On the other hand, if you want to customize the platform and processes to your specific use case, you also have the possibility to do that. 

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

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.