Areas that have room for improvement in Camunda include the user interface. We moved from Camunda 7 to Camunda 8, and previously we had Camunda 7 Cockpit, and now we have Operate. The UI of Operate is less user-friendly. It may be a little more modern, but it is less user-friendly, so some insights are missed. The UI could be improved. Another topic is something that should have been recently solved in Camunda 8, but in Camunda 7, we had a case management system based on Camunda, and we had our own identifiers in our system. It was easier in Camunda 7 to link these identifications, the business identification to the process identification, and in Camunda 8, this was not implemented until the 8.10 release. We really missed that feature, as it made it very difficult to embed and especially for debugging. The combination with the new Operate instead of Camunda 7 Cockpit made it difficult to find specific running processes. The maintenance of Camunda is somewhat complex. Recently, we had to move from 8.8 to 8.9 or 8.10, and everything was broken, which cost us a lot of time to repair and revert. The complexity is particularly evident because of the architectural changes Camunda made when moving from Camunda 7 to Camunda 8. It took about three years to make Camunda 8 mature, and sometimes it seems they realized they made a wrong decision by switching to a completely different approach. It is not just a matter of pushing a button and installing it; it has a bigger impact than expected, which is indeed one of the downsides we recently faced. The ability to observe and control processes at runtime, related to Operate, rates at a six in my assessment, so that could definitely be improved.
