User Story (Required on creation):

In order to give our customers the same experience for Camunda 7 and Camunda 8 we compared the API's we are using (C7) to the API's available for Camunda 8.

Therefore, we figured out lots of missing endpoints and properties. 

Concepts are different in Camunda 8, we figured out that the following endpoints are missing:

• DecisionDefinition: There is an api for Process-Definitions in the Operate Api, but nothing about Decision-Definitions
• Deployment: Nothing found to retrieve deployments.
• Execution: Nothing found
• ExternalTasks: Some implementations are done at the Zeebe API, but not all our requirements are fulfilled
• History (Activity, Detail, Process-Instance, Task, User-Operation, Variable-Instance): There is nothing like History anymore. Is this included in the main endpoints or is it just not done yet?
• Sub/Super/Root Process Instances: There is currently no option to query for Sub-/Super-/Root Process Instances and it is also not visible through the API's
• BusinessKey: Not found for Message, Process-Start, Querying Process-Instances, etc.
• Tenant: Missing overall: we make another request to address this issue.

In the hints section, I included the details of our analysis. There was no approach to get 100% correctness, but it is still pretty broad.

We also have to admit, that we are a bit curious about the API-Technologies used. For every API, there is a different technology (gRPC, GraphQL, REST). Is this changing in the future to reduce the tech-overhead for each API? Also the separation.

The separation between Operate and Task API seems curious. Currently we combine process instance details with task and variable details a lot in our queries. What we would prefer is a single GraphQL API that can be used to execute such queries. As we understand all the data is inside the same (elastic search) database, this could led to better performance. Another option would be, that we use our own indexes / namespace in elastic search - in this case, the indexes used by camunda should be documented. This is a blockbox for us right now.

As discussed with Jakob Arndt we create a Feature-Request for this matter. If there is any questions regarding the content, do not hesitate to ask.

We would appreciate an answer regarding to these issues, thank you.

Functional Requirements (Required before implementation):

Technical Requirements (Required before implementation):

Limitations of Scope (Optional):

Hints (optional):

The mentioned list of our API-Calls, which we are using at the moment. Red parts are missing, green parts should work.