Skip to content

Commit 631cd5d

Browse files
committed
Corrections based on editor comments
1 parent 518a4c6 commit 631cd5d

File tree

2 files changed

+14
-6
lines changed

2 files changed

+14
-6
lines changed

articles/data-explorer/flow-usage.md

Lines changed: 10 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -69,12 +69,12 @@ Follow these instructions to create a similar Flow:
6969
1. From the dynamic content window, select the parameter you want to use as a condition for next actions.
7070
1. Select the type of *Relationship* and *Value* to set a specific condition on the given parameter.
7171

72-
![](./media/flow-usage/flow-condition.png "Flow conditions")(./media/flow-usage/flow-condition.png#lightbox)
72+
[!(./media/flow-usage/flow-condition.png "Flow conditions")](./media/flow-usage/flow-condition.png#lightbox)
7373

7474
Flow applies this condition on each row of the query result table.
7575
1. Add actions for when the condition is true and false.
7676

77-
![](./media/flow-usage/flow-conditionactions.png "Flow condition actions")(./media/flow-usage/flow-conditionactions.png#lightbox)
77+
[![(./media/flow-usage/flow-conditionactions.png "Flow condition actions")](./media/flow-usage/flow-conditionactions.png#lightbox)
7878

7979
You can use the result values from the Kusto query as input for the next actions. Select the result values from the dynamic content window.
8080
In the example below, a Slack - Post Message action and Visual Studio - Create a new work item action containing data from the Kusto query were added.
@@ -100,7 +100,7 @@ Visualize this information as a pie chart and email it to the team.
100100
1. Add a new step, with one or more Kusto - Run query and visualize results actions.
101101

102102
![Run several queries in a flow](./media/flow-usage/flow-severalqueries.png)
103-
1. For each*Kusto - Run query and visualize result, define the following fields:
103+
1. For each Kusto - Run query and visualize result, define the following fields:
104104
* Cluster URL (in the *Cluster Name* field)
105105
* Database Name
106106
* Query and Chart Type (HTML Table/ Pie Chart/ Time Chart/ Bar Chart/ Enter Custom Value).
@@ -117,9 +117,9 @@ Visualize this information as a pie chart and email it to the team.
117117

118118
Results:
119119

120-
![Results of multiple attachments](./media/flow-usage/flow-resultsmultipleattachments.png)(./media/flow-usage/flow-resultsmultipleattachments.png#lightbox)
120+
[![Results of multiple attachments](./media/flow-usage/flow-resultsmultipleattachments.png)](./media/flow-usage/flow-resultsmultipleattachments.png#lightbox)
121121

122-
![Results of multiple attachments](./media/flow-usage/flow-resultsmultipleattachments2.png)(./media/flow-usage/flow-resultsmultipleattachments2.png#lightbox)
122+
[![Results of multiple attachments](./media/flow-usage/flow-resultsmultipleattachments2.png)](./media/flow-usage/flow-resultsmultipleattachments2.png#lightbox)
123123

124124
## Send a different email to different contacts
125125

@@ -169,7 +169,7 @@ Follow these instructions to create a similar Flow:
169169

170170
```if(equals(items('Apply_to_each')?['Level'], 'Warning'), 'Yellow', if(equals(items('Apply_to_each')?['Level'], 'Error'), 'red', 'white'))```
171171

172-
![Create HTML table loop content](./media/flow-usage/flow-createhtmltableloopcontent.png)(./media/flow-usage/flow-createhtmltableloopcontent.png#lightbox)
172+
[![Create HTML table loop content](./media/flow-usage/flow-createhtmltableloopcontent.png)](./media/flow-usage/flow-createhtmltableloopcontent.png#lightbox)
173173

174174
1. Create the full HTML content:
175175
1. Add a new action outside Apply to each.
@@ -182,3 +182,7 @@ Follow these instructions to create a similar Flow:
182182
Result:
183183

184184
![Custom HTML table email result](./media/flow-usage/flow-customhtmltableresult.png)
185+
186+
## Next steps
187+
188+
Learn about the [Microsoft Azure Explorer Logic App connector](https://docs.microsoft.com/azure/kusto/tools/logicapps) which is another way to run Kusto queries and commands automatically as part of a scheduled or triggered task.

articles/data-explorer/flow.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -198,3 +198,7 @@ For more information, read about [Query best practices](https://docs.microsoft.c
198198
* Results returned to the client are limited to 500,000 records. The overall memory for those records can't exceed 64 MB and seven-minutes execution time.
199199
* The connector does not support the [fork](https://docs.microsoft.com/azure/kusto/query/forkoperator) and [facet](https://docs.microsoft.com/azure/kusto/query/facetoperator) operators.
200200
* Flow works best on Microsoft Edge and Chrome.
201+
202+
## Next steps
203+
204+
Learn about the [Microsoft Azure Explorer Logic App connector](https://docs.microsoft.com/azure/kusto/tools/logicapps) which is another way to run Kusto queries and commands automatically as part of a scheduled or triggered task.

0 commit comments

Comments
 (0)