Merge pull request mendix#10877 from mendix/yl-ai-agent-task-documentation

Add AI Agent Task Documentation

Author: MarkvanMents

content/en/docs/refguide/modeling/application-logic/workflows/boundary-events.md

@@ -33,6 +33,7 @@ Studio Pro now supports the following boundary event:
 * [Multi-user task](/refguide/multi-user-task/)
 * [Call microflow](/refguide/call-microflow/)
 * [Call workflow](/refguide/call-workflow/)
+* [AI agent task](/refguide/ai-agent-task/) (in Studio Pro 11.9 and above)
 
 {{% alert color="info" %}}
 When a boundary event is added to an activity, this activity is also referred to as the parent activity of the boundary event.

content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/_index.md

@@ -28,9 +28,9 @@ The elements of this category are described in the table below:
 | Graphic                                                     | Element                           | Description                                                  |
 | ----------------------------------------------------------- | --------------------------------- | ------------------------------------------------------------ |
 | {{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/start-event.png" alt="Start Event" class="no-border" >}} | Start event                    | The starting point of a workflow. Workflows are triggered either by the [Call workflow](/refguide/on-click-event/#call-workflow) on-click event on pages or by the [Call workflow](/refguide/workflow-call/) activity in microflows. <br />Click the start event to open [workflow properties](/refguide/workflow-properties/). |
-| {{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/annotation.png" alt="Annotation" class="no-border" >}} | Annotation | An annotation is an element that can be used to put comments to a flow. For example, you can add a comment for your team that one of the user tasks needs to be changed later. <br />You can add annotations to the workflow or to individual activities. To add the annotation to the workflow, drag and drop the annotation in the editor's working area. To add the annotation to the activity, drag and drop it inside the activity. |
-| {{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/decision.png" alt="Decision" class="no-border" >}} | [Decision](/refguide/decision-in-workflows/) | Makes a choice based on a condition and follows one and only one of the outgoing paths. |
-| {{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/parallel-split.png" alt="Parallel Split" class="no-border" >}} | [Parallel split](/refguide/parallel-split/)  | Adds two parallel paths to your workflow.                    |
+| {{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/annotation.png" alt="Annotation" class="no-border" >}} | Annotation | Allows you to put comments to a flow. For example, you can add a comment for your team that one of the user tasks needs to be changed later. <br />You can add annotations to the workflow or to individual activities. To add the annotation to the workflow, drag and drop the annotation in the editor's working area. To add the annotation to the activity, drag and drop it inside the activity. |
+| {{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/decision.png" alt="Decision" class="no-border" >}} | [Decision](/refguide/decision-in-workflows/) | Allows you to make a choice based on a condition and follows one and only one of the outgoing paths. |
+| {{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/parallel-split.png" alt="Parallel Split" class="no-border" >}} | [Parallel split](/refguide/parallel-split/) | Allows you to create parallel paths that execute activities concurrently. By default, two paths are added. |
 | {{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/jump.png" alt="Jump Activity" class="no-border" >}} | [Jump](/refguide/jump-activity/)             | Allows you to jump to other activities in the workflow.      |
 | {{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/wait-for-notification.png" alt="Wait for notification activity" class="no-border" >}} | [Wait for notification](/refguide/wait-for-notification/)             | Allows you to suspend a workflow’s execution until the workflow is notified.      | 
 | {{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/end-event.png" alt="End event" >}} | [End event](/refguide/end-event-in-workflows/)           | Ends the path of the workflow.                                |
@@ -47,8 +47,9 @@ The elements of this category are described in the table below:
 
 | Graphic                                                     | Element                           | Description                                                  |
 | ----------------------------------------------------------- | --------------------------------- | ------------------------------------------------------------ |
-| {{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/user-task.png" width="50px" alt="User Task" class="no-border" >}} | [User task](/refguide/user-task/) | A central element in a workflow that allows you to assign a task to a certain user or a group of users using filters or microflows. |
-| {{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/multi-user-task.png" width="50px" alt="Multi-user task" class="no-border" >}} | [Multi-user task](/refguide/multi-user-task/) | A central element in a workflow that allows you assign a task to multiple users. Each user performs the same task. The outcomes from all individual tasks will be aggregated into a single multi-user task outcome based on the [completion condition](/refguide/multi-user-task/#completion-condition).  |
+| {{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/user-task.png" width="50px" alt="User Task" class="no-border" >}} | [User task](/refguide/user-task/) | Allows you to assign a task to a certain user or a group of users using filters or microflows. |
+| {{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/multi-user-task.png" width="50px" alt="Multi-user task" class="no-border" >}} | [Multi-user task](/refguide/multi-user-task/) | Allows you assign a task to multiple users. Each user performs the same task. The outcomes from all individual tasks will be aggregated into a single multi-user task outcome based on the [completion condition](/refguide/multi-user-task/#completion-condition). |
+| {{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/ai-agent-task.png" width="50px" alt="AI agent task" >}} | [AI agent task](/refguide/ai-agent-task/) | Allows you to call an [AI agent](/refguide/ai-agent-task/#ai-agents) to complete a task such as classification, summarization, or content generation. |
 
 ## Events {#events}
 

content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/ai-agent-task.md

@@ -0,0 +1,72 @@
+---
+title: "AI Agent Task"
+url: /refguide/ai-agent-task/
+weight: 85
+#If moving or renaming this doc file, implement a temporary redirect and let the respective team know they should update the URL in the product. See Mapping to Products for more details. The anchor {#ai-agents} is also used in the product. 
+---
+
+## Introduction
+
+**AI agent task** lets you assign a task to an AI agent as a step in your workflow, instead of assigning that step to a human. 
+
+When the workflow reaches the AI agent task, a microflow is called to handle the execution of an agent that performs a predefined task. The workflow then continues based on that result, for example, by routing to the next step, triggering an action, or escalating to a human reviewer.
+
+**AI agent task** can be used across a wide range of use cases. Some examples include assessing requests, classifying data, extracting information from unstructured text, summarizing content, and drafting outputs such as notifications or reports.
+
+## AI Agents {#ai-agents}
+
+An AI agent is an autonomous software system powered by large language models (LLMs). It perceives its environment, reasons through a goal, and takes actions to achieve the goal, replacing repetitive manual steps. For critical tasks, you can still add a user task to keep a human in the loop.
+
+With **AI agent task**, you can select a [microflow](#microflow) that calls any agent that has been configured in your application. You are not limited to one approach. Agents can be created and configured in different ways, as long as they can be called via a microflow. 
+
+If you do not yet have any agents configured, you can get started by following the guide on [creating your first agent](/appstore/modules/genai/how-to/howto-single-agent/).
+
+{{% alert color="info" %}}
+Support for configuring AI agents using an Agent Editor in Studio Pro is coming soon.
+{{% /alert %}}
+
+## Properties
+
+AI agent task properties consist of the following sections:
+
+* [General](#general)
+* [Parameters](#parameters)
+* [Outcomes](#outcomes)
+* [Boundary events](#boundary-events)
+* [Common](#common)
+
+### General Section {#general}
+
+#### Caption
+
+The **Caption** describes what happens in this element. It is displayed under the workflow element to make the workflow easier to read and understand.
+
+#### Microflow {#microflow}
+
+The microflow that handles the AI agent execution for the AI agent task. Use it to prepare and pass the right information to the agent, call the agent, and define what happens next.
+
+### Parameters {#parameters}
+
+Parameters of the selected microflow. Depending on the selected microflow, you will see a list of its parameters. Parameters pass data to the element. To view the **Parameters**, click the ellipsis icon next to the property name.
+
+### Outcomes {#outcomes}
+
+The outcomes depend on the return type of the selected microflow:
+
+* **No return type**: The activity has a single outcome and the workflow proceeds to the next step.
+* **Boolean**: The activity has two outcomes: `true` and `false`. The workflow proceeds to the next step based on the returned value.
+* **Enumeration**: The activity has one outcome for each enumeration value, plus an `empty` outcome for when the value is unassigned. The workflow proceeds to the next step based on the returned value.
+
+### Boundary Events Section {#boundary-events}
+
+Boundary events can be attached to this element and are triggered by certain events to handle exceptional situations during its execution. For more information, see [Boundary Events](/refguide/workflow-boundary-events/).
+
+### Common Section {#common}
+
+**Name** is the internal name of the element. When referring to the element in the app, you will use this name. It must be unique within the workflow, but you can have two elements with the same name in different workflows.
+
+## Read More
+
+* [Workflow Properties](/refguide/workflow-properties/)
+* [GenAI Capabilities in Mendix](/appstore/modules/genai/)
+* [Create Your First Agent](/appstore/modules/genai/how-to/howto-single-agent/)

content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/call-microflow.md

@@ -36,11 +36,15 @@ Parameters of the selected microflow. Depending on the selected microflow, you w
 
 ### Outcomes Section {#outcomes}
 
-**Outcomes** depends on the return type and values of the microflow. For example, when there is not return type, you have a single outcome; for the Boolean, you have **true** and **false** outcomes; and for the enumeration – an outcome per each enumeration value and an empty one when the value is unassigned. 
+The outcomes depend on the return type of the selected microflow:
+
+* **No return type**: The activity has a single outcome and the workflow proceeds to the next step.
+* **Boolean**: The activity has two outcomes: `true` and `false`. The workflow proceeds to the next step based on the returned value.
+* **Enumeration**: The activity has one outcome for each enumeration value, plus an `empty` outcome for when the value is unassigned. The workflow proceeds to the next step based on the returned value.
 
 ### Boundary Events Section {#boundary-events}
 
-For more information, see [Boundary Events](/refguide/workflow-boundary-events/).
+Boundary events can be attached to this element and are triggered by certain events to handle exceptional situations during its execution. For more information, see [Boundary Events](/refguide/workflow-boundary-events/).
 
 ### Common Section {#common}
 

content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/call-workflow.md

@@ -48,7 +48,7 @@ To change the parameter, either double-click the parameter from the list or sele
 
 ### Boundary Events Section {#boundary-events}
 
-For more information, see [Boundary Events](/refguide/workflow-boundary-events/).
+Boundary events can be attached to this element and are triggered by certain events to handle exceptional situations during its execution. For more information, see [Boundary Events](/refguide/workflow-boundary-events/).
 
 ### Common Section {#common}
 

content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/multi-user-task.md

@@ -401,7 +401,7 @@ In addition to adding new parameters, you can perform the following actions on p
 
 ### Boundary Events Section {#boundary-events}
 
-For more information, see [Boundary Events](/refguide/workflow-boundary-events/).
+Boundary events can be attached to this element and are triggered by certain events to handle exceptional situations during its execution. For more information, see [Boundary Events](/refguide/workflow-boundary-events/).
 
 ### Common Section {#common}
 

content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/user-task.md

@@ -200,7 +200,7 @@ In addition to adding new parameters, you can perform the following actions on p
 
 ### Boundary Events Section {#boundary-events}
 
-For more information, see [Boundary Events](/refguide/workflow-boundary-events/).
+Boundary events can be attached to this element and are triggered by certain events to handle exceptional situations during its execution. For more information, see [Boundary Events](/refguide/workflow-boundary-events/).
 
 ### Common Section {#common}
 

content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/wait-for-notification.md

@@ -31,7 +31,7 @@ The **Caption** describes what happens in this element. It is displayed under th
 
 ### Boundary Events {#boundary-events}
 
-For more information, see [Boundary Events](/refguide/workflow-boundary-events/).
+Boundary events can be attached to this element and are triggered by certain events to handle exceptional situations during its execution. For more information, see [Boundary Events](/refguide/workflow-boundary-events/).
 
 ### Common Section {#common}