SR-A20470 · Issue 240001
Twitter harvesting enhanced
Resolved in Pega Version 7.2.1
Data recovery has been improved for Pega Customer Service Social Engagement customers harvesting Twitter streaming data. If a steaming data set fails for any reason, whether due to disconnecting of the API for a short period, server failure, or for any other scenario where Tweets are not ingested in real time, the data recovery capability will fetch missed Tweets within a given set time window of recent Twitter historical data. This is done through an activity to create a Twitter search data set which can then be used to work act as a data source for the data flow. Additionally, logic has been added to identify the appropriate language for short inputs (one or two words).
SR-A20504 · Issue 241375
Queue type validation updated in MDBListener
Resolved in Pega Version 7.2.1
Queue type validation failed when testing connectivity in MDBListener if the pyResourceName was set with queue name and there was no pyResQueueName defined in the page. To handle this, the getString function will use the pyResourceName instead of pyResQueueName.
SR-A20569 · Issue 238382
Mandatory date and amount fields validation performed before reset
Resolved in Pega Version 7.2.1
Date and amount fields changed to incorrect format if any mandatory field was empty and screen was saved. This was traced to a handling error where the reset of read-only formatting happened before the validation check, and has been fixed.
SR-A20581 · Issue 242760
Added checks to pagelist indexes for processing and recovery
Resolved in Pega Version 7.2.1
Sporadically, work objects saved to the database generated the error "The Flow Action pre-processing activity pyPopulateCaseContentsWrapper failed: cannot be null or blank. page: . Details: Invalid value for aReference passed to com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.getProperty(String, char)" This happened when changes to Indexes in pagelists were getting overridden with another pagelist index, causing data to be lost on database save. A check has now been added to identify whether the entry has been processed in the current encode, and a hard check has been inserted to prevent data loss of page lists.
SR-A20593 · Issue 238898
Pagination added to Hotfix Manager
Resolved in Pega Version 7.2.1
If there were more than 10 uncommitted hotfixes, the Hotfix Manager was not able to display them all due to a page limit and pagination being disabled by default. The pagination footer has now been made visible to allow viewing of the full list of uncommitted fixes.
SR-A20603 · Issue 241334
Post-upgrade Connect-SOAP multi-ref mapping fixed
Resolved in Pega Version 7.2.1
After upgrade, the Connect-SOAP responses including multi-refs were not getting mapped correctly and there were problems viewing the response message from the SOAP service. This has been fixed.
SR-A20634 · Issue 248378
Added handling for missing blob from external data class
Resolved in Pega Version 7.2.1
When using an external data class, an error was generated complaining of "trying to retrieve property pxInsHandle from a fully exposed table that does not contain it". This happened because the external table did not have a blob column but did have pxObjClass and pzInsKey, and handling has been added to correct this.
SR-A20639 · Issue 239986
Special Character conversion added to ExportToPDF
Resolved in Pega Version 7.2.1
If the file name used in the ExportToPDF activity contained special characters like ", ?, *, , |, :, a JS exception occurred. To resolve this, special characters like ", ?, *, , |, : will be replaced with "_" as these special characters are not supported in file names.
SR-A20675 · Issue 243568
Repaired encrypted remote tracing
Resolved in Pega Version 7.2.1
Remote tracing was not working when URLEncryption was enabled due to an error calling SafeURL. This has been fixed.
SR-A20761 · Issue 247086
New test Suite ruleform display resolved
Resolved in Pega Version 7.2.1
When attempting to create a new unit test suite, no ruleform was presented. Instead, raw XML was displayed. To correct this, the TestSuite Rule Form has been autogenerated so that it is viewable and openable in 7.2 in supported browsers.