> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/interfacing-help-files-fr/analystes-de-processus/business-process-management/creating-and-editing-process-diagrams/mapping-a-process/editing-bpmn-properties-for-objects-and-flows/tasks-and-subprocesses.md). # Tasks & Subprocesses Configure properties to control activity behavior, looping patterns, and (for tasks) functional type, defining how work executes in your process. A **task** or **subprocess** is an **activity** in BPMN—a unit of work to be performed. Each activity can be defined by: * **Special Behaviors** — how it deviates from standard execution * **Loop Characteristics** — how and when it repeats * **Task Type** *(tasks only)* – its functional role in the process {% hint style="info" %} Use **Auto Reroute** to automatically redraw edges and improve diagram readability. This is useful if edges become misaligned, disconnected, or difficult to follow. * See [**Rerouting with Auto Reroute**](#rerouting-with-auto-reroute) below for instructions. {% endhint %}
Rerouting with Auto Reroute Use **Auto Reroute** to quickly correct and tidy up flows connected to an activity. This may be necessary if: * The activity node size changes after applying **BPMN properties** * Edges appear broken or disconnected * Flows overlap or reduce diagram readability To reroute flows: 1. **Right-click** the affected activity and select **Edit BPMN Properties**.
2. In the **BPMN Properties** dialog, click **Auto Reroute**.
All connected flows will be automatically redrawn for clarity and proper alignment.
*** ## Special Activity Behaviors These properties modify the default way a task or subprocess runs.
What It IsWhen to UseWhat It Looks Like
Ad-HocAn ad-hoc element allows its contained steps to be performed as needed—in any order or skipped entirely.For activities requiring flexibility and user-driven control over sequence and execution.
CompensationA compensation element reverses the outcome of a previously completed activity, restoring a prior state or mitigating its effects.To undo results when errors, exceptions, or abnormal situations occur.
*** ## Loop Characteristics Loop characteristics define **whether and how an activity repeats**.
What It IsWhat It Looks Like
LoopA loop repeats a set of activities multiple times based on a specified condition, stopping only when that condition is no longer met.
ParallelA parallel loop executes multiple instances of the looped activities simultaneously, with each iteration running independently.
Sequential LoopA sequential loop executes the looped activities one after another, starting the next iteration only after the previous one finishes.
*** ## Task Types (Tasks Only) Task types specify the functional role of a task in the process.
What It IsWhat It Looks Like
AbstractAn abstract task acts as a placeholder representing an activity that is not fully defined in the process model.
SendA send task represents an activity that initiates sending a message or communication to an external recipient or system.
ReceiveA receive task represents a point where the process flow pauses until a specific message or signal is received from an external participant or system.
UserA user task requires a human to complete work using a software interface, such as reviewing documents or approving requests.
ManualA manual task involves work performed entirely outside of any software system, relying on human effort, such as physical tasks, paper-based activities, or manual decision-making.
Business RuleA business rule task executes a business rule or decision, automating rule-based processes such as validations or decision logic.
ServiceA service task represents work performed by an automated software service, application, or external system invoked during the process.
ScriptA script task represents an activity implemented via a script or code snippet (e.g., JavaScript, Groovy, Python) that executes custom logic or automation within the process.
*** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://interfacing.gitbook.io/interfacing-help-files/interfacing-help-files-fr/analystes-de-processus/business-process-management/creating-and-editing-process-diagrams/mapping-a-process/editing-bpmn-properties-for-objects-and-flows/tasks-and-subprocesses.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.