Skip to content

Commit 7ad7b69

Browse files
committed
couple of touchups
1 parent 2f29fd1 commit 7ad7b69

File tree

4 files changed

+7
-5
lines changed

4 files changed

+7
-5
lines changed

articles/machine-learning/prompt-flow/how-to-develop-flow.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.topic: how-to
1212
author: lgayhardt
1313
ms.author: lagayhar
1414
ms.reviewer: jinzhong
15-
ms.date: 10/15/2024
15+
ms.date: 10/16/2024
1616
---
1717
# Develop prompt flow
1818

@@ -49,7 +49,9 @@ Before you begin authoring, start the compute session by selecting **Start compu
4949
The compute session can take a few minutes to start. While the compute session is starting, inspect the parts of the flow authoring page.
5050

5151
- The **Flow** or *flatten* view on the left side of the page is the main working area where you author the flow. In the flatten view, you can edit nodes, tools, prompts, and inputs; run nodes or the whole flow; and define and view outputs.
52+
5253
- **Files** at top right shows the folder and file structure of the flow. Each flow has a folder that contains a *flow.dag.yaml* file, source code files, and system folders. You can add, edit, delete, upload, or download files for testing, deployment, or collaboration.
54+
5355
- The **Graph** view at lower right visualizes the flow structure. You can zoom in or out or use auto layout. You can't edit this view directly, but you can select a node to locate and edit it in the flatten view.
5456

5557
### Flow input and output
@@ -135,7 +137,7 @@ After a flow run completes, you can select **View outputs** to check all histori
135137

136138
A *chat flow* is a specific type of prompt flow designed for conversational application development. Chat flow builds on the standard flow capabilities to provide enhanced support for chat inputs/outputs and chat history. By using chat flow, you can easily create a chatbot that handles chat input and output.
137139

138-
To create a chat flow, select **Create** in the **Chat flow** card on the **Create a new flow** screen, or select **Chat** in the **Explore gallery** and clone one of the available flows.
140+
To create a chat flow, on the **Create a new flow** screen, select **Create** on the **Chat flow** card, or select **Chat** in the **Explore gallery** and clone one of the available flows.
139141

140142
In a chat flow authoring page, the chat flow is tagged with a **Chat** label to distinguish it from standard and evaluation flows. To test a chat flow, you select **Chat** at the top of the page to trigger a **Chat** box for conversation.
141143

@@ -151,15 +153,15 @@ The most important elements that differentiate a chat flow from a standard flow
151153

152154
- **Chat output** refers to the AI-generated messages that are sent to users in response to their inputs. Generating contextually appropriate and engaging chat output is vital for a positive user experience.
153155

154-
A chat flow can have multiple inputs. In the chat flow **Inputs** section, you mark one of the inputs as the **Chat input**, and you populate the chat input value by typing in the **Chat** box.
156+
A chat flow can have multiple inputs. In the chat flow **Inputs** section, you mark one of the inputs as the **Chat input**, and you populate the chat input value by entering a question in the **Chat** box.
155157

156158
:::image type="content" source="./media/how-to-develop-flow/flow-input-output.png" alt-text="Screenshot showing the test question in the Inputs section and the Chat box." lightbox ="./media/how-to-develop-flow/flow-input-output.png":::
157159

158160
### Manage chat history
159161

160162
To help you manage chat history, `chat_history` in the **Inputs** section is reserved for representing chat history. You can't manually edit `chat_history`.
161163

162-
Chat history is structured as a list of inputs and outputs. All interactions in the chat box, including user chat inputs, generated chat outputs, and other flow inputs and outputs, are automatically stored in chat history.
164+
Chat history is structured as a list of inputs and outputs. All interactions in the chat box, including user chat inputs, generated chat outputs, and other flow inputs and outputs, are automatically stored in chat history. The following code shows the structure of chat history.
163165

164166
```json
165167
[
@@ -192,7 +194,7 @@ Chat history is structured as a list of inputs and outputs. All interactions in
192194
> [!NOTE]
193195
> When you conduct tests in the **Chat** box, you automatically save chat history. For batch runs, you must include chat history within the batch run dataset. If there's no chat history available, set the `chat_history` to an empty list `[]` within the batch run dataset.
194196
195-
To retrieve past interactions, reference `chat_history` in your prompts. You can then reference previous inputs and outputs to create contextually relevant responses. Incorporating chat history into your prompts is essential for creating context-aware and engaging chatbot responses.
197+
To retrieve past interactions, reference `chat_history` in your prompts. You can then refer to previous inputs and outputs to create contextually relevant responses. Incorporating chat history into your prompts is essential for creating context-aware and engaging chatbot responses.
196198

197199
You can use the Jinja language [for-loop](https://jinja.palletsprojects.com/en/3.1.x/templates/#for) grammar to display a list of inputs and outputs from `chat_history`.
198200

1.64 KB
Loading
-40.6 KB
Loading
7.25 KB
Loading

0 commit comments

Comments
 (0)