writinwaters
commited on
Commit
·
4e483d4
1
Parent(s):
019279d
Added description of the Concentrator component (#4549)
Browse files### What problem does this PR solve?
### Type of change
- [x] Documentation Update
docs/references/agent_component_reference/concentrator.mdx
CHANGED
|
@@ -0,0 +1,26 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
---
|
| 2 |
+
sidebar_position: 10
|
| 3 |
+
slug: /concentrator_component
|
| 4 |
+
---
|
| 5 |
+
|
| 6 |
+
# Concentrator component
|
| 7 |
+
|
| 8 |
+
A component that directs execution flow to multiple downstream components.
|
| 9 |
+
|
| 10 |
+
---
|
| 11 |
+
|
| 12 |
+
The **Concentrator** component acts as a "repeater" of execution flow, transmitting a flow to multiple downstream components.
|
| 13 |
+
|
| 14 |
+
|
| 15 |
+
## Scenarios
|
| 16 |
+
|
| 17 |
+
A **Concentrator** component enhances the current UX design. For a component originally designed to support only one downstream component, you can append a **Concentrator**, enabling it to have multiple downstream components.
|
| 18 |
+
|
| 19 |
+
## Examples
|
| 20 |
+
|
| 21 |
+
Explore our general-purpose chatbot agent template, featuring a **Concentrator** component (component ID: **medical**) that relays an execution flow from category 2 of the **Categorize** component to the two translator components:
|
| 22 |
+
|
| 23 |
+
1. Click the **Agent** tab at the top center of the page to access the **Agent** page.
|
| 24 |
+
2. Click **+ Create agent** on the top right of the page to open the **agent template** page.
|
| 25 |
+
3. On the **agent template** page, hover over the **General-purpose chatbot** card and click **Use this template**.
|
| 26 |
+
4. Name your new agent and click **OK** to enter the workflow editor.
|
docs/references/agent_component_reference/switch.mdx
CHANGED
|
@@ -19,7 +19,7 @@ A **Switch** component is essential for condition-based direction of execution f
|
|
| 19 |
|
| 20 |
### Case n
|
| 21 |
|
| 22 |
-
A **Switch** component must have at least one case, each with multiple specified conditions and
|
| 23 |
|
| 24 |
#### Next step
|
| 25 |
|
|
|
|
| 19 |
|
| 20 |
### Case n
|
| 21 |
|
| 22 |
+
A **Switch** component must have at least one case, each with multiple specified conditions and *only one* downstream component. When multiple conditions are specified for a case, you must set the logical relationship between them to either AND or OR.
|
| 23 |
|
| 24 |
#### Next step
|
| 25 |
|