add overviews to bpmn elements

docs/components/modeler/bpmn/events.md

@@ -4,6 +4,10 @@ title: "Overview"
 description: "This document outlines an overview of general events, intermediate events, and boundary events."
 ---
 
+**Events** in BPMN represent things that _happen_. A process can react to events (_catching_ event) as well as emit events (_throwing_ event). For example, a catching message event makes the token continue as soon as a message is received. The XML representation of the process contains the criteria for which kind of message triggers continuation.
+
+Events can be added to the process in various ways. Not only can they be used to make a token wait at a certain point, but also for interrupting a token's progress.
+
 Currently supported events:
 
 - [None events](none-events/none-events.md)

docs/components/modeler/bpmn/gateways.md

@@ -4,6 +4,10 @@ title: "Overview"
 description: "This document outlines an overview of currently supported gateways."
 ---
 
+Gateways are elements that route tokens in more complex patterns than plain sequence flow.
+
+BPMN's **exclusive gateway** chooses one sequence flow out of many based on data, whereas BPMN's **parallel gateway** generates new tokens by activating multiple sequence flows in parallel, for example.
+
 Currently supported elements:
 
 - [Exclusive gateways](exclusive-gateways/exclusive-gateways.md)

docs/components/modeler/bpmn/markers.md

@@ -4,6 +4,12 @@ title: "Overview"
 description: "This document outlines an overview of supported markers."
 ---
 
