The usage of the 'conversation label' in the build of a catalog item.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago
Quite often, the areas that need a catalog item built for them need language inserted into the build and also quite often, there is a LOT of, what they consider, absolutely necessary information. This can make the section large and include a few links. How we handle this is to create a display label using Rich text. In order to succinctly detail what is in the Rich Text Display Label, I have been using the Conversation Label field in order to do that. It greatly helps when looking at a build that might use several Rich Text Display Label fields throughout, to quickly scan the variables to identify the one you need to add to or make a correction to. Someone said this could potentially mess with the Virtual Agent bot down the road when this feature has been fully integrated into our experience. We are in the midst of a migration from Helix to ServiceNow so this Virtual Agent has not been completely set up.
Would someone tell me if what we are using the Conversation Label to do for us currently, is going to be an issue down the road with the Virtual Agent? I'll attach an example.
