-
Type:
Task
-
Resolution: Unresolved
-
Priority:
L3 - Default
-
None
-
Affects Version/s: None
-
Component/s: engine
Environment (Required on creation): Camunda Platform 7.15 +
Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket):
With Cloud 1.0 we have two workflow enginges (Camunda Cloud and Camunda Platform) at the same time. It might happen (and in fact already happened) that users would try to deploy a cloud diagram to platform or vice versa. In this case a meaningful error message will help the user to understand that this is not possible. The same thing is being implemented for Camunda Cloud (see https://github.com/camunda-cloud/zeebe/issues/7375)
Steps to reproduce (Required on creation):
- Run a Camunda Platfrom distro (WildFly, Tomcat, Run).
- Deploy a Camunda Cloud diagram (e.g. simpleclouddiagram.bpmn
).
Observed Behavior (Required on creation):
- A Camunda Cloud diagram is deployed successfully.
- Camunda Cloud (Zeebe) components are ignored when a process instance is started.
Expected behavior (Required on creation):
As a user I get a clear "can't deploy a BPMN made for Camunda Cloud on Camunda Platform" (or similar)