{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":4539,"path":"conversational-interfaces/advanced-work-assignment/define-extrnl-routng-plugin.md","title":"Define external routing test implementation","bundle":null,"doc_type":null,"release":"australia","body":"\n# Define external routing test implementation\n\nDefine the External Routing Test Tools plugin \\[com.glide.awa.external.test\\_tools\\] with a simplified external-routing-provider sample Automated Test Framework \\(ATF\\) by using the demo data that is available with the plugin installation.\n\nTo run the ExternalRoutingConfigurationTestTool, verify that you have:\n\n-   Loaded the demo data for AWA, awa.external, and awa.external.test\\_tools.\n-   Filled up the credentials in the **AutomationUser** in the sys\\_auth\\_profile\\_basic table.\n-   Created the HTTP\\(s\\) Connection in sys\\_alias, ServiceNow\\_Basic record.\n\nYou must open the ExternalRoutingConfigurationTestTool record and click Run Test to complete the actions of the External Routing test.\n\n## Functions of the External Routing Test Tools plugin \\(com.glide.awa.external.test\\_tools\\)\n\nWhen the External Routing Test Tools plugin \\(com.glide.awa.external.test\\_tools\\) is run, it validates if:\n\n-   The Connection record is created in the HTTP\\(S\\) Connection \\[http\\_connection\\].\n-   The Credentials are provided in the HTTP\\(S\\) Connection \\[http\\_connection\\].\n-   The AWA\\_Queue record is updated successfully with the following values:\n    -   **External** = **true**\n    -   **Provider** = **ServiceNow Demo**\n-   A record is successfully created in the Interaction \\[interaction\\] table with the following values:\n    -   **Short description** = **Created from ATF test automation**\n    -   **State** = **New**\n    -   **Type** = **Chat**\n-   The record is automatically created in the Work Item.\n-   The Server-Side Validation Script is run by passing the Work Item ID to the Workflow Studio and calling to the external third-party CCaaS provider.\n-   The sys\\_flow\\_context ID is retrieved from the sys\\_flow\\_context execution.\n-   The retrieved sys\\_flow\\_context ID provides the payload response.\n-   The payload response belongs to the Work Item that you have created.\n-   The Server-Side Validation Script is run to verify if the response is successful and then the payload is sent to the Manual Assignment REST API.\n-   The authorization for credentials is configured in the Basic Auth Configuration \\[sys\\_auth\\_profile\\_basic\\] table.\n-   An Agent is available in the User \\[sys\\_user\\] table to ascend the payload.\n-   The Server-Side Validation Script is run to confirm that the Agent is available in the correct Service Channel.\n-   The Manual Assignment REST API is called when the Agent is available.\n-   The response status is successful and the response payload contains `Manual Assignment successfully requested`.\n-   The AWA Work Item is successfully assigned to the Agent and is not in the queue state.\n\n    **Note:** If the test fails at any step, the detailed information about where the configuration failed is provided to the user along with the solution to fix it.\n\n\n"}}