SR-A2418 · Issue 213013
Fixed PageLists extract errors
Resolved in Pega Version 7.2
Unmatched strings in XML Output Extracts were causing some Page Lists to fail. A filter method has now been added to return unmatched strings.
SR-A5624 · Issue 217224
Fixed rollback to preserve status of SLA Queue Entries
Resolved in Pega Version 7.2
When moving ahead in a flow from Assignment A to Assignment B, if A had an SLA configured on it and an exception was thrown, a rollback was triggered that put the case back into Assignment A but removed all changes done within the context of the case processing and the SLA queue entry had its pyItemStatus set to "Now-Processing" instead of "Scheduled". This was an issue with the status locking in the dequeue process that was not preserving the original status, and has been fixed.
SR-A4626 · Issue 218040
Handling added to ensure proper localization after passivation
Resolved in Pega Version 7.2
An unexpected localization was occurring after passivation for an operator with en_GB as default locale (for which there is no language pack): after leaving the browser idle for some time, the Designer Studio UI would use the JVM locale and any associated language pack when resumed. This was due to passivation and reactivation being handled by processes that looked at different application context information, and a check has been added to ensure the proper context is restored.
SR-A6945 · Issue 215685
Modified pyRuleExecutionMessagesLogged search activity to handle rolling file names
Resolved in Pega Version 7.2
The pyRuleExecutionMessagesLogged activity was returning the previous day's data as the latest results instead of the correct current results. This was traced to the pyRuleExecutionMessagesLogged activity only scanning log files that specifically have the string "log" in the name, but when using a dailyRollingFileAppender, the current day's logfile did not have "log" in the name (in the typical configuration). This was only added once the file is rolled. To correct this, the pyRuleExecutionMessagesLogged activity has been modified to find log files of a site's particular naming convention by updating the prlogging.xml file to fit the name search performed by the pyRuleExecutionMessagesLogged activity.
SR-A176 · Issue 210096
out-of-the-box validate activity now schema qualified
Resolved in Pega Version 7.2
The out-of-the-box validate activity did not support schema prefix, resulting in repetitive error messages/log file traffic which may give the impression of a system failure or mask other salient messaging. To resolve this, the Validate Activity for Rule-Admin-Nodes, Step 3, has been updated.
SR-A8254 · Issue 217223
Path extraction support added for REST connectors to NBAM
Resolved in Pega Version 7.2
If a system used pathinfo (containing "!") rather than requestURL, a null pointer exception was raised when attempting to access a REST service endpoint in Next-Best-Action Marketing (also called PegaMarketing) at the point when the system attempted to tokenize the "resources path". To allow for smooth operation after upgrade, code has been added to extract the necessary path information.
SR-A6089 · Issue 215650
Resolved Class name mismatch in root element in BIX XSD
Resolved in Pega Version 7.2
Running a series of comma separated extract rules to an XML file from the command line resulted in the class elements in the corresponding XSD file all having the same classname. This was caused by an error in the array list processing that caused the values to be overridden by the last extract processed, and has been corrected.
SR-A4158 · Issue 210201
Resolved hang during call for available DBMS connections
Resolved in Pega Version 7.2
The system was hanging after making repeated requests for available DBMS connections to the database. This was caused by an exception thrown by the requestor.getRequestorPage() call , and the thread handling has been revised to resolve this.
SR-A8075 · Issue 217226
Resolved NPE for large cache Factory Report generations
Resolved in Pega Version 7.2
When generating Factory reports from SMA, an exception was generated if it included a very large Property Reference cache. An enhancement has been added to skip null values and speed processing in these cases.
SR-A2695 · Issue 206875
Resolved Property-Ref method conflict for external page properties
Resolved in Pega Version 7.2
A discrepancy was found in the runtime and design time behavior of the Property-Ref method in allowing a property reference to point to a page that it is contained in page-list which in turn is embedded under another top-level page. Because the activity assembler needs valid class definition of property that has been defined on the right side at save time whereas the java was treated as just valid java code at design time and at runtime. Since the clipboard page, exists it assigned the reference. To clear up this conflict, the type resolution logic employed by the expression parser has been updated to ensure consistent property references.