INC-201334 · Issue 690735
ADMinputsource field population updated to handle transactional decisions
Resolved in Pega Version 8.7
The CaptureResponse flow was failing while writing to AdaptiveAnalytics with the error "IllegalArgumentException - argument does not represent JSON object". This occurred while running an outbound campaign where a few decisions were treated as transactional and did not have Model executions. Attempting to set a response for these decisions resulted in a JSON parse exception being thrown due to pxADMInputs not being populated (no models executed). This occurred only when using transactional actions in CDH, and was caused by the system only including predictive models during the make decision flow due to common inputs not being stored. While there was a workaround of overriding the property pzADMInputSource to use modelReferences instead of admInputContainer, this has been resolved by correcting how the pzADMinputsource field is populated. When there is no modelInput, the system will not populate that field so the page is ignored.
SR-123011 · Issue 182646
Added null check for datetime in SOAP
Resolved in Pega Version 7.1.8
Some SOAP services using a Response Parameter with Data Type of DateTime and for services of type RPC/ literal were generating an NPE when the service was executed outside Pega7 using Google Chrome. Running the service directly from the service rule within Pega7 did not encounter this error. Other SOAP requests returned a date of 1970-01-01. This was traced to a check to get the thread which did not handle situations where PRDateFormat.formatXSDDateTime() could be null, and the handling for that case has been added for this browser.
SR-124833 · Issue 187240
Added null check for datetime in SOAP
Resolved in Pega Version 7.1.8
Some SOAP services using a Response Parameter with Data Type of DateTime and for services of type RPC/ literal were generating an NPE when the service was executed outside Pega7 using Google Chrome. Running the service directly from the service rule within Pega7 did not encounter this error. Other SOAP requests returned a date of 1970-01-01. This was traced to a check to get the thread which did not handle situations where PRDateFormat.formatXSDDateTime() could be null, and the handling for that case has been added for this browser.
SR-131612 · Issue 200253
Handling added for accent characters in DataTable editing
Resolved in Pega Version 7.1.8
When a DataTable had a key value with an accented character like "é", clicking on the "Open this item" icon to edit the row displayed a blank page in the editor. This was caused by the escape method of native JavaScript being deprecated, and the system has been updated to use encodeURIComponent method instead.
SR-128332 · Issue 199072
Added detection for WSDL import failure
Resolved in Pega Version 7.1.8
Issues were encountered while importing WSDL in the ML6 environment while SoapUI was successful using the same SOAP service. This error happened when the WSDLParser.parse(Reader) was trying to read a closed java.io.Reader instance and silently generating an exception. Error handling has been added to report the failure and give an informative message.
SR-A22699 · Issue 248560
RuleServiceFile.parseRecordAtTime and RuleServiceFile.parseByRecordType Timer function corrected
Resolved in Pega Version 7.2.2
The Timer function used in the RuleServiceFile.parseRecordAtTime and RuleServiceFile.parseByRecordType functions was not properly halting when it encountered an exception, causing any subsequent invocation to these methods to start the Timer again. This created errors and incorrect results. The parseRecordAtTime and parseByRecordType methods have now been updated to enclose inbound mapping related stopTiming within a finally block for accuracy.
SR-118615 · Issue 172704
Addressed XML handling for "Expand Java Pages"
Resolved in Pega Version 7.1.8
After upgrading, an IOException occurred while updating a work object if "Expand Java Pages" was unchecked in General options -> Tracer Settings. When the checkbox is enabled, the Javaobject wrapper uses its custom read/write methods to serialize the page. When unchecked, default serialization invoked the ParseXMLSAXRulWrapper.java which contained some properties which are not Serializable. In order to ensure proper XML handling, changes were made to XMLStream.java so the code flow is independent of the expand java pages option in tracer and always takes the custom serialization path.
INC-147654 · Issue 642189
Updates to displaying embedded images in cases
Resolved in Pega Version 8.7
Sending an email with an embedded image to the email ID associated with the email listener successfully created the interaction case, but the embedded image was not displayed when the case was opened from the work-basket. A rule-not found exception was seen in the tracer for pyGetImageDisplay, the rule responsible for displaying the images in the ET pane. Investigation showed that when URLObfuscation was turned on, the decryption of the URL was not successful because "&" had been encoded to '& amp;'. This has been resolved by calling the activity pyGetImageForDisplay using URLMapping instead. An additional issue was seen with displaying images in the email interaction pane where the additional empty new lines moved the image outside the intended place. This was traced to a customization for the reply area which used the pyHighlightedMessage property and converted newlines to br tags even in HTML mode. To resolve this, pyHighlightedMessage has ben modified to convert newlines to br tags only if the mode is plain text.
SR-A92387 · Issue 261229
Guardrail warning for offset/length removed from MapStructure rule
Resolved in Pega Version 7.2.2
In Map Structured rules, a guardrail warning was coming up for every row which had non-continuous length due to excess offset. This warning was generic without specifying the row number, and every time an attempt was made to justify the warning it was unrecognized and generated another warning. This left the rule with unjustified warnings on saving. As this rule is used often for generating excel sheets and formatting data neatly, it is not possible to provide the offset and length as expected by the Map Structured rule and there was a huge impact on the compliance score of applications when there was more than one Map Structured rule. As this is a common use case, the guardrail warning has been removed.
INC-175595 · Issue 652831
Java Bean import updated to handling differences in Java 7 and Java 8
Resolved in Pega Version 8.7
The behavior of the java bean Introspector class is inconsistent across different versions of the JDK when detecting indexed properties built off of java.util.List objects, causing Java Bean import to generate differently in Java 7 and Java 8. This has been resolved by updating PRIndexedPropertyDescriptor to better handle this JDK difference by resolving indexed read and write methods manually using simple reflection.