--- title: "How to: Use the Server Side Execution Testing Page" slug: "how-to-use-the-server-side-execution-testing-page" updated: 2025-09-26T11:01:41Z published: 2025-09-26T11:01:41Z canonical: "docs.unqork.io/how-to-use-the-server-side-execution-testing-page" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.unqork.io/llms.txt > Use this file to discover all available pages before exploring further. # How to: Use the Server Side Execution Testing Page UDesignerClassic Designer ## Overview The **Server Side Execution Testing** page simulates a submission’s remote execution. This page gives you the freedom to test data without impacting the [module](/v1/docs/what-is-a-module) or submission. You can also choose to overwrite existing data with new data. This testing page is a great way to test your module while you build. It also lets you mimic a remote execute without configuring a [Plug-In](/v1/docs/plug-in-component) component. The Debugger tool is a part of the Server Side Execution Testing page. It shows every step of your module’s remote execution. Change a value and the Debugger shows you how that change affects the rest of the [application](/v1/docs/introduction-to-unqork-applications). > [!NOTE] > We use the terms server-side execute and remote execute the same way. They both mean that Unqork executes the module on the back-end and on the server. > [!WARNING] > This tool is only available in non-production environments. ### How the Configuration Works For this how-to guide, your end-user navigates to a front-end module in Express View. Your end-user inputs insurance information into the module using Radio Buttons and Text Field components. When saved, the module's Plug-In component fires, calling the back-end module: 1. The front-end module's **radioToSend** **R****adio Buttons** component response populates the **destinationFieldForRadio** **H****idden** component in the back-end module. 2. The back-end module's **ruleDecideCalc** **D****ecisions** component fires the appropriate calculation based on the **radioToSend** **R****adio Buttons** response. 3. The **calcHouse**, **calcCar**, and **calcBoat** **![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/calculator_teal_component(6).png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A55Z&se=2026-11-07T18%3A57%3A55Z&sr=c&sp=r&sig=S9XKZiLm2dL29lNV%2BW%2BlqYY%2B%2BizCzrBXNoiJ6eRmbIM%3D) Calculator** components' result populates the **insuranceRate** **H****idden** component. 4. The front-end module’s **pluginRemoteExecutePart1** ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Screenshot 2025-09-11 151123.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A55Z&se=2026-11-07T18%3A57%3A55Z&sr=c&sp=r&sig=S9XKZiLm2dL29lNV%2BW%2BlqYY%2B%2BizCzrBXNoiJ6eRmbIM%3D) **Plug-In** retrieves the **insuranceRate** data from the back-end module. 5. The data populates the **destinationForRateReturnedFromPart1** **T****ext Field** component in the front-end module. Your end-user then receives their insurance rate. Because you’re mimicking a remote execute, use the Debugger tool on the back-end module. The Debugger lets you see how the module behaves as you input data. When testing API calls, you can also use the Service Logs tool to test and log each response. To complete this how-to guide, you need: - [**EnablementLab_RemoteExecute1_BackEnd**](https://training.unqork.io/#/form/5d9e06f2b5871a004223b54e/edit): This module represents the back-end functions. It also has the Module ID used by the Plug-In’s remote execute. - [**EnablementLab_RemoteExecute1_FrontEnd**](https://training.unqork.io/#/form/5d9e0743b5871a004223b550/edit): This module represents the front-end functions. This is where the user selects the inputs for insurance cost calculations. > Copy and paste the module definitions of each lab into your UDesigner modules. To learn how to copy/paste module definitions, visit our [How to: Copy and Paste Module Definitions](/v1/docs/how-to-copy-and-paste-module-definitions) article. ### Accessing the Server Side Execution Testing Page To run the Debugger tool, open the Server Side Execution Testing page. To open the Server Side Execution Testing page: 1. Click the link to open the **EnablementLab_RemoteExecute1_BackEnd** module in the Module Builder: [https://training.unqork.io/#/form/5d9e06f2b5871a004223b54e/edit](https://training.unqork.io/#/form/5d9e06f2b5871a004223b54e/edit). 2. At the top right of the page, click the Server Side Execution button. > [!NOTE] > You might need to enter your credentials to access the Server Side Testing Tools. When you arrive on the page, you see the Request section and the Response and Debugger tabs. In the Request section of the page, enter the information to run your PUT API request. Running the Put request will upload the data from an existing module. ### Server Side Execution Testing When you open the Testing page, your module’s ID populates in the Module ID field. You can then customize the settings as you see fit. 1. Enter the **Submission ID** for the submission where you want to run test data. Or, leave this field blank to create a new submission. 2. Under **Data**, select if you want to ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/radioComponent_teal_icon(22).png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A55Z&se=2026-11-07T18%3A57%3A55Z&sr=c&sp=r&sig=S9XKZiLm2dL29lNV%2BW%2BlqYY%2B%2BizCzrBXNoiJ6eRmbIM%3D) **Enter as Key-Value** or ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/radioComponent_teal_icon(22).png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A55Z&se=2026-11-07T18%3A57%3A55Z&sr=c&sp=r&sig=S9XKZiLm2dL29lNV%2BW%2BlqYY%2B%2BizCzrBXNoiJ6eRmbIM%3D)**Enter as JSON**. Then, enter the data that you want to test. > [!NOTE] > Click `Add Row` if you need to add more data when selecting **Enter as Key-Value**. Or, click `Delete` to remove data. 3. Under **Flags**, select your desired options. 4. Under **Metadata**, select if you want to ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/radioComponent_teal_icon(22).png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A55Z&se=2026-11-07T18%3A57%3A55Z&sr=c&sp=r&sig=S9XKZiLm2dL29lNV%2BW%2BlqYY%2B%2BizCzrBXNoiJ6eRmbIM%3D) **Enter as Key-Value** or ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/radioComponent_teal_icon(22).png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A55Z&se=2026-11-07T18%3A57%3A55Z&sr=c&sp=r&sig=S9XKZiLm2dL29lNV%2BW%2BlqYY%2B%2BizCzrBXNoiJ6eRmbIM%3D)**Enter as JSON**. Then, enter the metadata that you want to test. > [!NOTE] > Click `Add Row` if you need to add more data when selecting **Enter as Key-Value**. Or, click `Delete` to remove metadata. 5. Click **Execute**. The module executes with new data based on your chosen preferences. Here's a closer look at each setting on the Server Side Execution Testing page: 1. Enter the following test data in the **Data Key** and **Data Value** fields: 2. Click **Execute**. 3. Click the **Debugger** tab. ### Service Logs Testing If you're testing an API server side execute, you can run your tests on the Module Builder using the Service Logs pane. You can also open the Server Side Testing page from here by clicking the **Open SEE Debugger** button. To open the Service Logs pane: 1. Open your module in the Module Builder. 2. Click the `···` (**ellipsis**) button. 3. Select **Service Logs**.The Service Logs pane appears to the right of the Module Builder. The Server Side Execute tool the Service Logs panel operates the same way as the Response tab in the Server Side Execution testing page. Click **Run Now** to initiate the test and view the result. [![Static image showing the Service Logs testing panel after successfully running a test.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/UD_ServerSide_Testing_05_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A55Z&se=2026-11-07T18%3A57%3A55Z&sr=c&sp=r&sig=S9XKZiLm2dL29lNV%2BW%2BlqYY%2B%2BizCzrBXNoiJ6eRmbIM%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/UD%20ServerSide%20Testing%2005.jpeg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A55Z&se=2026-11-07T18%3A57%3A55Z&sr=c&sp=r&sig=S9XKZiLm2dL29lNV%2BW%2BlqYY%2B%2BizCzrBXNoiJ6eRmbIM%3D) > [!TIP] > Service logs also allow you to store and render your tests in a dashboard. For more information on Service Logs, visit our [Service Logs Dashboard Tool](/v1/docs/service-logs-dashboard-tool) article. ## Overview The **Server Side Execution Testing** page simulates a submission’s remote execution. This page gives you the freedom to test data without impacting the [module](/v1/docs/what-is-a-module) or submission. You can also choose to overwrite existing data with new data. This testing page is a great way to test your module while you build. It also lets you mimic a remote execute without configuring a [Plug-In](/v1/docs/plug-in-component) component. The Debugger tool is a part of the Server Side Execution Testing page. It shows every step of your module’s remote execution. Change a value and the Debugger shows you how that change affects the rest of the [application](/v1/docs/introduction-to-unqork-applications). > [!NOTE] > We use the terms server-side execute and remote execute the same way. They both mean that Unqork executes the module on the back-end and on the server. > [!WARNING] > This tool is only available in non-production environments. ### How the Configuration Works For this how-to guide, your end-user navigates to a front-end module in Express View. Your end-user inputs insurance information into the module using [Radio Buttons](/v1/docs/radio-buttons-component) and [Text Field](/v1/docs/text-field-component) components. When saved, the module's Plug-In component fires, calling the back-end module: 1. The front-end module's **radioToSend** **R****adio Buttons** component response populates the **destinationFieldForRadio** **H****idden** component in the back-end module. 2. The back-end module's **ruleDecideCalc** **D****ecisions** component fires the appropriate calculation based on the **radioToSend** **R****adio Buttons** response. 3. The **calcHouse**, **calcCar**, and **calcBoat** **![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/calculator_teal_component(6).png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A55Z&se=2026-11-07T18%3A57%3A55Z&sr=c&sp=r&sig=S9XKZiLm2dL29lNV%2BW%2BlqYY%2B%2BizCzrBXNoiJ6eRmbIM%3D) Calculator** components' result populates the **insuranceRate** **H****idden** component. 4. The front-end module’s **pluginRemoteExecutePart1** Plug-In retrieves the **insuranceRate** data from the back-end module. 5. The data populates the **destinationForRateReturnedFromPart1** **T****ext Field** component in the front-end module. Your end-user then receives their insurance rate. Because you’re mimicking a remote execute, use the Debugger tool on the back-end module. The Debugger lets you see how the module behaves as you input data. To complete this how-to guide, you need: - [**EnablementLab_RemoteExecute1_BackEnd**](https://training.unqork.io/#/form/5d9e06f2b5871a004223b54e/edit): This module represents the back-end functions. It also has the Module ID used by the Plug-In’s remote execute. - [**EnablementLab_RemoteExecute1_FrontEnd**](https://training.unqork.io/#/form/5d9e0743b5871a004223b550/edit): This module represents the front-end functions. This is where the user selects the inputs for insurance cost calculations. ### Accessing the Server Side Execution Testing Page To run the Debugger tool, open the Server Side Execution Testing page. To open the Server Side Execution Testing page: 1. Click the link to open the **EnablementLab_RemoteExecute1_BackEnd** module in the Module Builder: [https://training.unqork.io/#/form/5d9e06f2b5871a004223b54e/edit](https://training.unqork.io/#/form/5d9e06f2b5871a004223b54e/edit). 2. At the top right of the page, click the Server Side Execution button. > [!NOTE] > You might need to enter your credentials to access the Server Side Testing Tools. When you arrive on the page, you see three sections: Request, Response, and Debugger. In the Request section of the page, you see PUT and GET Request Methods. A PUT API request updates data and a GET API request retrieves data. Because the Server Side Execution Testing settings change depending on the Request Method, let's look at those settings separately. ### PUT Server Side Execution Testing 1. Enter the **Submission ID** for the submission where you want to run test data. Or, leave this field blank to create a new submission. 2. Under **Flags**, select your desired options. 3. Under **Data**, select if you want to **Enter as Key-Value** or **Enter as JSON**. Then, enter the data that you want to test. > [!NOTE] > Click Add Data Value if you need to add more data when selecting Enter as Key-Value. Or, click Delete to remove data. 4. Under **Metadata**, select if you want to **Enter as Key-Value** or **Enter as JSON**. Then, enter the metadata that you want to test. > [!NOTE] > Click Add Metadata Value if you need to add more data when selecting Enter as Key-Value. Or, click Delete to remove metadata. 5. Click Execute. The module executes with new data based on your chosen preferences. ### GET Server Side Execution Testing 1. Enter the **Submission ID** for the submission where you want to run test data. Or, leave this field blank to create a new submission. 2. Under **Flags**, select your desired options. 3. Under **Data**, enter the data that you want to test. > [!NOTE] > Click Add Data Value if you need to add more data. Or, click Delete if you want to remove data. 4. Click Execute. The module executes with new data based on your chosen preferences. After clicking **Execute**, you see a Response tab ## Resources - [Service Logs Dashboard Tool](/v1/docs/service-logs-dashboard-tool) - [Understanding Service Logs](/v1/docs/understanding-service-logs) - [Common Troubleshooting Strategies](/v1/docs/common-troubleshooting-strategies) - [Is there a way to test arrays using the Data Key field?](https://community.unqork.com/platform-q-a-10/server-side-execution-testing-2204) Also known as Record Data. Submission data consists of information saved by Unqork components. View submission data by using the angular command, or in Record Collections. End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product. Express View is how your end-user views your application. Express View also lets you preview your applications to test your configuration and view the styling. This is also the view your end-users will see when interacting with your application. After configuring a module, click Preview in the Module Builder to interact with the module in Express View. APIs (application programming interfaces) are a set of protocols and definitions developers use to build and integrate application software. APIs act as the connective tissue between products and services.