--- title: Basic Concepts of Tracker slug: tracker-en/basic-concepts-of-tracker description: Learn how to create a seamless flow using Events, Activities, Extensions, Gateways, Swimlanes, Artifacts, and Dynamic Components. This comprehensive document offers an overview of each element's functionality and provides real-life examples for better und createdAt: 2021-10-05T21:12:53.000Z --- **4biz** Flows can be drawn using a vast amount of elements that are available, below are described the elements as well as their characteristics and properties. ## Elements of Flow Element is the nomenclature used to group the components you can use to create a flow. They are distributed as follows: **Events**, **Activities**, **Extensions**, **Gateways**, **Swimlanes**, **Artifacts**, and **Dynamic Components**. To better understand what is in each Element group and each component functionality, check the items below. ### Events Events are components used to represent events in a flow. They may represent the waiting for an event to happen to initiate or proceed with the execution of an activity or may represent the beginning, or the end of a flow. | **Icon** | **Description** | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | |
:inlineImage[]{src="https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/ioRTQzWSoaENkN-sfJ73d_image.png" alt caption size="40" width="39" height="37"}
| **Start Event** – an element that starts the flow; | |
:inlineImage[]{src="https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/oYJQ82RnAEaf8cP-2VAJh_image.png" alt caption size="40" width="37" height="36"}
| **Sending Intermediate Event** – allows sending control of user activity to another activity. | |
:inlineImage[]{src="https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/eqdoGhgs67XTZJPSYccc5_image.png" alt caption size="40" width="36" height="35"}
| **Intermediate Capture Event** – allows receiving the control that was sent. | |
:inlineImage[]{src="https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/of3mL2ZEVxp3AUDSPMO6q_image.png" alt caption size="40" width="36" height="37"}
**** | **Timer Intermediate Event** – are events triggered by a set time and related to a Cron Expression, can be used as an initial or intermediate event. A frequent use for this event is in Batch services.

| |
:inlineImage[]{src="https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/DtupoooYJXVRlMvRKegZ3_image.png" alt caption size="40" width="36" height="38"}
| **End Event** – an element that identifies the end of the flow. | ### Activities The components of activities are the representations of what will be done in the flow. | **Icon** | **Description** | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | |
:inlineImage[]{src="https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/20SD-XYI0AJxDGvgYKOAa_image.png" alt caption size="40" width="68" height="44"}
| **User Task** – is used to model the work that needs to be done by human action. | |
:inlineImage[]{src="https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/mjHmp8jnIG5qir_F1oRYg_image.png" alt caption size="40" width="68" height="45"}
| **Message Sending **(E-mail) – is used to "**send**" e-mails automatically to one or more users or group(s) assigned to this task. | |
:inlineImage[]{src="https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/eD52_eDmilazJscRnKgns_image.png" alt caption size="40" width="70" height="45"}
| **Service Task **(ESI) – is a "**Bus Service**" solution that allows creating integration flows and interfaces between solutions, databases, files, and/or services existing in a computing environment. | |
:inlineImage[]{src="https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/2HslXyujWo6cmHOgR-hdN_image.png" alt caption size="40" width="69" height="45"}
| **Subprocesses** – allows the creation of ITSM requests or incidents, related or not to the request of the workflow being executed. | ### Extensions The extension components integrate the flow and with the user in a practical and direct way. | **Icon** | **Description** | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | |
:inlineImage[]{src="https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/51akH8VsvZwmwU0_cyj-M_image.png" alt caption size="40" width="56" height="43"}
| **Communication REST** – is a connection to web services accessing and passing parameters with the GET or POST methods. | |
:inlineImage[]{src="https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/I2uGkuu3WSnnI_k5NK73y_image.png" alt caption size="40" width="52" height="41"}
| **Notification** – used to send notification during the process of one or more users or group assigned to it. | ### Gateways Gateways are components responsible for controlling flow iterations, creating pathways in process mapping in the same sequence of activities. A gateway is connected to the flow, through sequence flow. They are represented visually by a rhombus. The inner symbol of the rhombus identifies the interpretation of the logic of the component. | **Icon** | **Description** | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | |
:inlineImage[]{src="https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/Omln0INizskAz8l_9ZsLj_image.png" alt caption size="40" width="43" height="42"}
| **Inclusive Gateway** - divides the process flow into one or more flows. By dividing, one or more branches are activated. All active input branches must be completed before mixing.

| |
:inlineImage[]{src="https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/rhLRF_XPuilvRL0gZ_FUU_image.png" alt caption size="40" width="43" height="43"}
| **Parallel Gateway** - Parallel symbol - Differs from other gateways because it does not depend on conditions or events. Instead, parallel gateways are used to represent two simultaneous tasks in a business flow.

| |
:inlineImage[]{src="https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/WgBiilykkPyEySW5TC-bE_image.png" alt caption size="40" width="45" height="47"}
| **Exclusive** **Gateway** - based on condition, divides the flow into one or more mutually exclusive paths. When dividing, it restores the sequence flow to exactly one of the output branches. When mixing, it waits for an input branch to be completed before triggering the output flow.

| ### Swimlanes | **Icon** | **Description** | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | |
:inlineImage[]{src="https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/Jfl2DIXqKdbV7NuiiTsQK_image.png" alt caption size="40" width="73" height="38"}
| **Pool/Participant** – A Pool is the graphical representation of a workflow context. It also acts as a "lane". It is a graphic container to partition a set of Activities.

| |
:inlineImage[]{src="https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/Db27LXh_PuqXlIQazf_JR_image.png" alt caption size="42" width="64" height="35"}
| **Lane **– A Lane is a sub-article within a process, sometimes within a pool, and will extend the entire length of the process. The lanes are used to organize and categorize the Activities.

| ### Artifacts | **Icon** | **Description** | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | |
:inlineImage[]{src="https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/DGiCK7Dhh5ydxB0REBGGE_image.png" alt caption size="40" width="43" height="39"}
| **Text Notes** – Represent relevant information to the template or individual elements within the process. | ### Dynamic components Dynamic Components are user-created elements that allow you to perform a different activity than system standards. To use it, you need to create a **Dynamic Component** and configure it to be used in the desired way. For this, access our documentation. ### Integration flow The integration flow is a parallel flow to the standard system workflow that uses different elements such as creating a database connection and functionalities directly programmed within the flow, among other elements other than those mentioned above. The Integration Flow tab within the standard flow has the functionality to only create a link from one flow to the other. To learn more about the integration flow, access our documentation.