Incorrect URL Encoding in Rovo's ServiceNow Connector Search Results

XMLWordPrintable

    • 1
    • Minor

      Issue Summary

      When using the Rovo integration with ServiceNow, the URLs generated for incident records in the search results are malformed, containing multiple '?' characters. This results in a 'Result not found' error when attempting to access the records via the click-through links. 

      Steps to Reproduce

      1. Integrate Rovo and ServiceNow through the connector
      2. Perform a search that's related to Data in ServiceNow
      3. Wait for the AI-generated answer to get populated, and click on the Source tab next to the AI answer
      4. Click on the link to the ServiceNow incident in the Source tab.

      Expected Results

      The link to the ServiceNow incident opens the correct incident.

      Actual Results

      The link to the ServiceNow incident opens a "Result not found" error, which is caused by the incorrect encoding

      Workaround

      Right-click on the Incident link to copy it. Pasting it in the browser will open the correct incident link. 

            Assignee:
            Cameron Ownbey
            Reporter:
            Naveen
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: