Motivation
Actually it is not possible, in kogito, to perform the authoring neither execution of cases (process engine). So the main motivation behind this task is to provide case authoring and execution capabilities for the different kogito channels, as well as it's currently available for BC.

The key difference in the case authoring side, between BC and the expected for kogito, is:

• BC -> Process and Case are different assets, different editors. It means once loading any asset, the editor already provides the necessary capabiltiities for each asset type
• Kogito -> It makes no difference, at authoring time, about process and case. It means there will be a single editor (BPMN) for achieveing both process and case capabilities. On the other hand, these BPMN editor updates have to also be backwards compatible with BC, as it differs between assets

Goals
This task focuses the tooling side of case management support, so the main goal is to provide case management capabilities for the actual BPMN editor, in the different kogito channels.

This whole task can be split in several steps, in several actions also deliveries, by keeping those in sync with the work around case management capabilities being done on the kogito runtime engines side (CC cristiano.nicolai@gmail.com rhn-support-rromerom)

Actions (WIP)

• 1) Figure out how to provide addtional CM capabilities by using a "single" BPMN editor instance:
  • Do the CM additions (eg: nodes, properties) will be presented by default for all processes? or should addtions be presented or removed at runtime (eg: nodes in the palette) by giving some runtime predicate? (eg: some field value in some BPMN node), is also possible to "switch" then between case / process mode at runtime?
  • Figure out how to keep backward compatibility with BC, so it will present CM additions just based on the asset type
• 2) Support for Milestones (KOGITO-2367)
• 3) Support for Stages
  • An stage is just and Ad-hoc subprocess, how both will coexist in a single editor?
• 4) Support for Case Files

This ticket is an Epic type, so actions above will be presented as different issues in this Epic. The complete case authoring capabilities can be expected once issues in epic are are also completed.