What is your primary use case for Camunda BPM?

We have integrated Camunda workflow and decision engine into our solution that enables management and digital sales of products – Digital Product Center. We use mainly Camunda Modeler and Camunda Cockpit. For some implementations, we also used Camunda Tasklist. Camunda is used to model and orchestrate processes. We have developed a module where for selected process steps, the user can build forms that will be used to present or gather data by the end-user. Another module is responsible for defining the products, with business parameters, that an end-user will be able to buy on the platform. The link between product definition and process definition is also configured.

The primary use case of this solution is for migrating IBM BPM to Camunda.

We had a client who wanted to use a BPM to track user subscriptions on their website. They had 20 steps from different areas and different people who wanted to join as new users of their services. We had to use Camunda BPM to track those services because they used to lose track of some clients in the past. They then had to spend more, add some more steps, and add new user subscriptions for months. The key here was always to track a new user and guarantee that they will get subscribed to their service in good time.

We recently finished a proof of concept with Comunda, and it was successful. Because it's a complete solution, you can start modeling to automate processes. We can also develop projects with a high degree of collaboration, which is precious for us, especially during this pandemic when we are often isolated. Within our organization, there are roughly 20 employees using this solution.

We are a bank and use this solution for process modeling, organizing, and process architecture like line of business, and to be able to make process interfaces between each diagram. Activities include client enrollment, or a client account opening with a process for loan granting, which can't be done in Modeler. We are customers of Camunda and I'm a process analyst.

We are using Camunda BPM to schedule outbound phone calls.

We use Camunda for the automation of the workflow and business process designer. We use the module cockpit and the workflow engine to orchestrate the process. We are a consulting company and we're not doing this for internal purposes. We mostly do this for projects, and these projects are for our clients. The environment where we work is very dynamic and is changing a lot. So based on the circumstances, we mostly work on the delivery parts, as in project deliveries. At the beginning of the year, we have a clear scope, clear targets, but down the road, we face a lot of challenges where we face many dependencies. We need to constantly go around the dependencies and change things back and forth. We have a lot of experience in the development, on the ERP, and so forth. We have seen that investing in a tool like Camunda is valuable, especially because it's an open-source product. When you do the customization, you'll be enriching and increasing the automation possibility of the product. So, the value is always increasing.

We use an open-source version of this product. In some cases we install on-premises, in some cases, we install on Dockers. How we install the product depends on the use cases and the needs of the projects that we engage in. One client may be in logistics. Another client may be involved with internal communication. Another one is in retail. Some will be in business project management. We have to treat each of these to fit their unique needs.

Use cases vary depending on the client's needs. It depends on the customer. We have done a lot of flow automation for the return and authorization, like vehicle return material authorization. We have done a lot of automating their campaign systems. .It purely depends on the customer's requirements.

Our primary use case for Camunda is as a process orchestration layer to help prioritize tasks for users as they were designing downstream systems. Camunda is a way to push the rules to the downstream systems. We are partly a reseller, but we also implement and we are the systems integrator. I'm the vice president and account CCO of our company.

We primarily use the solution to run business processes that contain human tasks.

The primary use case is for modeling processes.

Our primary use case of this solution is for credit flow processes in the banking industry, like loan approval processes and so on. The solution offers good automation and it is pretty simple to build a business process. We've also tried integration with other robotics and it was feasible. Because we are partners, we currently use an enterprise edition. But sometimes we help our clients with community versions, so I have experience of both. These versions are very similar. The community version contains all the necessary features because there are only some applicable features in one of their web applications.

Our primary use case of this solution is for invoices, receipts and purchase orders. There is no specific line of business but we basically use it for some main processes that we want to be automated.

Our primary use for this solution is to create a rules-based API. We are using the BPMN Model to build a rules engine. We are running a development server running on Azure, and an on-premises version running for the client.

I mainly use it in investment banks, in workflow management. For example, the onboarding can be from one box. So when the client comes, the sales guy would collect the documentation. Then there would be another task, and someone would be reviewing those documents then upload those documents into some other third party application. This is just one example but we have a lot of complex use cases.

We're planning and exploring moving to the Enterprise Edition. We find some functionality for the migration to be helpful for us. This is why we might move to the Enterprise Edition.

This solution enables the development team to quickly create prototypes and put them into production.