-
Task
-
Resolution: Unresolved
-
Major
-
None
-
None
-
False
-
None
-
False
-
---
-
---
-
-
MessageIn/Out were removed from BPMN VS Code editor in KOGITO-418 since those properties are not used in Kogito Runtime. But it creates issues when processes with General Service Task importing to the Business Central.
Expected Result
When creating Start->Service Task->End process MessageIn/Out elements should be present:
<bpmn2:itemDefinition id='_25ADBBE9-1825-4910-99C5-1409422D46AB_InMessageType' structureRef='org.acme.travels.Trip'/> <bpmn2:itemDefinition id='_25ADBBE9-1825-4910-99C5-1409422D46AB_OutMessageType' structureRef='org.acme.travels.Trip'/> <bpmn2:message id='_25ADBBE9-1825-4910-99C5-1409422D46AB_InMessage' itemRef='_25ADBBE9-1825-4910-99C5-1409422D46AB_InMessageType'/> <bpmn2:message id='_25ADBBE9-1825-4910-99C5-1409422D46AB_OutMessage' itemRef='_25ADBBE9-1825-4910-99C5-1409422D46AB_OutMessageType'/> and <bpmn2:inMessageRef>_25ADBBE9-1825-4910-99C5-1409422D46AB_InMessage</bpmn2:inMessageRef> <bpmn2:outMessageRef>_25ADBBE9-1825-4910-99C5-1409422D46AB_OutMessage</bpmn2:outMessageRef>
- blocks
-
RHPAM-4604 BPMN file contaning (Java) ServiceTask created using VSCode BPMN Editor causes parser errors in maven build
- Closed
- is caused by
-
KOGITO-418 Missing structureref type for service task in VSCode BPMN editor
- Resolved
- is duplicated by
-
KOGITO-8279 BPMN file contaning (Java) ServiceTask created using VSCode BPMN Editor causes parser errors in maven build
- Closed
- is incorporated by
-
RHPAM-4604 BPMN file contaning (Java) ServiceTask created using VSCode BPMN Editor causes parser errors in maven build
- Closed