Action subflows

There is a standard template for action subflows: they must start with the BeginAction subflow and terminate with the EndAction subflow. In between these start and end flows, any arrangement of integration nodes is possible. Often, only a single compute node or database node is required, and the action logic is implemented in the ESQL associated with this node.

The following figure shows a typical action implementation, where the business logic of the action is implemented in a database node.

The action subflows must be included in the overall actions subflow. This is a container for all actions, which is included in the main event processing flow.