The BusinessCase is classically an instance of a CaseMap execution. So the CaseMap is the static definition of the flow, while the BusinessCase reflects a real execution of a CaseMap. Every execution of a CaseMap creates a new Business Case instance. In classical workflows, where users start a Business Process directly via IVP link, the first Case is treated as Business Case. You can attach follow up cases (triggered or signaled) as child case to the first Business Case by simply declaring this on the Inscription mask. And this is also the default for newly created processes. We still create detached cases for old processes, to not break any existing behavior. So basically you can make use of this new Business Case concept without using a Case Map. Its the new cool thing to keep agile process executions together. ![alt text][1]![alt text][2] [1]: https://answers.axonivy.com/upfiles/requestStartEvent_triggerTab.png [2]: https://answers.axonivy.com/upfiles/signalStartEvent_signalTab.png

The BusinessCase is classically an instance of a CaseMap execution. So the CaseMap is the static definition of the flow, while the BusinessCase reflects a real execution of a CaseMap. Every execution of a CaseMap creates a new Business Case instance. In classical workflows, where users start a Business Process directly via IVP link, the first Case is treated as Business Case. You can attach follow up cases (triggered or signaled) as child case to the first Business Case by simply declaring this on the Inscription mask. And this is also the default for newly created processes. We still create detached cases for old processes, to not break any existing behavior. So basically you can make use of this new Business Case concept without using a Case Map. Its the new cool thing to keep agile process executions together.