Get the latest live chat benchmark data broken down by team size & industry

Read more
Comm100 X2 Pre-Upgrade Checklist

To ensure that your upgrade proceeds smoothly, please review this pre-upgrade checklist. If you are using certain features or configurations, action may need to be taken on your side. Should you have questions about anything, please email support@comm100.com or contact your Customer Success Manager.

In case you want to download this article, click Comm100 X2 Pre-Upgrade Checklist.


Checklist

  • Visitor side JavaScript (JS) API - If you are using any visitor side JS API to call int (integer) ID on your website on the current platform, then the visitor side JS API needs to be updated to GUID before the upgrade or immediately after the upgrade. For instance, the data type of agentId needs to be updated from int (Integer) to GUID in the Comm100 X2 platform. 
    To learn more on the visitor side JS APIs, please see Comm100 X2 Upgrade - Visitor side JavaScript API
  • Agent Console Extension - If you are using the agent console extension on the current platform, the agent console extension needs to be re-uploaded immediately after migration. And if the code within the extension has pointed to comm100 domains, then needs to be updated with X2 domains.
    To learn more on how to upload agent console extension, please see, How to create or manage your own apps.
    To learn more on the Comm100 domain, please see Comm100 X2 Upgrade – Firewall Update.
  • RESTful API  - If you are using the RESTful API on the current platform, the API needs to be updated immediately after the upgrade. We suggest you perform testing before the upgrade. Comm100 can create a Sandbox account for testing. To learn more on the upgrade to APIs, please see,  Upgrade to Comm100 Restful API Guide ver. 4.0.
    To learn more on the APIs, please see Comm100 RESTful API Guide.
  • Webhooks  - If you are using a Webhook in a Chatbot intent-answer or any third-party bot then ensure that all request data types are in camelCase. Additionally, for Live Chat Webhook, the data type of agentId needs to be updated from int (Integer) to GUID.
    To learn more on Webhook, please see Comm100 X2 Upgrade – Webhook.
  • Firewall - If you are configuring any Comm100 domain in your firewall on the current platform, the Comm100 domain needs to be updated immediately after the upgrade, as the Comm100 domain will be changed in the Comm100 X2 platform. 
    To learn more on the Comm100 domain, please see Comm100 X2 Upgrade – Firewall Update.
  • Knowledge Base (KB) article URL change - If you have any links to Comm100 KB articles on your website or in your chatbot, the KB article URLs need to be updated immediately after the upgrade, and the old URL of the KB article will be unavailable.
    For example, if the current URL of KB article is: https://portal2.comm100.io/kb/10000/02000000-0000-0000-0000-006f00002710/a/ef000000-0000-0000-0000-006900002710/how-to-install-comm100-live-chat-on-magento-site, after the upgrade, it might be changed to:  https://dash11.comm100.io/kb/100/f9627b0c-6ff8-45c5-bdf5-b627f234d9bf/a/75c67adb-369b-4a98-a36e-2a1a811fcd78/how-to-install-comm100-live-chat-to-magento-site
  • Features and UI Changes: There're some features and UI changes on the X2 platform.
    To learn more about features and UI changes, please see Comm100 X2 Upgrade - Features and UI Changes.
  • Integration - If you are using any of these integrations, it needs to be reconfigured immediately after the upgrade. Integration, such as Zapier, WordPress, Cisco, Magento, Join.Me, or Salesforce on the current platform.
    To learn more on reconfiguring integrations, please see Comm100 X2 Upgrade – Integration Reconfiguration.
  • SSO - If you are using Agent SSO and Visitor SSO, then Agent SSO and Visitor SSO need to be reconfigured immediately after the upgrade.
    To learn more on reconfiguring the Agent and Visitor SSO, please see Comm100 X2 Upgrade - Agent and Visitor SSO Reconfiguration.
  • Ticketing & Messaging 
    • The sorting of Views is recorded in the browser side’s local storage. When you upgrade to the Comm100 X2 platform, the sorting of Views will be lost, and you need to re-order the Views according to your need.
    • Some fields in View will get renamed after the upgrade.
    • Some fields or field options in the Routing Rules will get removed in the Comm100 X2 platform. If you have configured the following fields in your Routing Rules, you need to update the conditions after the upgrade.
    • Some field options in the SLA Policies will get removed in the Comm100 X2 platform. If you have configured the following field options (@Today+1, @Today+7, @Today+15, @Today+30) in your SLA Policies, you need to update the conditions after the upgrade.
    • Some fields or field options in the Triggers will get removed in the Comm100 X2 platform. If you have configured the following fields (First Message of Ticket, @Today+1, @Today+7, @Today+15, @Today+30) in your Triggers, you need to update the conditions with the new fields after the upgrade.
      To learn more about reconfiguring the Ticketing & Messaging changes, please see Comm100 X2 Upgrade – Ticketing & Messaging Changes.
  • Bot - If you are using Comm100 Bot on your current platform, as a precautionary step, we suggest taking backup (export) of all the bots before the upgrade. You can go to Bot > AI Chatbot > Bots page and Export bot.Picture1.png
  • If you're currently using the old version of the Comm100 app on iOS/Android devices, please update the app to the latest version. 

To learn more on the Comm100 X2 Version Upgrade, see our knowledge base  here. If you have any questions, please chat with our support team at  www.comm100.com or contact your Customer Success Manager.