diff --git a/docs/docs/workflows/nodes.md b/docs/docs/workflows/nodes.md
index fe861524a8..ec97cafeca 100644
--- a/docs/docs/workflows/nodes.md
+++ b/docs/docs/workflows/nodes.md
@@ -24,7 +24,7 @@ The **If condition** node triggers one of the outgoing flows depending on the gi
-
- If you click on the If condition node, a dialog box will appear on the right that accepts a logical expression. diff --git a/docs/docs/workflows/overview.md b/docs/docs/workflows/overview.md index 66d2ea6b2a..e5c8065dbd 100644 --- a/docs/docs/workflows/overview.md +++ b/docs/docs/workflows/overview.md @@ -43,7 +43,7 @@ For this guide, we've created a MonthlySales table in PostgreSQL with 5 columns We can now see a node named *postgresql1* connected to the outgoing flow of the **Start trigger** node on the canvas. Click on the *postgresql1* node, a dialog box will show up on the right. -
- Click on the input field next to the PostgreSQL logo and rename the node to fetchSalesData. @@ -77,7 +77,7 @@ Create an outgoing flow from the *fetchSalesData* node that we just created by c The **JavaScript** node lets you run JavaScript code to transform data and perform other tasks. The JavaScript code executes on the server side to protect sensitive logic and data from exposure to the client. In our example, we are using it to convert the result from the previous node into a string. -
- In the JavaScript node, the data retrieved from the fetchSalesData node can be accessed using the property - fetchSalesData.data. @@ -146,7 +146,7 @@ The **If condition** node accepts a logical expression and evaluates it. The out Click on the **If condition** node, a dialog box will appear on the right. -
- Enter the below logical expression in the input area:
@@ -229,5 +229,3 @@ Continue learning about the different elements of ToolJet Workflows using the be
**[Overview of Logs](/docs/workflows/logs)**
**[Permissions in Workflows](/docs/workflows/permissions)**
-
-
diff --git a/docs/versioned_docs/version-2.14.0/workflows/nodes.md b/docs/versioned_docs/version-2.14.0/workflows/nodes.md
index fe861524a8..ec97cafeca 100644
--- a/docs/versioned_docs/version-2.14.0/workflows/nodes.md
+++ b/docs/versioned_docs/version-2.14.0/workflows/nodes.md
@@ -24,7 +24,7 @@ The **If condition** node triggers one of the outgoing flows depending on the gi
- If you click on the If condition node, a dialog box will appear on the right that accepts a logical expression. diff --git a/docs/versioned_docs/version-2.14.0/workflows/overview.md b/docs/versioned_docs/version-2.14.0/workflows/overview.md index 00639ba3b1..e5c8065dbd 100644 --- a/docs/versioned_docs/version-2.14.0/workflows/overview.md +++ b/docs/versioned_docs/version-2.14.0/workflows/overview.md @@ -43,7 +43,7 @@ For this guide, we've created a MonthlySales table in PostgreSQL with 5 columns We can now see a node named *postgresql1* connected to the outgoing flow of the **Start trigger** node on the canvas. Click on the *postgresql1* node, a dialog box will show up on the right. -
- Click on the input field next to the PostgreSQL logo and rename the node to fetchSalesData. @@ -77,7 +77,7 @@ Create an outgoing flow from the *fetchSalesData* node that we just created by c The **JavaScript** node lets you run JavaScript code to transform data and perform other tasks. The JavaScript code executes on the server side to protect sensitive logic and data from exposure to the client. In our example, we are using it to convert the result from the previous node into a string. -
- In the JavaScript node, the data retrieved from the fetchSalesData node can be accessed using the property - fetchSalesData.data. @@ -146,7 +146,7 @@ The **If condition** node accepts a logical expression and evaluates it. The out Click on the **If condition** node, a dialog box will appear on the right. -
- Enter the below logical expression in the input area: