From c6ccc13813f8f6cb882ea9cb388d0f746f9672b3 Mon Sep 17 00:00:00 2001 From: senurah Date: Wed, 15 Oct 2025 14:53:39 +0530 Subject: [PATCH 1/7] Add docs for manually testing automation with dynamic arguments --- .../schedule-your-first-automation.md | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/en/docs/quick-start-guides/schedule-your-first-automation.md b/en/docs/quick-start-guides/schedule-your-first-automation.md index 9afe3ca8..184e20db 100644 --- a/en/docs/quick-start-guides/schedule-your-first-automation.md +++ b/en/docs/quick-start-guides/schedule-your-first-automation.md @@ -49,6 +49,31 @@ This redirects you to the **Create New Integration in VS Code** page. 3. Add an appropriate commit message and commit. 4. Click **Sync Changes** to push the changes to remote. +## Optional: Test the Automation manually + +1. In the left navigation menu, click **Execute**. +2. Click **Run Now**. This triggers the task. + + !!! info "Inject Dynamic Values into Your Application as Command-Line Arguments" + If you want to inject dynamic values into your application as command-line arguments when you run a manual task, follow these steps: + 1. Click the drop-down icon next to **Run Now** and then click **Run with Arguments**. + 2. In the **Runtime Arguments** pane, enter the arguments you want to pass to your application. + 3. Click **Execute**. This triggers the task with the specified arguments. + + The capability to run a manual task with arguments is supported for the following build presets: + + === "WSO2 MI" + To explore a WSO2 MI-based manual task with arguments, try out the [Weather to Logs Task](https://github.com/wso2/choreo-samples/tree/main/weather-to-logs-mi-manual-task) sample. For instructions, see the `readme.md` file in the sample repository. + + !!! info + When working on WSO2 MI projects and deploying a WSO2 MI integration as a manual task in Choreo, use the WSO2 MI automation mode. For details, see [Running the Micro Integrator in Automation Mode](https://apim.docs.wso2.com/en/latest/install-and-setup/install/running-the-mi-in-automation-mode/). + + === "Ballerina" + To explore a Ballerina manual task with arguments, try out the [Weather to Email Task](https://github.com/wso2/choreo-samples/tree/main/weather-to-email-integration) sample. For instructions, see the README.md file in the sample repository. + + !!! info + If you want to pass arguments to Ballerina main functions, use the **Run with Arguments** capability. For details on the arguments you can pass, see the [Ballerina documentation](https://ballerina.io/learn/by-example/main-function/). You can also override configurable values in the same manner. For more information, see [Provide values to configurable variables](https://ballerina.io/learn/provide-values-to-configurable-variables/#provide-via-command-line-arguments). + ## Step 5: Schedule Automation 1. Once you push the changes, the overview page of the Devant automation will automatically refresh and show you the **Latest Commit** and automatically build your automation showing the **Build Status**. From 35e0921c6e76b4962df21f72f667828be05baee7 Mon Sep 17 00:00:00 2001 From: senurah Date: Wed, 15 Oct 2025 17:39:32 +0530 Subject: [PATCH 2/7] Add testing instructions for automation in the overview page --- .../schedule-your-first-automation.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/en/docs/quick-start-guides/schedule-your-first-automation.md b/en/docs/quick-start-guides/schedule-your-first-automation.md index 184e20db..b9c5acd5 100644 --- a/en/docs/quick-start-guides/schedule-your-first-automation.md +++ b/en/docs/quick-start-guides/schedule-your-first-automation.md @@ -51,11 +51,14 @@ This redirects you to the **Create New Integration in VS Code** page. ## Optional: Test the Automation manually -1. In the left navigation menu, click **Execute**. -2. Click **Run Now**. This triggers the task. +You can test your automation directly from the **Development** card on the **Overview** page: + +1. On the Overview page, locate the **Development** card. +2. Click **Test** to run your automation immediately. !!! info "Inject Dynamic Values into Your Application as Command-Line Arguments" - If you want to inject dynamic values into your application as command-line arguments when you run a manual task, follow these steps: + To pass dynamic values to your application when testing manually,follow these steps: + 1. Click the drop-down icon next to **Run Now** and then click **Run with Arguments**. 2. In the **Runtime Arguments** pane, enter the arguments you want to pass to your application. 3. Click **Execute**. This triggers the task with the specified arguments. @@ -73,6 +76,8 @@ This redirects you to the **Create New Integration in VS Code** page. !!! info If you want to pass arguments to Ballerina main functions, use the **Run with Arguments** capability. For details on the arguments you can pass, see the [Ballerina documentation](https://ballerina.io/learn/by-example/main-function/). You can also override configurable values in the same manner. For more information, see [Provide values to configurable variables](https://ballerina.io/learn/provide-values-to-configurable-variables/#provide-via-command-line-arguments). + !!! note + As user portal features are added, testing and other actions will be accessible directly from the **Overview** page, making it easier to manage and validate your automations. ## Step 5: Schedule Automation From 298cf0dd4fe14d1a674dc7e7a2aa30ab4588694d Mon Sep 17 00:00:00 2001 From: senurah Date: Thu, 16 Oct 2025 08:53:21 +0530 Subject: [PATCH 3/7] Add testing instructions for manual tasks with dynamic arguments --- .../schedule-your-first-automation.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/en/docs/quick-start-guides/schedule-your-first-automation.md b/en/docs/quick-start-guides/schedule-your-first-automation.md index b9c5acd5..958ace7d 100644 --- a/en/docs/quick-start-guides/schedule-your-first-automation.md +++ b/en/docs/quick-start-guides/schedule-your-first-automation.md @@ -57,25 +57,25 @@ You can test your automation directly from the **Development** card on the **Ove 2. Click **Test** to run your automation immediately. !!! info "Inject Dynamic Values into Your Application as Command-Line Arguments" - To pass dynamic values to your application when testing manually,follow these steps: + To pass dynamic values to your application when testing manually, follow these steps: - 1. Click the drop-down icon next to **Run Now** and then click **Run with Arguments**. + 1. Click the drop-down icon next to **Test** and then click **Test with Arguments**. 2. In the **Runtime Arguments** pane, enter the arguments you want to pass to your application. 3. Click **Execute**. This triggers the task with the specified arguments. The capability to run a manual task with arguments is supported for the following build presets: === "WSO2 MI" - To explore a WSO2 MI-based manual task with arguments, try out the [Weather to Logs Task](https://github.com/wso2/choreo-samples/tree/main/weather-to-logs-mi-manual-task) sample. For instructions, see the `readme.md` file in the sample repository. + To explore a WSO2 MI-based manual task with arguments, try out the [Weather to Logs Task](https://github.com/wso2/choreo-samples/tree/main/weather-to-logs-mi-manual-task) sample. For instructions, see the `README.md` file in the sample repository. !!! info - When working on WSO2 MI projects and deploying a WSO2 MI integration as a manual task in Choreo, use the WSO2 MI automation mode. For details, see [Running the Micro Integrator in Automation Mode](https://apim.docs.wso2.com/en/latest/install-and-setup/install/running-the-mi-in-automation-mode/). + When working on WSO2 MI projects and deploying a WSO2 MI integration as a manual task in Choreo, use the WSO2 MI automation mode. For details, see [Running the Micro Integrator in Automation Mode](https://mi.docs.wso2.com/en/latest/install-and-setup/install/running-the-mi-in-automation-mode/). === "Ballerina" - To explore a Ballerina manual task with arguments, try out the [Weather to Email Task](https://github.com/wso2/choreo-samples/tree/main/weather-to-email-integration) sample. For instructions, see the README.md file in the sample repository. + To explore a Ballerina manual task with arguments, try out the [Weather to Email Task](https://github.com/wso2/choreo-samples/tree/main/weather-to-email-integration) sample. For instructions, see the `README.md` file in the sample repository. !!! info - If you want to pass arguments to Ballerina main functions, use the **Run with Arguments** capability. For details on the arguments you can pass, see the [Ballerina documentation](https://ballerina.io/learn/by-example/main-function/). You can also override configurable values in the same manner. For more information, see [Provide values to configurable variables](https://ballerina.io/learn/provide-values-to-configurable-variables/#provide-via-command-line-arguments). + If you want to pass arguments to Ballerina main functions, use the **Test with Arguments** capability. For details on the arguments you can pass, see the [Ballerina documentation](https://ballerina.io/learn/by-example/main-function/). You can also override configurable values in the same manner. For more information, see [Provide values to configurable variables](https://ballerina.io/learn/provide-values-to-configurable-variables/#provide-via-command-line-arguments). !!! note As user portal features are added, testing and other actions will be accessible directly from the **Overview** page, making it easier to manage and validate your automations. From 31897f3d1b0eb086336d5536e46208f4a1dae2c7 Mon Sep 17 00:00:00 2001 From: senurah Date: Thu, 16 Oct 2025 09:21:16 +0530 Subject: [PATCH 4/7] Update production automation instructions --- .../quick-start-guides/schedule-your-first-automation.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/en/docs/quick-start-guides/schedule-your-first-automation.md b/en/docs/quick-start-guides/schedule-your-first-automation.md index 958ace7d..48cef6f7 100644 --- a/en/docs/quick-start-guides/schedule-your-first-automation.md +++ b/en/docs/quick-start-guides/schedule-your-first-automation.md @@ -100,7 +100,12 @@ You can test your automation directly from the **Development** card on the **Ove 10. After successfully testing, you can promote your automation to production by clicking the **Promote** button. -11. In critical environments (Production), you will be able to see automation metrics such as: +11. Once promoted to production, click **Run** to run your automation immediately. + + !!!info + If you want to pass runtime arguments when running in production, use the **Run with Arguments** option in the same way as described above in the [Test the Automation manually](#optional-test-the-automation-manually) section. + +12. In critical environments (Production), you will be able to see automation metrics such as: - **Error Rate**: Percentage of failed executions - **Average Duration**: Average time taken for executions From 5d1f6c1647ca29787911e9db99b74ccf7d265142 Mon Sep 17 00:00:00 2001 From: Chiran Fernando Date: Thu, 16 Oct 2025 14:13:22 +0530 Subject: [PATCH 5/7] Update en/docs/quick-start-guides/schedule-your-first-automation.md --- en/docs/quick-start-guides/schedule-your-first-automation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/en/docs/quick-start-guides/schedule-your-first-automation.md b/en/docs/quick-start-guides/schedule-your-first-automation.md index 48cef6f7..af8aea6a 100644 --- a/en/docs/quick-start-guides/schedule-your-first-automation.md +++ b/en/docs/quick-start-guides/schedule-your-first-automation.md @@ -51,7 +51,7 @@ This redirects you to the **Create New Integration in VS Code** page. ## Optional: Test the Automation manually -You can test your automation directly from the **Development** card on the **Overview** page: +You can execute your automation directly from the environment card on the **Overview** page: 1. On the Overview page, locate the **Development** card. 2. Click **Test** to run your automation immediately. From 6b864eea7e02522a15edefeeae0fb61371d7b078 Mon Sep 17 00:00:00 2001 From: senurah Date: Thu, 23 Oct 2025 11:57:29 +0530 Subject: [PATCH 6/7] Update build preset names in automation instructions --- en/docs/quick-start-guides/schedule-your-first-automation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/en/docs/quick-start-guides/schedule-your-first-automation.md b/en/docs/quick-start-guides/schedule-your-first-automation.md index af8aea6a..d90755d7 100644 --- a/en/docs/quick-start-guides/schedule-your-first-automation.md +++ b/en/docs/quick-start-guides/schedule-your-first-automation.md @@ -71,7 +71,7 @@ You can execute your automation directly from the environment card on the **Over !!! info When working on WSO2 MI projects and deploying a WSO2 MI integration as a manual task in Choreo, use the WSO2 MI automation mode. For details, see [Running the Micro Integrator in Automation Mode](https://mi.docs.wso2.com/en/latest/install-and-setup/install/running-the-mi-in-automation-mode/). - === "Ballerina" + === "WSO2 BI" To explore a Ballerina manual task with arguments, try out the [Weather to Email Task](https://github.com/wso2/choreo-samples/tree/main/weather-to-email-integration) sample. For instructions, see the `README.md` file in the sample repository. !!! info From 4f5db5ee215fe754e4c55f1b216a6ea4b3d43eb5 Mon Sep 17 00:00:00 2001 From: senurah Date: Fri, 20 Feb 2026 09:37:29 +0530 Subject: [PATCH 7/7] Update schedule-your-first-automation page --- .../schedule-your-first-automation.md | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/en/docs/quick-start-guides/schedule-your-first-automation.md b/en/docs/quick-start-guides/schedule-your-first-automation.md index e36f9d1a..d17fd945 100644 --- a/en/docs/quick-start-guides/schedule-your-first-automation.md +++ b/en/docs/quick-start-guides/schedule-your-first-automation.md @@ -54,9 +54,12 @@ This redirects you to the **Create New Integration in VS Code** page. 3. Add an appropriate commit message and commit. 4. Click **Sync Changes** to push the changes to remote. -## Optional: Test the Automation manually +## Optional: Test the automation manually -You can execute your automation directly from the environment card on the **Overview** page: +!!! note "Prerequisite" + Ensure the build has completed successfully (Build Status: `Completed`) before testing. You can view the Build History by clicking **Build** in the left navigation. + +You can execute your automation directly from the **Development** card on the **Overview** page: 1. On the Overview page, locate the **Development** card. 2. Click **Test** to run your automation immediately. @@ -74,7 +77,7 @@ You can execute your automation directly from the environment card on the **Over To explore a WSO2 MI-based manual task with arguments, try out the [Weather to Logs Task](https://github.com/wso2/choreo-samples/tree/main/weather-to-logs-mi-manual-task) sample. For instructions, see the `README.md` file in the sample repository. !!! info - When working on WSO2 MI projects and deploying a WSO2 MI integration as a manual task in Choreo, use the WSO2 MI automation mode. For details, see [Running the Micro Integrator in Automation Mode](https://mi.docs.wso2.com/en/latest/install-and-setup/install/running-the-mi-in-automation-mode/). + When working on WSO2 MI projects and deploying a WSO2 MI integration as a manual task in Devant, use the WSO2 MI automation mode. For details, see [Running the Micro Integrator in Automation Mode](https://mi.docs.wso2.com/en/latest/install-and-setup/install/running-the-mi-in-automation-mode/). === "WSO2 BI" To explore a Ballerina manual task with arguments, try out the [Weather to Email Task](https://github.com/wso2/choreo-samples/tree/main/weather-to-email-integration) sample. For instructions, see the `README.md` file in the sample repository. @@ -84,14 +87,14 @@ You can execute your automation directly from the environment card on the **Over !!! note As user portal features are added, testing and other actions will be accessible directly from the **Overview** page, making it easier to manage and validate your automations. -## Step 5: Schedule Automation +## Step 5: Schedule automation 1. Once you push the changes, the overview page of the Devant automation will automatically refresh and show you the **Latest Commit** and automatically build your automation showing the **Build Status**. !!! note - The build process may take some time. Once complete, the build status changes to **Success**. You can see the Build History by clicking **Build** in the left navigation. + The build process may take some time. Once complete, the build status changes to **Completed**. You can see the Build History by clicking **Build** in the left navigation. -2. Once the **Build Status** shows `Build completed`, click **Test** to run your automation once. +2. Once the **Build Status** shows `Completed`, you can test your automation. See the [Optional: Test the automation manually](#optional-test-the-automation-manually) section for detailed instructions on testing, including testing with runtime arguments. 3. The development card automatically updates with execution details. Click the refresh button in the top right corner if it is not automatically updated. 4. Click **View Logs** on an execution. You will see the `Hello World` log printed along with the execution time. 5. Click **Schedule** to schedule the automation. @@ -107,7 +110,7 @@ You can execute your automation directly from the environment card on the **Over 10. After successfully testing, you can promote your automation to production by clicking the **Promote** button. 11. Once promoted to production, click **Run** to run your automation immediately. - !!!info + !!! info If you want to pass runtime arguments when running in production, use the **Run with Arguments** option in the same way as described above in the [Test the Automation manually](#optional-test-the-automation-manually) section. 12. In critical environments (Production), you will be able to see automation metrics such as: