What is your primary use case for Camunda Platform?

Our primary use of ECS is to host all our services in the cloud. We work in the legal sector, and our workloads are often deployed on Fargate containers or Azure containers to abstract the hardware.

Camunda can be used in various workflow scenarios, such as policy administration systems, onboarding, account management in telecom, insurance products, policy issuance, claims management, and loan management. It is also suitable for customer service center activities where customers' accounts are created. Camunda can manage any workflow that requires customer interaction with the system. It is a competitor to other BPM solutions like Pega.

Since I completed the courses at my workplace, I have only used Camunda for testing and practice. We had assignments to create a flow for pizza delivery and another one for an electronic shop. This practice was verified by our professor.

We use the workflow only in Camunda. It acts as libraries for workflow visualization, focusing on automating my company's processes.

We use the product to automate our workflows. It is used for task management.

We use it in telecom service management to automate and orchestrate our service order flows.

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.

I worked on a project in Pakistan. For this project, I replicated processes on Camunda, including BPDs (Business Process Diagrams) and activities. Currently, I am working on the forms aspect of the implementation. I appreciate Camunda's strong SLA agreement, my current bank client required customized forms. Camunda forms are built on Angular, and I'm currently involved in a headless reporting project with Camunda. Camunda's front end is built in Angular, while I'm integrating the Java backend services. I'll consume the Java services and handle integration with Angular on the front end. When deploying Camunda, I prefer a headless approach. This means Camunda acts as middleware while the front end is built using a different technology. And back end will be from the different technology. I've integrated a database with Camunda's process engine. This allows me to generate emails and update the database as needed.

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

We use the solution for workflow processes of different sectors.

The solution is used in my company, where we deal with insurance. In our company, we use Camunda to automate our process to reduce the need for human tasks. In short, my company uses the product to reduce the need for manual work. The tool can help automate processes like insurance claims, onboarding, and other areas that are managed manually. Various processes in our company can be converted to automated ones with the help of Camunda.

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

We use it in the banking sector for a specific project. The platform aids in optimizing and automating business processes, enhancing operational efficiency, and ensuring seamless workflow management

We use the Camunda platform for workflow management.

My company uses Camunda Platform as a business process optimization or business process engineering tool.

We use Camunda Platform for automating networking business processes.

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.

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.

We use it as a task manager. Our use case is to help manage human tasks and have a workflow to which we can assign a function and some criteria to agents.

We only use the engine, and we have implemented our solution around Camunda Cloud. We have a lot of use cases. In the past, the major use case was related to infrastructure ordering. If users wanted to onboard their applications to the cloud, the whole process was run by us. They would go to the ITSM tool that we have, and from there, the whole process of onboarding the application was run by us. For example, if you required certain access, all these accesses were provided by us. So, mainly, it was related to the infrastructure processes where you order something and have to talk to AD, Exchange, or other kinds of infrastructure products and systems you have in the company.

We have an event-based architecture and Camunda works as an orchestrator for our microservices. Over the last three years or so, we have been using Kafka a lot. We wanted to bring in an orchestration engine to integrate seamlessly with our nesting system. We had a lot of existing applications that are not that old, and we did not want to rewrite software components that we own to get the benefits of orchestration. That was where there was a need. One of the factors that will decide if we will use it for more use cases at our company or not, is the ease of integration.

It is usually used to orchestrate or automate flows of interaction between our systems. It is basically for integration. For example, for a permit that needs to go through several systems, in Camunda, we have a business process that orchestrates all the steps where the permit needs to be processed. All the systems are notified of this permit, and if there are people who need to interact with a specific permit, they get notified. They can then take action. That's the kind of use case for which we use Camunda in our organization. For myself, the use case is similar, but it is for invoicing. When we receive an invoice, we need to process it. It goes through the business process. There are a lot of business rules that are applied to it. For example, we will check whether the total amount is balanced with subtotals and tax, and if that's not the case, with Camunda, we can create what's called a user task. It allows us to make an agent to take care of this invoice and fix the data that is related to it. These are the use cases that we are trying to achieve with Camunda. The goal is to clean up the invoice and make sure that the information related to it is correct so that it can be transferred to our ERP to pay suppliers. It is on-premise, and we've been able to put it in a Docker container. It is deployed in Kubernetes in our organization.

We are a fintech company located in Argentina, and most of our use cases are related to transferring money from one account to another and doing the orchestration with financial institutions. It is also used for the orchestration of all the documents for onboarding. We have electronic onboarding where you give some information about yourself, and then you take a selfie and provide photos of the front and back of your document. We have to orchestrate all this information in order to validate it with a third-party bureau of data. When we receive an okay from the bureau, we know that you are an active customer, and we can give you an account. In terms of deployment, it is a public cloud. We have Amazon Web Services running inside a Kubernetes cluster.

We use the BPMN flows for order capturing of our end-to-end customer journey. There are many intermediate flows and we mainly use the tax delegate part of it.

We're using Camunda as an SI integrator. We are currently working on becoming partners with Camunda but for now, we're customers.

We are using it for one of our workflows. We are not using the user interface per se. We are making use of JavaScript Angular for the UI. So, we're just using the engine part of Camunda. We are using its latest version.

We have multiple B2B services running for our customers. We have approximately 120 workflows and are eventually migrating everything to the Camunda Platform. We have approximately 25 workflows on Camunda currently running.

Our deployment is not live yet. We are in the process of building it. We make basic use of this solution. It is embedded within a code module that requires workflows. Essentially, Camunda is used to keep track of workflow activity. So, we're not making massive use of it. Rather, we're making use of it as an embedded microservice.

We use the free version because our organization is a consulting organization and we work normally for customers. My primary use case is for training and modeling purposes. I use the BPMN and the DMN model.

Our primary use case of Camunda is for following a process in our applications. Camunda is a work process product. We are developing some applications and when we want them to follow a specific process, we use Camunda to help the programmers follow that process we want to achieve. We are using a version of the free service they provide, but I'm unsure which version it is. Camunda is deployed on-premise.

We are using the Camunda Platform to build data models.

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.

We primarily use the solution for our clients.

Our company uses this product for the automation of core banking processes. I'm an enterprise architect and team manager and we are partners with Camunda.

It is used in the same way that Azure and IBM BPM work. We use the Camunda Platform for Banking services.

I mainly use the solution for learning purposes. I primarily use the solution in order to get a clear view of my customer, including what we are doing and what processes are being made making it easy to see everything that is happening.

We are using the product as an OAM that we have included in our software product. We are offering a private cloud solution and we sell it and deploy it to our customers. We are using it to create a low-code solution for strategic planning and performance management in order to automate the management processes such as planning, performance management, governance processes, and business process management as a whole.

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.

Primary use case is for fast prototyping innovatie processes within the social domain of the government.

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.