Content Publishing --> Content Library - Rich Text strips out certain HTML/CSS/Javascript elements after saving - Known Error

Content Publishing --> Content Library - Rich Text strips out certain HTML/CSS/Javascript elements after saving Description Rich text is using a "Translated HTML" field to save the content. This case is configured to be sanitized using the HTMLSanitizerConfig, to avoid potential security threads. When the generated HTML/CSS/Javascript contains elements that are not allowed based on this HTMLSanitizerConfig then the Platform strips them out and save the remaining data.

Very specific tags like for example ( ) disappear when saving

Steps to Reproduce

Go to Content Publishing -> Content Library, click on New and select Rich Text (under Portal section) Fill the mandatory fields In the Rich text field and click to see the source code (<> icon) Add the below content to the source code hello

6. Save and Continue 7. Reopen html editor code

You will see the disappears

NOTE: This is just and example with "map". There are other HTML elements, CSS elements and Javascript that might not be allowed based on the HTMLSanitizerConfig configuration, where you may see the same behavior

Workaround As these fields are getting sanitized using HTMLSanitizerConfig, which has a configuration to determine which HTML elements are allowed and which are not (defined by Security) there are a couple of options that can be looked at to workaround this issue:

Recommended option is to modify the HTMLSanitizerConfig to allow the elements that are getting stripped out (if they are considered safe). Here is the doc ( https://docs.servicenow.com/en-US/bundle/utah-platform-security/page/administer/security/task/t_ConfigureHTMLSanitizer.html ). As this is an edit to a Script Include you may miss updates to it in the future. We recommend to mark the script as upgradable after modifying it (when any upgrade to the file comes it will overwrite these changes and might need to be redone) Disable sanitization for the field so none of the elements saved to that field will be ever sanitized. You can refer to this doc In both the cases we recommend to verify with your security team before applying any of the workarounds, as this configuration was put in place to prevent security threats.