Skip to main content

Troubleshoot your integrations (MT4)

This article explains common troubleshooting steps to take when creating a generic integration.

Step 1: Confirm local HTML behavior

Each of the GeniusLink integration samples has a plain HTML file, configured to use as the endpoint. Change the settings to your MindTouch site and confirm the widget behavior when stored as a regular HTML file running from your local computer.

If there are problems accessing the API from local HTML files, contact MindTouch Support.

Step 2: Confirm AJAX requests inside the CRM/CEM

After adding the HTML to the CRM/CEM, confirm AJAX requests are firing correctly. In Chrome, open Developer Tools and switch to the Network tab. Then attempt to use the widget, such as issuing a search:

In this case, we see the request to the query API, with a 200 OK returned. Ensure there are no issues here, such as a certificate that needs to be accepted. (Some trial sites may not have certificates setup, and are using self-signed certs that must be accepted.)

Otherwise, AJAX issues from requests originating within an external CRM/CEM must be resolved by their support team.

Step 3: Confirm Javascript behavior inside the CRM/CEM

The CRMs/CEMs may have its own Javascript definitions which interfere with the behavior of the widget. To troubleshoot:

  • Check the Javascript error console for errors, like conflicting versions of jQuery. (The MindTouch code samples load jQuery into a j$ variable to avoid conflicts, but you may need to find/replace this with another variable to ensure compatibility.) 
  • If the CRM/CEM requires AJAX requests to use their proxy, you may need to change the existing API calls that use j$.ajax() to use the new function instead.

Otherwise, Javascript errors within an external CRM/CEM must be resolved by their support team.

  • Was this article helpful?