Hi! We are using the latest version of Camunda 7 and would like to now whether it is possible to create contracts (similar to OpenAPI specifications) for service tasks?
We face the problem that with a growing number of processes and a growing amount of Service Tasks inside them, we loose track of the different variables a certain Service Task requires, as well as the variables it creates inside our Java Code. Finding this information is a difficult and tedious task, since we have to manually inspect the Java Code of every Service Task in order to find the affected variables and their types.
Especially when modeling a process, we would like to know which variables a certain service task needs and which variables it creates.
We’ve stumbled upon the possibility of creating templates for Service Tasks, this solution though lacks the ability to specify the exact structure of a variable (e.g. the JSON format of the variable). It also lacks the ability to specify output variables and their types. Furthermore, the template is non-binding for the ExternalTaskHandler we use in our Service Task Java Code, hence making it difficult to keep it consistent on both sides.
So to sum up, is there a way to create contracts (i.e. something similar to OpenAPI specifications) that would enable us to enforce certain rules inside the modeler as well as the ServiceTask’s external Java Code?
Best regards