Real users warnings after Xanadu upgrade - Support and Troubleshooting

Real users warnings after Xanadu upgrade Issue The following warning is being logged for real users. It started after the upgrade to glide-xanadu-07-02-2024__patch1-hotfix2-10-03-2024_10-03-2024_2059.

com.glide.script.RhinoEcmaError: null is not a function. : Line(1) column(0) ==> 1: null()

Symptoms On any X instance:

1) Add a field of type HTML on the incident table 2) Clear cache (cache.do) 3) Access incident.do from filter navigator 4) Access /syslog_list.do?sysparm_query=sys_created_onONToday%40javascript%3Ags.beginningOfToday()%40javascript%3Ags.endOfToday()%5Elevel%3D1%5EmessageSTARTSWITHcom.glide.script.RhinoEcmaError&sysparm_view=

Expected : No Warnings Actual : We can see below warnings in the log. This the number of logs is equal to the number of HTML fields on the form

Warning com.glide.script.RhinoEcmaError: null is not a function. : Line(1) column(0) ==> 1: null() Evaluator

Release Seen in:

Xanadu Patch 1 Hot Fix 3b Xanadu Patch 1 Hot Fix 2b Xanadu Patch 1 Hot Fix 3 Xanadu Patch 1 Hot Fix 2 Xanadu Patch 1 Hot Fix 2a

Cause com.glide.script.RhinoEcmaError: null is not a function. : Line(1) column(0) ==> 1: null() warnings are shown in sys logs after upgrade to XanaduP1hF2a

Resolution ##Issue : Real users warnings after Xanadu upgrade

##Reason This issue is reported at our end ** PRB1841733**.

##Workaround

Kindly check below workaround. I tested workaround on OOB instance and it works as expected.

This warning will be seen if you are using tinymce v6.

Warning will not be seen if the instance is using v5 of tinymce. This can be achieved by creating glide.ui.html.editor.use_v5 sys property and setting it to true.