AI search - Configure to search task table

[M_iA]

Hi, I would like to configure the AI search on our portal to enable users to search for their tickets.

However, when going to create the indexed source, task or any child table are not available in the source choice list.

Has anyone managed to configure this? And if so, what am i missing?

[Mike_R · Accepted solution]

I believe this wasn't always possible but is possible now (as of San Diego or Tokyo). This video is pretty helpful.

https://www.youtube.com/watch?v=lJQxTY5pM30

[M_iA]

Hi @Mike_R 

Many thanks for this - We are still on Rome for a few more weeks which is why. Thanks for this, much appreciated

[Mary Beth Hutch]

I have followed the guidance in the referenced video, but the tasks I am searching for are not able to be produced in the search results. When I debug AI Search, the ticket is found in the results! So I have an "it does not show up in the search results list" problem. 

- My indexed source is "task" and the child tables I configured are "incident" and "sc_req_item"

- I have confirmed the source is indexed properly, and that the source filter conditions return the tickets I am testing with

- When I index with the mapping of "map_to_raw" on the field "number" with the value "number", I get a warning in the AIS Logs that "The provided field name "number' is  unknown

- A difference that I do have is that the rest of my AI Search implementation is based on NLU and not on a script; does this matter?

[Mary Beth Hutch]

Figured out that my issue was with the EVAM! Lesson learned - if the debugger is returning the result, and the UI is not, you have an EVAM problem!