JS Error: NullPointerException in SafeURL.put(key,value) {ThreadName}, {undefined}
This was documented last year as being related to CPM v6...
But we see it in v7. Saw it in v7.1.2 last year, and now unexpectedly seeing this in v7.1.5.
This should silently log to console, rather than throw up an alert window. Will likely file an SR here.
Accepted Solution
BNY Mellon
US
Solved.
Checked the IE console, and saw that the strPyLabel had a newline in it, which led to an unterminated string.
Investigating where the newline came from.
It would be prudent to update WorkFormStandard and parse labelValue, not merely checking for the nefarious crossScriptingFilter characters, but also the humble newline.
labelValue=pega_rules_string.replaceAll(StringUtils.crossScriptingFilter(tools.getPrimaryPage().getString("pyLabel")),"\"","");
BNY Mellon
US
Here's the JS in 7.1.5.
Internal Javascript errors should never alert; they should write to console.
Is this fixed in a future ML?
SafeURL.prototype.put= function (key, value){
try {
if (key== undefined || key== null || value== undefined || value== null) {
throw "NullPointerException in SafeURL.put(key,value) {" + key + "}, {" + value + "}";
}else {//if(typeof(value)== 'string' || ( typeof(value)== 'object' && value.name== 'safeURL') ){
this.hashtable[key]= value;
return true;
}/*else {
throw "InvalidArgumentException :: SafeURL only accepts strings and SafeURL objects - {" + key + "}, {" + value + "}";
}*/
}
catch (exception) {
window.alert(exception);
return false;
}
}
Accepted Solution
BNY Mellon
US
Solved.
Checked the IE console, and saw that the strPyLabel had a newline in it, which led to an unterminated string.
Investigating where the newline came from.
It would be prudent to update WorkFormStandard and parse labelValue, not merely checking for the nefarious crossScriptingFilter characters, but also the humble newline.
labelValue=pega_rules_string.replaceAll(StringUtils.crossScriptingFilter(tools.getPrimaryPage().getString("pyLabel")),"\"","");
BNY Mellon
US
Note: Microsoft Exchange actually does "Header Folding" to put newlines in the Subject. We turned on logging and determined that the EmailListener engine code does not appear to be removing the newlines. See here:
So this should be addressed in the engine, or in activity CreateWorkFromEmail, or in fragment WorkFormStandard.
Pegasystems Inc.
US
I can definitely say it should not be handled in Email Listener.
Email Listener should be preserving the original email data as much as possible. It should be up to the consumer (Activities, data transforms) or some layer between the Listener and the consumer to deal with possible incompatibilities between the raw data and Pega.