BPMN Plus DMN - Combining Workflows and Decisions

The speaker begins by discussing the importance of workflows and how they are used to handle events in a process. They mention that using BPMN (Business Process Model and Notation) to describe rules can be challenging. Instead, they suggest using the existing BPMN symbol for business rules task and connecting it to a rules engine. The speaker then expresses their intention to generate a BPMN model and create a DMN (Decision Model and Notation) table to demonstrate how easy it is to manage the process.
The speaker explains the distinction between runtime tables and history tables in terms of performance. Runtime tables contain information about currently running process instances, while history tables store data about both running and finished processes. The history tables are not necessary for the engine to function, but they provide visibility into finished processes. Accessing the history requires using a different API to query and retrieve information about process events and variables.
The speaker mentions the ability to query the history for insights like identifying the most common part of a process and tracking changes in variables over time. They note that the level of granularity in history storage can be customized based on the requirements. The speaker concludes by thanking the attendees and mentioning the availability of a booth for further discussions and questions about Commando or the standards.