Updated Try it Out to reference correct names and updated image. Ens… (#169)

Cortex-DMS · Donna-Marie Smith · web-flow · commit 496a0e8313fe · 2024-10-09T17:00:02.000+01:00
Updated Try it Out to use correct names and updated image and ensured all previous upgrade try it outs have the old image and naming

---------

Co-authored-by: Donna-Marie Smith &lt;donna.smith@wearecortex.com&gt;
diff --git a/content/en/docs/2024.9/Guides/upgrade-cortex/2024.1-to-2024.3/multiple-server-with-ha/try-it-out.md b/content/en/docs/2024.9/Guides/upgrade-cortex/2024.1-to-2024.3/multiple-server-with-ha/try-it-out.md
@@ -9,7 +9,7 @@ weight: 60
 
 This guide describes how to try out an upgraded {{% ctx %}} to make sure it is working. Please ensure that both the [Application Servers and Load Balancer Upgrade][] and [Web Application Server Upgrade][] has been completed before taking these steps.
 
-{{< section "/upgrade/try-it-out/test-upgrade.md" >}}
+{{< section "/upgrade/2024.3/upgrade-web-application-server/test-upgrade.md" >}}
 
 ## Test Executing Production Flows
 
diff --git a/content/en/docs/2024.9/Guides/upgrade-cortex/2024.1-to-2024.3/single-server-without-ha/try-it-out.md b/content/en/docs/2024.9/Guides/upgrade-cortex/2024.1-to-2024.3/single-server-without-ha/try-it-out.md
@@ -9,7 +9,7 @@ weight: 60
 
 This guide describes how to try out an upgraded {{% ctx %}} to make sure it is working. Please ensure that both the [Application Server Upgrade][] and [Web Application Server Upgrade][] has been completed before taking these steps.
 
-{{< section "/upgrade/try-it-out/test-upgrade.md" >}}
+{{< section "/upgrade/2024.3/upgrade-web-application-server/test-upgrade.md" >}}
 
 ## Test Executing Production Flows
 
diff --git a/content/en/docs/2024.9/Guides/upgrade-cortex/2024.3-to-2024.5/multiple-server-with-ha/try-it-out.md b/content/en/docs/2024.9/Guides/upgrade-cortex/2024.3-to-2024.5/multiple-server-with-ha/try-it-out.md
@@ -9,7 +9,7 @@ weight: 60
 
 This guide describes how to try out an upgraded {{% ctx %}} to make sure it is working. Please ensure that both the [Application Servers and Load Balancer Upgrade][] and [Web Application Server Upgrade][] has been completed before taking these steps.
 
-{{< section "/upgrade/try-it-out/test-upgrade.md" >}}
+{{< section "/upgrade/2024.5/upgrade-web-application-server/test-upgrade.md" >}}
 
 ## Test Executing Production Flows
 
diff --git a/content/en/docs/2024.9/Guides/upgrade-cortex/2024.3-to-2024.5/single-server-without-ha/try-it-out.md b/content/en/docs/2024.9/Guides/upgrade-cortex/2024.3-to-2024.5/single-server-without-ha/try-it-out.md
@@ -9,7 +9,7 @@ weight: 60
 
 This guide describes how to try out an upgraded {{% ctx %}} to make sure it is working. Please ensure that both the [Application Server Upgrade][] and [Web Application Server Upgrade][] has been completed before taking these steps.
 
-{{< section "/upgrade/try-it-out/test-upgrade.md" >}}
+{{< section "/upgrade/2024.5/upgrade-web-application-server/test-upgrade.md" >}}
 
 ## Test Executing Production Flows
 
diff --git a/content/en/docs/2024.9/Guides/upgrade-cortex/2024.5-to-2024.7/multiple-server-with-ha/try-it-out.md b/content/en/docs/2024.9/Guides/upgrade-cortex/2024.5-to-2024.7/multiple-server-with-ha/try-it-out.md
@@ -9,7 +9,7 @@ weight: 60
 
 This guide describes how to try out an upgraded {{% ctx %}} to make sure it is working. Please ensure that both the [Application Servers and Load Balancer Upgrade][] and [Web Application Server Upgrade][] has been completed before taking these steps.
 
-{{< section "/upgrade/try-it-out/test-upgrade.md" >}}
+{{< section "/upgrade/2024.7/upgrade-web-application-server/test-upgrade.md" >}}
 
 ## Test Executing Production Flows
 
diff --git a/content/en/docs/2024.9/Guides/upgrade-cortex/2024.5-to-2024.7/single-server-without-ha/try-it-out.md b/content/en/docs/2024.9/Guides/upgrade-cortex/2024.5-to-2024.7/single-server-without-ha/try-it-out.md
@@ -9,7 +9,7 @@ weight: 60
 
 This guide describes how to try out an upgraded {{% ctx %}} to make sure it is working. Please ensure that both the [Application Server Upgrade][] and [Web Application Server Upgrade][] has been completed before taking these steps.
 
-{{< section "/upgrade/try-it-out/test-upgrade.md" >}}
+{{< section "/upgrade/2024.7/upgrade-web-application-server/test-upgrade.md" >}}
 
 ## Test Executing Production Flows
 
diff --git a/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/multiple-server-with-ha/try-it-out.md b/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/multiple-server-with-ha/try-it-out.md
@@ -9,7 +9,7 @@ weight: 60
 
 This guide describes how to try out an upgraded {{% ctx %}} to make sure it is working. Please ensure that both the [Application Servers and Load Balancer Upgrade][] and [Web Application Server Upgrade][] has been completed before taking these steps.
 
-{{< section "/upgrade/try-it-out/test-upgrade.md" >}}
+{{< section "/upgrade/2024.9/upgrade-web-application-server/test-upgrade.md" >}}
 
 ## Test Executing Production Flows
 
diff --git a/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/single-server-without-ha/try-it-out.md b/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/single-server-without-ha/try-it-out.md
@@ -9,7 +9,7 @@ weight: 60
 
 This guide describes how to try out an upgraded {{% ctx %}} to make sure it is working. Please ensure that both the [Application Server Upgrade][] and [Web Application Server Upgrade][] has been completed before taking these steps.
 
-{{< section "/upgrade/try-it-out/test-upgrade.md" >}}
+{{< section "/upgrade/2024.9/upgrade-web-application-server/test-upgrade.md" >}}
 
 ## Test Executing Production Flows
 
diff --git a/content/en/docs/2024.9/_shared/upgrade/2024.3/upgrade-web-application-server/test-upgrade.md b/content/en/docs/2024.9/_shared/upgrade/2024.3/upgrade-web-application-server/test-upgrade.md
@@ -8,7 +8,7 @@ Test the platform by creating a new flow and executing it using the following st
 1. Inside the group, click the `+` button again and click on `Flow` to open a dialog. If the menu item is not present, it means that the `FeatureFlags` in the `CortexGateway.SetParameters.xml` file was not set properly when installing Gateway. See [Troubleshooting][] for more information.
 1. Enter a name for the flow, configure the `Permission Groups` and click `OK` to create the flow.
 1. The flow should be displayed with a start flow block and end flow block, if those blocks are not displayed see [Troubleshooting][]. A list of block palettes should be displayed down the left hand side:
-    {{< figure src="/images/New Innovation Flow View.PNG" title="New Flow - Number of palettes may differ" >}}
+    {{< figure src="../../2024.3/images/New Innovation Flow View.PNG" title="New Flow - Number of palettes may differ" >}}
 1. Add a `Set Variable` block and connect it between the start and end blocks.
 1. Click the `Set Variable` block to open the Property Editor.
 1. Set the `Value` property to the expression `DateTimeOffset.Now`.
diff --git a/content/en/docs/2024.9/_shared/upgrade/2024.5/upgrade-web-application-server/test-upgrade.md b/content/en/docs/2024.9/_shared/upgrade/2024.5/upgrade-web-application-server/test-upgrade.md
@@ -0,0 +1,28 @@
+## Test Debugging Flows
+
+Test the platform by creating a new flow and executing it using the following steps:
+
+1. Click on the `Flows` charm, then the `+` button and click `Group` to open a dialog.
+1. Enter a name for the group, configure the `Permission Groups` and click `OK` to create the group.
+1. Click on the group to open it (refresh the page if it does not appear).
+1. Inside the group, click the `+` button again and click on `Flow` to open a dialog. If the menu item is not present, it means that the `FeatureFlags` in the `CortexGateway.SetParameters.xml` file was not set properly when installing Gateway. See [Troubleshooting][] for more information.
+1. Enter a name for the flow, configure the `Permission Groups` and click `OK` to create the flow.
+1. The flow should be displayed with a start flow block and end flow block, if those blocks are not displayed see [Troubleshooting][]. A list of block palettes should be displayed down the left hand side:
+    {{< figure src="../../2024.5/images/New Innovation Flow View.PNG" title="New Flow - Number of palettes may differ" >}}
+1. Add a `Set Variable` block and connect it between the start and end blocks.
+1. Click the `Set Variable` block to open the Property Editor.
+1. Set the `Value` property to the expression `DateTimeOffset.Now`.
+1. Type `Result` into the `Variable` property and click `Create Result`.
+1. In the Variable Editor, set `Is Output Variable?` to `true` for the new `Result` variable.
+1. Set a breakpoint on the end block and start the flow. An execution token should appear, the `Result` variable should show the current time. If the token does not appear, try refreshing the page. Failing that, see [Troubleshooting][].
+1. Continue or stop the execution.
+1. Commit the flow.
+
+## Test Publishing Production Flows
+
+1. Log in to Gateway with a user that has the `Admin` role.
+1. Click on the `Settings` charm, then `Packages`.
+1. Click `Add Package Definition`. Enter a package name and select the new flow to add to the package. Click `Save` to save the new package.
+1. Click `Publish`. A success message should appear. If it doesn't it means that there is a problem with the configuration in the `web.config` file for {{% ctx %}} Gateway, or the Application Services aren't healthy. See [Troubleshooting][] for more information.
+
+[Troubleshooting]: {{< url path="Cortex.Reference.Troubleshooting.Upgrade.TroubleshootingDuringUpgrade" >}}
diff --git a/content/en/docs/2024.9/_shared/upgrade/2024.7/upgrade-web-application-server/test-upgrade.md b/content/en/docs/2024.9/_shared/upgrade/2024.7/upgrade-web-application-server/test-upgrade.md
@@ -0,0 +1,28 @@
+## Test Debugging Flows
+
+Test the platform by creating a new flow and executing it using the following steps:
+
+1. Click on the `Flows` charm, then the `+` button and click `Group` to open a dialog.
+1. Enter a name for the group, configure the `Permission Groups` and click `OK` to create the group.
+1. Click on the group to open it (refresh the page if it does not appear).
+1. Inside the group, click the `+` button again and click on `Flow` to open a dialog. If the menu item is not present, it means that the `FeatureFlags` in the `CortexGateway.SetParameters.xml` file was not set properly when installing Gateway. See [Troubleshooting][] for more information.
+1. Enter a name for the flow, configure the `Permission Groups` and click `OK` to create the flow.
+1. The flow should be displayed with a start flow block and end flow block, if those blocks are not displayed see [Troubleshooting][]. A list of block palettes should be displayed down the left hand side:
+    {{< figure src="../../2024.7/images/New Innovation Flow View.PNG" title="New Flow - Number of palettes may differ" >}}
+1. Add a `Set Variable` block and connect it between the start and end blocks.
+1. Click the `Set Variable` block to open the Property Editor.
+1. Set the `Value` property to the expression `DateTimeOffset.Now`.
+1. Type `Result` into the `Variable` property and click `Create Result`.
+1. In the Variable Editor, set `Is Output Variable?` to `true` for the new `Result` variable.
+1. Set a breakpoint on the end block and start the flow. An execution token should appear, the `Result` variable should show the current time. If the token does not appear, try refreshing the page. Failing that, see [Troubleshooting][].
+1. Continue or stop the execution.
+1. Commit the flow.
+
+## Test Publishing Production Flows
+
+1. Log in to Gateway with a user that has the `Admin` role.
+1. Click on the `Settings` charm, then `Packages`.
+1. Click `Add Package Definition`. Enter a package name and select the new flow to add to the package. Click `Save` to save the new package.
+1. Click `Publish`. A success message should appear. If it doesn't it means that there is a problem with the configuration in the `web.config` file for {{% ctx %}} Gateway, or the Application Services aren't healthy. See [Troubleshooting][] for more information.
+
+[Troubleshooting]: {{< url path="Cortex.Reference.Troubleshooting.Upgrade.TroubleshootingDuringUpgrade" >}}
diff --git a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/test-upgrade.md b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/test-upgrade.md
@@ -0,0 +1,31 @@
+## Test Debugging Flows
+
+Test the platform by creating a new flow and executing it using the following steps:
+
+1. Click on the `Dev` charm, then the `+` button and click `Group` to open a dialog.
+1. Enter a name for the group, configure the `Permission Groups` and click `OK` to create the group.
+1. Click on the group to open it (refresh the page if it does not appear).
+1. Inside the group, click the `+` button again and click on `Activity` to open a dialog. If the menu item is not present, it means that the `FeatureFlags` in the `CortexGateway.SetParameters.xml` file was not set properly when installing Gateway. See [Troubleshooting][] for more information.
+1. Enter a name for the flow, configure the `Permission Groups` and click `OK` to create the flow.
+1. The flow should be displayed with a `Start Flow` block and `End Flow` block, if those blocks are not displayed see [Troubleshooting][]. A list of block palettes should be displayed down the left hand side:
+    {{< figure src="../../2024.9/images/New Innovation Flow View.PNG" title="New Flow - Number of palettes may differ" >}}
+1. Add a `Set Variable` block and connect it between the `Start Flow` and `End Flow` blocks.
+1. Click the `Set Variable` block to open the Property Editor.
+1. Set the `Value` property to the expression `DateTimeOffset.Now`.
+1. Type `Result` into the `Variable` property and click `Create Result`.
+1. In the Variables Grid, set `Is Output Variable?` to `true` for the new `Result` variable.
+1. Add a breakpoint to the `End Flow` block and start the flow. An execution token should appear.
+   If the token does not appear, try refreshing the page. Failing that, see [Troubleshooting][].
+1. Select the execution in the Executions Grid (bottom panel).
+1. The `Result` variable displayed in the Variables Viewer (right panel) should show the current time.
+1. Continue or stop the execution.
+1. Commit the flow.
+
+## Test Publishing Production Flows
+
+1. Log in to Gateway with a user that has the `Admin` role.
+1. Click on the `Admin` charm, then `Packages`.
+1. Click `Add Package Definition`. Enter a package name and select the new flow to add to the package. Click `Save` to save the new package.
+1. Click `Publish`. A success message should appear. If it doesn't it means that there is a problem with the configuration in the `web.config` file for {{% ctx %}} Gateway, or the Application Services aren't healthy. See [Troubleshooting][] for more information.
+
+[Troubleshooting]: {{< url path="Cortex.Reference.Troubleshooting.Upgrade.TroubleshootingDuringUpgrade" >}}
diff --git a/content/en/docs/2024.9/getting-started/on-premise/add-innovation-to-72/multiple-server-with-ha/try-it-out.md b/content/en/docs/2024.9/getting-started/on-premise/add-innovation-to-72/multiple-server-with-ha/try-it-out.md
@@ -13,26 +13,29 @@ This guide describes how to try out a new Innovation installation to make sure i
 
 Test the platform by creating a new flow and executing it using the following steps:
 
-1. Click on the `Flows` charm, then the `+` button and click `Group` to open a dialog.
+1. Click on the `Dev` charm, then the `+` button and click `Group` to open a dialog.
 1. Enter a name for the group, configure the `Permission Groups` and click `OK` to create the group.
 1. Click on the group to open it (refresh the page if it does not appear).
-1. Inside the group, click the `+` button again and click on <code>Flow<sup>(Innovation)</sup></code> to open a dialog. If the menu item is not present, it means that the `FeatureFlags` in the `CortexGateway.SetParameters.xml` file was not set properly when installing Gateway. See [Troubleshooting][Troubleshooting No Innovation] for more information.
+1. Inside the group, click the `+` button again and click on `Activity` to open a dialog. If the menu item is not present, it means that the `FeatureFlags` in the `CortexGateway.SetParameters.xml` file was not set properly when installing Gateway. See [Troubleshooting][Troubleshooting No Innovation] for more information.
 1. Enter a name for the flow, configure the `Permission Groups` and click `OK` to create the flow.
-1. The flow should be displayed with a start flow block and end flow block. A list of block palettes should be displayed down the left hand side:
+1. The flow should be displayed with a `Start Flow` block and `End Flow` block, if those blocks are not displayed see [Troubleshooting][Troubleshooting Flow No Blocks]. A list of block palettes should be displayed down the left hand side:
     {{< figure src="/images/New Innovation Flow View.PNG" title="New Flow - Number of palettes may differ" >}}
-1. Add a `Set Variable` block and connect it between the start and end blocks.
+1. Add a `Set Variable` block and connect it between the `Start Flow` and `End Flow` blocks.
 1. Click the `Set Variable` block to open the Property Editor.
 1. Set the `Value` property to the expression `DateTimeOffset.Now`.
 1. Type `Result` into the `Variable` property and click `Create Result`.
-1. In the Variable Editor, set `Is Output Variable?` to `true` for the new `Result` variable.
-1. Set a breakpoint on the end block and start the flow. An execution token should appear, the `Result` variable should show the current time. If the token does not appear, try refreshing the page.
+1. In the Variables Grid, set `Is Output Variable?` to `true` for the new `Result` variable.
+1. Add a breakpoint to the `End Flow` block and start the flow. An execution token should appear.
+   If the token does not appear, try refreshing the page. Failing that, see [Troubleshooting][Troubleshooting Flow Not Starting].
+1. Select the execution in the Executions Grid (bottom panel).
+1. The `Result` variable displayed in the Variables Viewer (right panel) should show the current time.
 1. Continue or stop the execution.
 1. Commit the flow.
 
 ## Test Publishing Production Flows
 
 1. Log in to Gateway with a user that has the `Admin` role.
-1. Click on the `Settings` charm, then `Packages`.
+1. Click on the `Admin` charm, then `Packages`.
 1. Click `Add Package Definition`. Enter a package name and select the new flow to add to the package. Click `Save` to save the new package.
 1. Click `Publish`. A success message should appear. If it doesn't it means that either one or more of the parameters prefixed with `Service Fabric` in the `CortexGateway.SetParameters.xml` file was not set properly when updating Gateway, or the Application Services aren't healthy. See [Troubleshooting][Troubleshooting No Publish] for more information.
 
@@ -55,6 +58,8 @@ Test the platform by creating a new flow and executing it using the following st
 1. {{% ctx %}} Innovation has now been verified and is ready to use.
 
 [Troubleshooting During Installation]: {{< url path="Cortex.Reference.Troubleshooting.Installation.TroubleshootingDuringInstallation" >}}
+[Troubleshooting Flow No Blocks]: {{< url path="Cortex.Reference.Troubleshooting.Installation.TroubleshootingFlowNoBlocks" >}}
+[Troubleshooting Flow Not Starting]: {{< url path="Cortex.Reference.Troubleshooting.Installation.TroubleshootingFlowNotStarting" >}}
 [Troubleshooting No Innovation]: {{< url path="Cortex.Reference.Troubleshooting.Installation.TroubleshootingNoInnovation" >}}
 [Troubleshooting No Publish]: {{< url path="Cortex.Reference.Troubleshooting.Installation.TroubleshootingNoPublish" >}}
 [Troubleshooting Root Certificate Error]: {{< url path="Cortex.Reference.Troubleshooting.Installation.TroubleshootingNoRootCertificate" >}}
diff --git a/content/en/docs/2024.9/getting-started/on-premise/add-innovation-to-72/single-server-without-ha/try-it-out.md b/content/en/docs/2024.9/getting-started/on-premise/add-innovation-to-72/single-server-without-ha/try-it-out.md
diff --git a/content/en/docs/2024.9/getting-started/on-premise/install-innovation-only/multiple-server-with-ha/try-it-out.md b/content/en/docs/2024.9/getting-started/on-premise/install-innovation-only/multiple-server-with-ha/try-it-out.md
diff --git a/content/en/docs/2024.9/getting-started/on-premise/install-innovation-only/single-server-without-ha/try-it-out.md b/content/en/docs/2024.9/getting-started/on-premise/install-innovation-only/single-server-without-ha/try-it-out.md
diff --git a/content/static/2024.9/images/New Innovation Flow View.PNG b/content/static/2024.9/images/New Innovation Flow View.PNG
