- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2024 07:46 AM
I'm looking at turning on AI Search for my instance, so I have been playing around with it in a sub-PROD environment. So far, it seems to be working well!
I know that people will expect Interactions to be searchable, so I added them to the index. I also figured out how to add facets so these can be filtered. So far, these work great. However, I can't seem to adjust how the search results appear.
See here:
I would like to populate more data in these, such as who the Interaction was opened for, date and time, etc. Currently I just have the Short Description showing. I'd also like to get rid of the "Generic" text and replace it with something, you know, useful.
Thanks for your help!
Solved! Go to Solution.
- Labels:
-
AI Search

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-23-2024 07:25 AM
Hello, you can adjust this via the EVAM View Config Table [sys_ux_composite_data_template_predicate]. There you have the View Template Reference Field where you select a specific UX Template. These Templates are stored in the [sys_ux_composite_data_template] table.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-23-2024 11:21 AM
Thanks! I will give it a try!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-04-2024 11:40 AM
Thanks! This got me to it. Had to do some tinkering but got it working!
@rojachiliveru1and @LearnerNitin --this is the answer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-01-2025 09:45 AM
@Joe1 hi, can you please tell me how you achieved the effect of adding interactions to the search results?
Technically speaking I also managed to achieve this :
but I am very not-sure I did it correctly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2025 06:35 AM
Yep! You are on the right track!
This is the template I set up for us. Note that we have a custom "subtype" field that we use:
{
"component": "sn-search-result-evam-card",
"staticValues": {
"imageType": {
"translatable": false,
"key": "icon"
},
"icon": {
"translatable": false,
"key": "chat-outline"
},
"textHeaderLabelOne": {
"translatable": true,
"key": "Interaction"
},
"detailLabelOne": {
"translatable": true,
"key": "Type:"
},
"detailLabelTwo": {
"translatable": true,
"key": "Subtype:"
},
"detailLabelThree": {
"translatable": true,
"key": "Opened for"
},
"detailLabelFour": {
"translatable": true,
"key": "Opened by"
},
"detailLabelFive": {
"translatable": false,
"key": "Created"
},
"requireLabelAndValue": {
"translatable": false,
"key": "true"
},
"detailPosition": {
"translatable": false,
"key": "above"
},
"detailLabelSeparator": {
"translatable": false,
"key": "|"
}
},
"mappings": {
"titleLabel": "ai_search_teaser_title",
"title": "short_description",
"textHeaderLabelTwo": "number",
"detailValueOne": "type",
"detailValueTwo": "subtype",
"detailValueThree": "opened_for",
"detailValueFour": "opened_by",
"detailValueFive": "opened_at"
},
"actionMappings": {
"clickAction": "navigation"
}
}