SR-A7275 · Issue 216805
Added non-ASCII character handling to MSOGenerateExcelFile activity
Resolved in Pega Version 7.2
When the name of the file to be downloaded contained Japanese characters, the resulting file name displayed spaces in place of the Japanese characters. This was due to the characters in the file name not being encoded using the same character set which would then be used by the browser to decode the file name. To resolve this, the name of the file to be downloaded is now set as part of the Content-Disposition response header and will support non-ASCII characters
SR-133693 · Issue 206383
Agent SystemCleaner default time changed
Resolved in Pega Version 7.2
Timezone conversion issues were causing sporadic issues with Agent SystemCleaner terminating prematurely in J2EE environments. By default, the agent will now run at 12:05am rather than precisely at midnight.
SR-A2960 · Issue 218751
Asynch loaded data pages correctly pulled into main thread
Resolved in Pega Version 7.2
After using Load-DataPage, using Connect-Wait to synchronize with child requestor caused the data page to be loaded again when it was referenced instead of the system bringing the asynchronously-loaded data page forward. This was caused by differing value handling during the cache key building for ADP load, and has been corrected.
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