Require assistance with the external_content ingestDocument api

Ashley
Kilo Sage

Good Afternoon,

I need some guidance with AI Search, I have put together a rest message that returns results from our SharePoint Knowledge base, this is all working fine with it returning the unique document id, title, url etc but I need to get this into AI Search so it is searchable within Virtual Agent.

I have created the external content schema table and search profile etc:
https://docs.servicenow.com/en-US/bundle/sandiego-platform-administration/page/administer/ai-search/task/create-ext-content-schema-ais.html

I have used the external_content/storeContent rest api to create the content pointer which is then used in the external_content/ingestDocument rest api.

Doing all this makes it searchable within Virtual Agent but the schema table I created remains empty and the url its using is pointing to the ServiceNow instance and not too the SharePoint site so ofc it fails to open.

The documentation around the api's is lacking in some areas and wondered if anyone else had any success ingesting external content that is searchable? wondering if I am doing the mapping wrong.

Any help and I would be grateful

Kind Regards

Ashley

1 ACCEPTED SOLUTION

Ashley
Kilo Sage

Good Morning,

So the article that resolved the problem for me in the end was this one:

https://docs.servicenow.com/bundle/sandiego-servicenow-platform/page/administer/conversational-interfaces/task/ac-configure-url-navigation.html

It doesn't get mentioned as part of the document ingest api documentation but for custom tables you need to create a new navigation url link which points to the new external schema table that gets created. Once I had this in place everything was pointing to the external site as needed.

Kind Regards

Ashley

View solution in original post

17 REPLIES 17

ServiceNow Tec2
Mega Sage
This has been resolved by ServiceNow Technical Support. Please refer to KB1007147 for more information.

ServiceNow Tec2
Mega Sage
This has been resolved by ServiceNow Technical Support. Please refer to KB1020747 for more information.

Ashley
Kilo Sage

Good Morning,

So the article that resolved the problem for me in the end was this one:

https://docs.servicenow.com/bundle/sandiego-servicenow-platform/page/administer/conversational-interfaces/task/ac-configure-url-navigation.html

It doesn't get mentioned as part of the document ingest api documentation but for custom tables you need to create a new navigation url link which points to the new external schema table that gets created. Once I had this in place everything was pointing to the external site as needed.

Kind Regards

Ashley

Hi Ashley

We recently enabled AI search in our instance and we have installed all the necessary plugin for external content search. I have created a schema map as mentioned in the documents.
Can you guide me whats the next step? 

I have SP search source where we have data fetch script for external content search (zing engine) , now I would like to have the same for AI search.

Thanks, 
Fedrick

Good Afternoon,

You have a number of options available to you but does depend on licencing that you have:

Best place to start:

https://docs.servicenow.com/en-US/bundle/sandiego-platform-administration/page/administer/ai-search/concept/external-content-ais.html

Options:

1) Search connector applications (Requires Employee Centre Pro licence)

2) Integration Hub AI Search spoke (Needs to be public facing site, i.e. doesn't support authentication session)

3) External Content REST API

We had to go with option 3 which is the hardest one, if you want to go with flow designer then this article will help you:

https://community.servicenow.com/community?id=community_article&sys_id=591e21f7db294d10f77799ead396195d

If you want to go down the Outbound Rest Message Route then article will help you:

https://docs.servicenow.com/bundle/sandiego-application-development/page/integrate/inbound-rest/concept/external-content-ingestion-api.html#ext_content-POST-ingestDocument

You can associate stored binary content with an external document by following these steps:

  1. Store the binary content in AI Search using the POST /ais/external_content/storeContent endpoint. Record the value of the result response body parameter.
  2. When sending the external document to AI Search using this endpoint, set its content_pointer request body parameter to match the recorded result response body parameter value.

Kind Regards

Ashley