- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi everyone,
I have an query. I've been trying to figure out from 2 days but couldn't able to(may be because I'm new to SNOW). In the attached screen for the search results which are tagged as Knowledge doesn't have Category while there's category for all others.
How to find this screen:
- Go to CSM/FSM Configurable Workspace > Interactions > My Interaction.
- Open any interaction.
- Search anything in the Recommendation Panel present on the right side of the screen.
I have already checked the category is present for the shown result in kb_knowledge table.
Kindly help.
Solved! Go to Solution.
- Labels:
-
CSM Configurable Workspace
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
It worked finally, but not via making changes in All > Recommended Actions > Action Types > Guidances. It turns out that when Recommended Actions are rendered through that specific UI component (Share KB in chat Interaction), the field display isn't governed by the standard guidance configurations at all. Instead, it relies directly on the UI Builder setup:
Get Preview Fields (Data Resource): Adding kb_category to the fields retrieved by the data resource.
Set Preview Fields (Client Script): Updating the script to parse kb_category and push it into the fieldsToDisplay state array so the card actually renders it.
Anyway thanks for taking your time and look into the issue. @Gangadhar Ravi @Sandhya Gurram
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 2 weeks ago
Hello @NavneetP
As discussed, sharing below the page and Scripts responsible for displaying Knowledge Articles Recommendation on your UI Page.
Page name: Share KB in chat interactions
Data Resource: Get Preview Fields (you need to add 'Category'/field(s) you wish to display on the searched Knowledge card of 'Recommendation' tab here).
Client Script: Set preview fields (you need to add piece of code under 'fieldsToDisplay' section to fetch the 'Category'/added field value here & add it to the returned payload).
We have tried together the solution and it worked for you.
Request you to please mark my solution helpful/correct/accepted so it can help others looking for similar guidance. Thanks!
Best regards
Madhuri Bhawnani
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
@NavneetP You need to go to sn_nb_action_recommended_action and find the exact recommendation that you want to modify and then find ga_guidance record for that where you can add or remove fields. you can check if that configuration have category if not you can add it for knowledge.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @NavneetP ,
The Category is missing because of how the card is set up, not because of your data. Each search card in the Recommended Actions panel is drawn by a guidance. The fields on that card come from the guidance’s “Fields To Display” setting, not from the kb_knowledge record. Your Knowledge source is most likely mapped to a knowledge-specific guidance (for example “Share KB in chat” or “Attach and share article”) that doesn’t include Category. Your other sources use different guidances, which is why they show it.
To fix it:
- Find which guidance your Knowledge results use. Go to All > Recommended Actions > Contexts and open the context for your interaction page. Check the Search Application Configuration field (the base config is “[CSM AIS] Configurable Workspace Search Config”). Then open the Search result mapping related list and find the row for the Knowledge search source table. Note the Action (guidance) on it.
- Open that guidance. Go to All > Recommended Actions > Action Types > Guidances and open the one from step 1.
- Add Category to the card. On the Preview Experience tab, click the lock icon on Fields To Display and move Category (kb_category) into Selected. You can pick up to four fields, so you may need to drop one. Lock the field again and save. You need the sn_nb_action.next_best_action_author or admin role.
- If Category isn’t in the list, the guidance has no input pointing at the article record. Go back to the search result mapping from step 1 and map the result’s sys_id or record to the guidance input. Then try step 3 again.
- Test it. Hard refresh the workspace, open an interaction and search again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I've tried both the suggestion but none of them work.
Hello @Sandhya Gurram
I have tried to follow the steps but unfortunately I'm still not seeing the category. Below are the screenshots.
See screenshots Recommended ActionsContexts 1, Recommended ActionsContexts 2, Recommended ActionsContexts 3 for Recommended Actions > Contexts screens. I have used CSM Interaction Context because other one is for ITSM.
See screen shot Recommended ActionsGuidances 1 for the changes made for Recommended Actions > Action Types > Guidances.
Please let me know if I'm missing something.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
It worked finally, but not via making changes in All > Recommended Actions > Action Types > Guidances. It turns out that when Recommended Actions are rendered through that specific UI component (Share KB in chat Interaction), the field display isn't governed by the standard guidance configurations at all. Instead, it relies directly on the UI Builder setup:
Get Preview Fields (Data Resource): Adding kb_category to the fields retrieved by the data resource.
Set Preview Fields (Client Script): Updating the script to parse kb_category and push it into the fieldsToDisplay state array so the card actually renders it.
Anyway thanks for taking your time and look into the issue. @Gangadhar Ravi @Sandhya Gurram