- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-24-2024 12:03 PM
Hello,
Hoping someone can help me with this. Whenever creating an assessment, with either the designer or through the normal UI, it is showing the HTML tags in the description fields. This happens even just using the text field html choices such as bold or italics.
I feel like this just started happening as we had multiple assessments formatted with HTML and now the tags are displaying for each of them.
Assuming it's a bug but I want a sanity check.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-03-2024 10:45 AM
HI Support has confirmed the issue and is testing on versions before Washington to determine if it was introduced in a recent update.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-24-2024 12:34 PM
Hi Travis,
HTML returning with tags is most probably due to stringified content. Since the backend configurations of properties in this block are OOB, we cannot decide on what action to take unless your instance is configured in some other area affecting this like creating properties that affect UI for HTML etc.
If my response proves useful, please mark it "Accept as Solution" and "Helpful". This action benefits both the community and me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-27-2024 12:44 PM
We started seeing this after updating to Washington DC as well. Note Survey Management PRB1700918 was supposed to fix a "font issue on assessment_take2". Not sure if related.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-27-2024 12:46 PM
Here is an example
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-03-2024 10:45 AM
HI Support has confirmed the issue and is testing on versions before Washington to determine if it was introduced in a recent update.