--- sourceDocument: Brazil Build or modify applications sourceDocumentLink: https://www.servicenow.com/docs/r/application-development Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Build or modify applications ft:clusterId : - cadev bundleId : - cadev workflow : - Development, Data, and Analytics --- # Test and activate # Test and activate a desktop action in AI Desktop Actions {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Test the desktop action and then activate it so that it's available as a tool in the AI Agent Studio. You can add this tool to the AI agents that execute desktop actions in your desktop environment. ## Before you begin * Capture your automation steps. For more information, see [Automate repetitive tasks by recording steps with AI in AI Desktop Actions](https://www.servicenow.com/docs/1tmtj16vM~L0BJC4vjGuuA "Create desktop actions by recording steps with AI to automate repetitive tasks in AI Desktop Actions. AI validates anchor positions and generates screen contexts automatically after recording, reducing the risk of automation failures at runtime."), [Automate repetitive tasks by auto-capturing steps in AI Desktop Actions](https://www.servicenow.com/docs/WtTq1gWDHHfpG2wHOQG4Cw "Create desktop actions by auto-capturing steps to automate repetitive tasks in AI Desktop Actions. You can save the steps that you perform on the application elements as a reusable desktop action of type on-screen task."), or [Extend a desktop action by manually capturing steps in AI Desktop Actions](https://www.servicenow.com/docs/I9fWp9dSATSwl7yS7jB2~Q "Extend the automation logic in a desktop action by manually capturing steps in AI Desktop Actions."). * Configure the properties for screens, anchors, and steps. For more information, see [Screen, anchor, and step properties in AI Desktop Actions](https://www.servicenow.com/docs/dSXSRZZenXx3T6SkN4PdEQ "Learn about the properties of screens, anchors, and steps. There are multiple types of steps and each step type has distinct properties. You can update the properties to modify the behavior of the steps."). * Add desktop action details, such as name, description, and associated applications, and review inputs and outputs. For more information, see [Add details to desktop actions in AI Desktop Actions](https://www.servicenow.com/docs/abGyi9FA~H5tPDnbFqL23Q "Add desktop action details, such as name, description, and associated applications, and review inputs and outputs."). {#test-activate-desktop-action-ad__ul_urn_w5j_y2c} Role required: sn_aia.admin ## About this task You can test the desktop action before you activate it. You can also test individual screens to quickly identify and troubleshoot issues. Execution workspace is launched to run and test the selected screen or the desktop action. After you run the test by entering the required inputs manually, test results are shown either for a screen or for entire desktop action in the Execution workspace. While running tests, if you do not see the Execution workspace coming forth, switch to the Execution workspace manually. While working on a desktop action, the test values you enter are retained across test runs until you close the desktop action or reset the test values. ## Procedure 1. From the desktop action header, select Test. 2. Option 1: Run the screen-level test. 1. In the Test modal, enter required inputs for the screen that you want to test. 2. Select Test screen. The Execution workspace is launched. 3. Enter the Windows Security credentials. Observe the test run in the Execution workspace. Note: If any pop up is blocking the automation from running, step in to clear the pop up so that you can see the test run in the Execution workspace. 4. After the test run is complete, check the status in the Test modal. * If test is successful, proceed with testing the next screen. * If test isn't successful, fix the issue highlighted in the error message and run the screen-level test again. {#test-activate-desktop-action-ad__ul_s4m_xcs_33c} 5. **Optional:** Reset test data by selecting Reset. 6. **Optional:** Cancel running test by selecting Cancel. {#test-activate-desktop-action-ad__substeps_eds_b5m_g3c} 3. Option 2: Run the Desktop action-level test. 1. In the Test modal, enter the required input values in the desktop action. * Show inputs - Shows all the required input fields. * Show all - Shows all fields. {#test-activate-desktop-action-ad__ul_r1t_4md_w3c} 2. Select Run test. The Execution workspace is launched. 3. Enter the Windows Security credentials. Observe the test run in the Execution workspace. Note: If any pop up is blocking the automation from running, step in to clear the pop up so that you can see the test run in the Execution workspace. 4. After the test run is complete, check the status in the Test modal. * If test is successful, proceed with activating the desktop action. * If test isn't successful, select Back to Test to check the configuration and run the test again. {#test-activate-desktop-action-ad__ul_xx5_2ds_33c} {#test-activate-desktop-action-ad__substeps_dt5_25m_g3c} 4. **Optional:** Cancel running test by selecting Cancel. 5. After a successful completion of the desktop action test and when you're satisfied with the result, select Activate to publish the desktop action in AI Agent Studio. Important: If you recorded the desktop action using [Record with AI](https://www.servicenow.com/docs/1tmtj16vM~L0BJC4vjGuuA "Create desktop actions by recording steps with AI to automate repetitive tasks in AI Desktop Actions. AI validates anchor positions and generates screen contexts automatically after recording, reducing the risk of automation failures at runtime."), an alert appears if any screens have failed anchors. Resolve the issues before activating to verify reliable automation at runtime. The Activate button sets the desktop action as active or inactive. Only the activated on-screen desktop actions can be selected from the drop-down in AI Agent Studio. Note: After activation, save the desktop action to make it available as a tool in AI Agent Studio. If you get en error that the file size is beyond 10 MB, you can increase the file size in a payload by creating system properties in the ServiceNow instance. For more information, see [Increase payload limit through system properties](https://www.servicenow.com/docs/_tZ9KBH~OaQRlhmj_sFK8w "By default, maximum 10 MB of file size is allowed in a scripted REST API request payload. Increase the payload limit to 15 MB by creating system properties in the global scope."). ## What to do next Create an AI agent. For more information, see [Creating AI agents and adding desktop action tool](https://www.servicenow.com/docs/mS_IKgZyuEhIjmjAEQznaw "Create an AI agent and add desktop action tool in AI Agent Studio to mimic human-like intelligence while executing desktop actions for repetitive tasks in web and desktop environment."). Enable AI agents to perform desktop actions by adding desktop actions as tools. For more information, see .