+You might want to execute some tasks for every element of a list, like the `for each` construct in programming languages. Refer to [Workflow Pattern 14: Multiple Instances with a priori Run-Time Knowledge](http://www.workflowpatterns.com/patterns/control/new/wcp14.php): "Multiple instances of a task can be created. The required number of instances may depend on a number of runtime factors, but is known before the task instances must be created. Once initiated, these instances are independent of each other and run concurrently. It is necessary to synchronize the instances at completion before any subsequent tasks can be triggered."
+
+In BPMN, this is implemented using [multiple instance activities](/components/modeler/bpmn/multi-instance/multi-instance.md):
+
+Parallel multiple instance markers define that a subprocess is executed multiple times - once for each element of a given collection (like a `for each` loop in a programming language).
+
 Currently supported markers:
 
 - [Multi-instance](multi-instance/multi-instance.md)

docs/components/modeler/bpmn/subprocesses.md

@@ -4,6 +4,10 @@ title: "Overview"
 description: "This document outlines an overview of supported elements."
 ---
 
+**Subprocesses** are element containers that allow defining common functionality. For example, you can attach an event to a sub process's border.
+
+When the event is triggered, the subprocess is interrupted, regardless which of its elements is currently active.
+
 Currently supported elements:
 
 - [Embedded subprocess](embedded-subprocesses/embedded-subprocesses.md)

docs/components/modeler/bpmn/tasks.md

@@ -4,6 +4,10 @@ title: "Overview"
 description: "This document outlines an overview of supported elements."
 ---
 
+The basic elements of BPMN processes are tasks; these are atomic units of work composed to create a meaningful result. Whenever a token reaches a task, the token stops and Zeebe creates a job and notifies a registered worker to perform work. When that handler signals completion, the token continues on the outgoing sequence flow.
+
+Choosing the granularity of a task is up to the person modeling the process. For example, the activity of processing an order can be modeled as a single _Process Order_ task, or as three individual tasks _Collect Money_, _Fetch Items_, _Ship Parcel_. If you use Zeebe to orchestrate microservices, one task can represent one microservice invocation.
+
 Currently supported elements:
 
 - [Service tasks](service-tasks/service-tasks.md)

versioned_docs/version-8.2/components/modeler/bpmn/events.md

@@ -4,6 +4,10 @@ title: "Overview"
 description: "This document outlines an overview of general events, intermediate events, and boundary events."
 ---
 
+**Events** in BPMN represent things that _happen_. A process can react to events (_catching_ event) as well as emit events (_throwing_ event). For example, a catching message event makes the token continue as soon as a message is received. The XML representation of the process contains the criteria for which kind of message triggers continuation.
+
+Events can be added to the process in various ways. Not only can they be used to make a token wait at a certain point, but also for interrupting a token's progress.
+
 Currently supported events:
 
 - [None events](none-events/none-events.md)

versioned_docs/version-8.2/components/modeler/bpmn/gateways.md

@@ -4,6 +4,10 @@ title: "Overview"
 description: "This document outlines an overview of currently supported gateways."
 ---
 
+Gateways are elements that route tokens in more complex patterns than plain sequence flow.
+
+BPMN's **exclusive gateway** chooses one sequence flow out of many based on data, whereas BPMN's **parallel gateway** generates new tokens by activating multiple sequence flows in parallel, for example.
+
 Currently supported elements:
 
 - [Exclusive gateways](exclusive-gateways/exclusive-gateways.md)

versioned_docs/version-8.2/components/modeler/bpmn/markers.md

@@ -4,6 +4,12 @@ title: "Overview"
 description: "This document outlines an overview of supported markers."
 ---
 
+You might want to execute some tasks for every element of a list, like the `for each` construct in programming languages. Refer to [Workflow Pattern 14: Multiple Instances with a priori Run-Time Knowledge](http://www.workflowpatterns.com/patterns/control/new/wcp14.php): "Multiple instances of a task can be created. The required number of instances may depend on a number of runtime factors, but is known before the task instances must be created. Once initiated, these instances are independent of each other and run concurrently. It is necessary to synchronize the instances at completion before any subsequent tasks can be triggered."
+
+In BPMN, this is implemented using [multiple instance activities](/components/modeler/bpmn/multi-instance/multi-instance.md):
+
+Parallel multiple instance markers define that a subprocess is executed multiple times - once for each element of a given collection (like a `for each` loop in a programming language).
+
 Currently supported markers:
 
 - [Multi-instance](multi-instance/multi-instance.md)

versioned_docs/version-8.2/components/modeler/bpmn/subprocesses.md

@@ -4,6 +4,10 @@ title: "Overview"
 description: "This document outlines an overview of supported elements."
 ---
 
+**Subprocesses** are element containers that allow defining common functionality. For example, you can attach an event to a sub process's border.
+
+When the event is triggered, the subprocess is interrupted, regardless which of its elements is currently active.
+
 Currently supported elements:
 
 - [Embedded subprocess](embedded-subprocesses/embedded-subprocesses.md)

versioned_docs/version-8.2/components/modeler/bpmn/tasks.md

@@ -4,6 +4,10 @@ title: "Overview"
 description: "This document outlines an overview of supported elements."
 ---
 
+The basic elements of BPMN processes are tasks; these are atomic units of work composed to create a meaningful result. Whenever a token reaches a task, the token stops and Zeebe creates a job and notifies a registered worker to perform work. When that handler signals completion, the token continues on the outgoing sequence flow.
+
+Choosing the granularity of a task is up to the person modeling the process. For example, the activity of processing an order can be modeled as a single _Process Order_ task, or as three individual tasks _Collect Money_, _Fetch Items_, _Ship Parcel_. If you use Zeebe to orchestrate microservices, one task can represent one microservice invocation.
+
 Currently supported elements:
 
 - [Service tasks](service-tasks/service-tasks.md)

versioned_docs/version-8.3/components/modeler/bpmn/events.md

@@ -4,6 +4,10 @@ title: "Overview"
 description: "This document outlines an overview of general events, intermediate events, and boundary events."
 ---
 
+**Events** in BPMN represent things that _happen_. A process can react to events (_catching_ event) as well as emit events (_throwing_ event). For example, a catching message event makes the token continue as soon as a message is received. The XML representation of the process contains the criteria for which kind of message triggers continuation.
+
+Events can be added to the process in various ways. Not only can they be used to make a token wait at a certain point, but also for interrupting a token's progress.
+
 Currently supported events:
 
 - [None events](none-events/none-events.md)

versioned_docs/version-8.3/components/modeler/bpmn/gateways.md

@@ -4,6 +4,10 @@ title: "Overview"
 description: "This document outlines an overview of currently supported gateways."
 ---
 
+Gateways are elements that route tokens in more complex patterns than plain sequence flow.
+
+BPMN's **exclusive gateway** chooses one sequence flow out of many based on data, whereas BPMN's **parallel gateway** generates new tokens by activating multiple sequence flows in parallel, for example.
+
 Currently supported elements:
 
 - [Exclusive gateways](exclusive-gateways/exclusive-gateways.md)

versioned_docs/version-8.3/components/modeler/bpmn/markers.md

@@ -4,6 +4,12 @@ title: "Overview"
 description: "This document outlines an overview of supported markers."
 ---
 
+You might want to execute some tasks for every element of a list, like the `for each` construct in programming languages. Refer to [Workflow Pattern 14: Multiple Instances with a priori Run-Time Knowledge](http://www.workflowpatterns.com/patterns/control/new/wcp14.php): "Multiple instances of a task can be created. The required number of instances may depend on a number of runtime factors, but is known before the task instances must be created. Once initiated, these instances are independent of each other and run concurrently. It is necessary to synchronize the instances at completion before any subsequent tasks can be triggered."
+
+In BPMN, this is implemented using [multiple instance activities](/components/modeler/bpmn/multi-instance/multi-instance.md):
+
+Parallel multiple instance markers define that a subprocess is executed multiple times - once for each element of a given collection (like a `for each` loop in a programming language).
+
 Currently supported markers:
 
 - [Multi-instance](multi-instance/multi-instance.md)

versioned_docs/version-8.3/components/modeler/bpmn/subprocesses.md

@@ -4,6 +4,10 @@ title: "Overview"
 description: "This document outlines an overview of supported elements."
 ---
 
+**Subprocesses** are element containers that allow defining common functionality. For example, you can attach an event to a sub process's border.
+
+When the event is triggered, the subprocess is interrupted, regardless which of its elements is currently active.
+
 Currently supported elements:
 
 - [Embedded subprocess](embedded-subprocesses/embedded-subprocesses.md)

versioned_docs/version-8.3/components/modeler/bpmn/tasks.md

@@ -4,6 +4,10 @@ title: "Overview"
 description: "This document outlines an overview of supported elements."
 ---
 
+The basic elements of BPMN processes are tasks; these are atomic units of work composed to create a meaningful result. Whenever a token reaches a task, the token stops and Zeebe creates a job and notifies a registered worker to perform work. When that handler signals completion, the token continues on the outgoing sequence flow.
+
+Choosing the granularity of a task is up to the person modeling the process. For example, the activity of processing an order can be modeled as a single _Process Order_ task, or as three individual tasks _Collect Money_, _Fetch Items_, _Ship Parcel_. If you use Zeebe to orchestrate microservices, one task can represent one microservice invocation.
+
 Currently supported elements:
 
 - [Service tasks](service-tasks/service-tasks.md)

versioned_docs/version-8.4/components/modeler/bpmn/events.md

@@ -4,6 +4,10 @@ title: "Overview"
 description: "This document outlines an overview of general events, intermediate events, and boundary events."
 ---
 
+**Events** in BPMN represent things that _happen_. A process can react to events (_catching_ event) as well as emit events (_throwing_ event). For example, a catching message event makes the token continue as soon as a message is received. The XML representation of the process contains the criteria for which kind of message triggers continuation.
+
+Events can be added to the process in various ways. Not only can they be used to make a token wait at a certain point, but also for interrupting a token's progress.
+
 Currently supported events:
 
 - [None events](none-events/none-events.md)

versioned_docs/version-8.4/components/modeler/bpmn/gateways.md

@@ -4,6 +4,10 @@ title: "Overview"
 description: "This document outlines an overview of currently supported gateways."
 ---
 
+Gateways are elements that route tokens in more complex patterns than plain sequence flow.
+
+BPMN's **exclusive gateway** chooses one sequence flow out of many based on data, whereas BPMN's **parallel gateway** generates new tokens by activating multiple sequence flows in parallel, for example.
+
 Currently supported elements:
 
 - [Exclusive gateways](exclusive-gateways/exclusive-gateways.md)

versioned_docs/version-8.4/components/modeler/bpmn/markers.md

@@ -4,6 +4,12 @@ title: "Overview"
 description: "This document outlines an overview of supported markers."
 ---
 
+You might want to execute some tasks for every element of a list, like the `for each` construct in programming languages. Refer to [Workflow Pattern 14: Multiple Instances with a priori Run-Time Knowledge](http://www.workflowpatterns.com/patterns/control/new/wcp14.php): "Multiple instances of a task can be created. The required number of instances may depend on a number of runtime factors, but is known before the task instances must be created. Once initiated, these instances are independent of each other and run concurrently. It is necessary to synchronize the instances at completion before any subsequent tasks can be triggered."
+
+In BPMN, this is implemented using [multiple instance activities](/components/modeler/bpmn/multi-instance/multi-instance.md):
+
+Parallel multiple instance markers define that a subprocess is executed multiple times - once for each element of a given collection (like a `for each` loop in a programming language).
+
 Currently supported markers:
 
 - [Multi-instance](multi-instance/multi-instance.md)

versioned_docs/version-8.4/components/modeler/bpmn/subprocesses.md

@@ -4,6 +4,10 @@ title: "Overview"
 description: "This document outlines an overview of supported elements."
 ---
 
+**Subprocesses** are element containers that allow defining common functionality. For example, you can attach an event to a sub process's border.
+
+When the event is triggered, the subprocess is interrupted, regardless which of its elements is currently active.
+
 Currently supported elements:
 
 - [Embedded subprocess](embedded-subprocesses/embedded-subprocesses.md)

versioned_docs/version-8.4/components/modeler/bpmn/tasks.md

@@ -4,6 +4,10 @@ title: "Overview"
 description: "This document outlines an overview of supported elements."
 ---
 
+The basic elements of BPMN processes are tasks; these are atomic units of work composed to create a meaningful result. Whenever a token reaches a task, the token stops and Zeebe creates a job and notifies a registered worker to perform work. When that handler signals completion, the token continues on the outgoing sequence flow.
+
+Choosing the granularity of a task is up to the person modeling the process. For example, the activity of processing an order can be modeled as a single _Process Order_ task, or as three individual tasks _Collect Money_, _Fetch Items_, _Ship Parcel_. If you use Zeebe to orchestrate microservices, one task can represent one microservice invocation.
+
 Currently supported elements:
 
 - [Service tasks](service-tasks/service-tasks.md)