SR-
114971 · Issue 164164
SOAP settings updated to work with IBM JDK 1.7
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
When calling Service SOAP hosted on Websphere 8.5+ and JDK 1.7, the SOAP client was failing with a java.lang.VerifyError. This was traced to a change in the settings necessary for use with IBM JBK 1.7, and the needed properties have been updated.
SR-
114971 · Issue 165871
SOAP settings updated to work with IBM JDK 1.7
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
When calling Service SOAP hosted on Websphere 8.5+ and JDK 1.7, the SOAP client was failing with a java.lang.VerifyError. This was traced to a change in the settings necessary for use with IBM JBK 1.7, and the needed properties have been updated.
SR-
116448 · Issue 166844
SOAP settings updated to work with IBM JDK 1.7
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
When calling Service SOAP hosted on Websphere 8.5+ and JDK 1.7, the SOAP client was failing with a java.lang.VerifyError. This was traced to a change in the settings necessary for use with IBM JBK 1.7, and the needed properties have been updated.
SR-116479 · Issue 170952
Elapsed Time reporting corrected
Resolved in Pega Version 7.1.7
Two out-of-the-box reports, Elapsed Status Time Trend and Average Elapsed Time Per Status, were causing the browser to freeze and stop responding if there were more than 1000 records. This was caused by an invalid value for the datetime units on the category for the chart causing looping behavior. This has been corrected.
SR-116508 · Issue 170253
Large flow handling improved for IE8
Resolved in Pega Version 7.1.7
When opening a large flow in IE8 which includes multiple sub flows, a long-running script warning is displayed. This is caused by too many calls being executed at once on IE8, and has been remedied by turning on the asyncProcessing parameter for IE8.
SR-116510 · Issue 171699
Handling corrected for testing rulesets with multiple versions
Resolved in Pega Version 7.1.7
If two rulesets with multiple versions were moved to a test environment, when the product rule was created only one of the version's instances was in the .jar file. This issue was caused by incomplete clearing of the ruleset spec after collecting the rules, and has been corrected.
SR-116556 · Issue 170813
AllLinksForParticularRule changed from Final to Available
Resolved in Pega Version 7.1.7
The list view reporting limit AllLinksForParticularRule has been changed from a Final rule to an Available rule in order to allow an increase in the number of links shown in the Application Profile. The default is 500.
SR-116585 · Issue 167063
Screen flow previous button repaired in obfuscated IAC
Resolved in Pega Version 7.1.7
When using IAC with obfuscation is enabled, the screen flow 'previous' button was not responding. This was caused by the '\' at the end of the URL parameter being accidentally obfuscated as well, and has been fixed.
SR-116587 · Issue 170222
Clarified default values for Create Class
Resolved in Pega Version 7.1.7
The Create Class screen was offering default values that had the potential to lead to classes being created in an incorrect / invalid part of the Class Structure. This has been corrected.
SR-116597 · Issue 169929
Correct report name displaying on chart reports
Resolved in Pega Version 7.1.7
In Case Manager reports, maximizing a report containing a chart showed the URL as the report name if the report title parameter did not have a value. This field has been updated to default to the report's title if the name has not been explicitly set.