Issue with making "glide.ui.escape_text " property false

pkumbhar
Tera Contributor

Hi,

We have some html tags inside Help Text for Service catalog, to avoid this problem we got workaround to update "glide.ui.escape_text" properties to false.

But once we update this property to false and if we try to open any record from servicenow we get below error and page doesn't get open.

Element type "myGroups.length" must be followed by either attribute specifications, ">" or "/>".

Please let me know if anybody has any idea on this issue.

Thanks,

Pradip Kumbhar

1 ACCEPTED SOLUTION

Shahed Shah1
Tera Guru

Hi Pradip



This is an expected behaviour as the Variable help text was never intended to contain HTML. See: Styling your Service Catalog form in Geneva and ServiceNow KB: PRB663858: More information tag on Service Catalog Variables turns HTML into escaped ... .



Additionally, setting the glide.ui.escape_text property to false should not be considered a workaround, as this impacts the security of the Instance as mentioned in the Product Documentation: High Security Settings properties.



But for some good news, the Istanbul release introduces proper support for having HTML in the Help text. Here's the release notes regarding that: Service Catalog release notes



Regards


Shahid


View solution in original post

3 REPLIES 3

Vignesh11
Tera Expert

Hi Pradip,



Usually we will false this system property to make use of next line <br> tag in service catalog more information, but there wont be any impact as far i have seen,


try to check enable debug all and see which one is making this error.


if this doesn't work check any schedule job, event log is running.


Shahed Shah1
Tera Guru

Hi Pradip



This is an expected behaviour as the Variable help text was never intended to contain HTML. See: Styling your Service Catalog form in Geneva and ServiceNow KB: PRB663858: More information tag on Service Catalog Variables turns HTML into escaped ... .



Additionally, setting the glide.ui.escape_text property to false should not be considered a workaround, as this impacts the security of the Instance as mentioned in the Product Documentation: High Security Settings properties.



But for some good news, the Istanbul release introduces proper support for having HTML in the Help text. Here's the release notes regarding that: Service Catalog release notes



Regards


Shahid


Pradip, please let us know if this answered your question we want to make sure you have your question answered. Thanks