Skip to content

Commit 1f156e6

Browse files
author
Donna-Marie Smith
committed
Fixed up header Menu issues on Try It Out for upgrades
1 parent d7ce879 commit 1f156e6

File tree

4 files changed

+20
-11
lines changed

4 files changed

+20
-11
lines changed

content/en/docs/2025.1/Guides/upgrade-cortex/2024.11-to-2025.1/multiple-server-with-ha/try-it-out.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,13 @@ weight: 60
99

1010
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.
1111

12-
{{< section "/upgrade/2025.1/upgrade-web-application-server/test-upgrade.md" >}}
12+
## Test Debugging Flows
13+
14+
{{< section "/upgrade/try-it-out/test-debugging-flows.md" >}}
15+
16+
## Test Publishing Production Flows
17+
18+
{{< section "/upgrade/try-it-out/test-publishing-flows.md" >}}
1319

1420
## Test Executing Production Flows
1521

content/en/docs/2025.1/Guides/upgrade-cortex/2024.11-to-2025.1/single-server-without-ha/try-it-out.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,13 @@ weight: 60
99

1010
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.
1111

12-
{{< section "/upgrade/2025.1/upgrade-web-application-server/test-upgrade.md" >}}
12+
## Test Debugging Flows
13+
14+
{{< section "/upgrade/try-it-out/test-debugging-flows.md" >}}
15+
16+
## Test Publishing Production Flows
17+
18+
{{< section "/upgrade/try-it-out/test-publishing-flows.md" >}}
1319

1420
## Test Executing Production Flows
1521

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
## Test Debugging Flows
2-
31
Test the platform by creating a new flow and executing it using the following steps:
42

53
1. Click on the `Dev` charm, then the `+` button and click `Group` to open a dialog.
@@ -21,11 +19,4 @@ Test the platform by creating a new flow and executing it using the following st
2119
1. Continue or stop the execution.
2220
1. Commit the flow.
2321

24-
## Test Publishing Production Flows
25-
26-
1. Log in to Gateway with a user that has the `Admin` role.
27-
1. Click on the `Admin` charm, then `Packages`.
28-
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.
29-
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.
30-
3122
[Troubleshooting]: {{< url path="Cortex.Reference.Troubleshooting.Upgrade.TroubleshootingDuringUpgrade" >}}
Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
1. Log in to Gateway with a user that has the `Admin` role.
2+
1. Click on the `Admin` charm, then `Packages`.
3+
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.
4+
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.
5+
6+
[Troubleshooting]: {{< url path="Cortex.Reference.Troubleshooting.Upgrade.TroubleshootingDuringUpgrade" >}}

0 commit comments

Comments
 (0)