SR-A5881 · Issue 217291
Blocked rule passivation error resolved
Resolved in Pega Version 7.2
An exception was being thrown for a blocked Data page when the system idled until the passivation time out occurred. This was an issue with the passivation attempting to read the blocked rule to set the context of PassivatorThread. To fix this, the system will use Thread-To-Be-Passivated for the context instead.
SR-A6900 · Issue 218481
Changed name check for page-ref skips
Resolved in Pega Version 7.2
When a work object which uses property-ref method was submitted, corruption was seen in the reference information if the name of the referring page and/or referring scalar property it contained was a substring of the name of a reference property that was intended to be skipped. For example, if a reference page list property called "TopPage. TestPageList" was to be skipped for encoding and there was a referring page property by the name of "TestPage", then encoding of "TestPage" was also skipped. To avoid this problem, the system now checks for the complete name of property "." instead of doing partial match with "contains". The page will not be saved if there is a reference property with the same name or something extra. For example: page "PRPCpage" will not be saved if there is a reference property "XXXPRPCpageXXX".
SR-A6666 · Issue 215202
Corrected handling of transient page list item
Resolved in Pega Version 7.2
When the "Do not save property data" option was checked, saving work data without clearing the page list properties caused an .IndexOutOfBoundsException error when attempting to reopen the same work object. This was an error in the handling of the transient page list item, and has been corrected.
SR-A8553 · Issue 220468
Corrected tenantname storage and reretrieval for field values
Resolved in Pega Version 7.2
The field values in the tenant layer were not getting translated unless a revalidate and save operation was performed. While preloading the field value conclusions, the conclusions are added into the map based on the tenantIdentifier but then fetched using tenantName. The code has been updated to use consistent naming.
SR-A8062 · Issue 217266
Diagnostic enhancements added to ClientAbortException errors
Resolved in Pega Version 7.2
An enhancement has been added to allow for better diagnostics for ClientAbortException: java.io.IOException errors. This error will now print the requestor ID and produce a stack trace for use in debugging the issue. The request URL and Query String will be also be printed when an IO Exception is caught, and the user ID will be provided if possible.
SR-A3665 · Issue 216774
Exception saving app entry to database resolved
Resolved in Pega Version 7.2
When using the developer portal (logged in as [email protected]), an error was added to the log file every time the user selected any of the explorers or opened any of the landing pages. The root cause was traced to the EJB class loader hierarchy not having these exception classes preloaded at startup, and this has been fixed.
SR-A5110 · Issue 214245
Fixed exception generated by 'getclassname' used with autocomplete
Resolved in Pega Version 7.2
An issue was found in some new installations using autocomplete where trying to set and execute 'getclassname' after a name change caused a conflict between the old and new values. The problem was traced to a function that set the new value and then repeated a call to the old one, nullifying the change. This did not effect upgraded systems due to a difference in the storage stream versions, and the conflict has been resolved by updating the logic
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.