When transforming a PlanQK Service Task to native BPMN constructs, it is replaced by a subprocess comprising three regular Service Tasks.
However, the current implementation relies on the availability of specific Java classes, which have to be deployed to the Camunda engine before execution.
This is unsuitable for usage within the PlanQK platform, thus, the equivalent logic should be implemented using Connectors as implementation of the Service Tasks.
Sketch:
The resulting subprocess after transforming a PlanQK Service Task, as well as the corresponding implementation, is shown below:
References (Optional):
The Java classes of the current implementation can be found here.
The Java files are available via: src/main/java/de/stoneone/planqk/workflow/serviceimpl
Expected Behavior:
The PlanQK service should be invoked without requiring deploying additional files except for the BPMN file.
Problem Statement:
When transforming a PlanQK Service Task to native BPMN constructs, it is replaced by a subprocess comprising three regular Service Tasks. However, the current implementation relies on the availability of specific Java classes, which have to be deployed to the Camunda engine before execution. This is unsuitable for usage within the PlanQK platform, thus, the equivalent logic should be implemented using Connectors as implementation of the Service Tasks.
Sketch:
The resulting subprocess after transforming a PlanQK Service Task, as well as the corresponding implementation, is shown below:
References (Optional):
The Java classes of the current implementation can be found here.
The Java files are available via: src/main/java/de/stoneone/planqk/workflow/serviceimpl
Expected Behavior:
The PlanQK service should be invoked without requiring deploying additional files except for the BPMN file.