SR-A24962 · Issue 248678
DataSet-Execute updated to correct time-to-live error
Resolved in Pega Version 7.2.2
When using the time to live option of a Decision Data Store dataset, the java generation for the DataSet-Execute method was causing java compilation errors. This was due to an inconsistency between the code generation for DataSet-Execute method in an activity and the settings provided. To correct this, the algorithm used to generate the code for DataSet-Execute method has been updated to include the time to live setting and to generate correct and compilable code.
SR-A80784 · Issue 254197
Enhancement for Facebook connector retrieval
Resolved in Pega Version 7.2.2
Whenever the Facebook connector was restarted, historical posts on the monitored page were being fetched and duplicate documents were getting harvested into the DB. To resolve this, a new search parameter has been added for the Facebook connector that will receive a date as parameter for how many period/days of historical data to fetch.
SR-B6425 · Issue 275629
Scrum Board chicklet error resolved
Resolved in Pega Version 7.2.2
After collapsing and expanding a user story chicklet in the Scrum Board, adding a new note to the user story would cause the user story chicklet to disappear. This was a rendering issue due to an error in the type property syncing with the level property, and has been fixed.
SR-A94166 · Issue 262015
Fixed misaligned headers in decision table
Resolved in Pega Version 7.2.2
A misalignment of column headers was seen in a decision table when the number of columns added exceeded 18-20. This has been corrected by adding pixel adjustment of the scroll width to the decision table header when a range is selected for a column in pzRuleDeclareDecisionTableStandard js.
SR-A92650 · Issue 262402
PackageRuntime error resolved
Resolved in Pega Version 7.2.2
A pzPackageRuntime error when saving instance of custom rule was traced to the variable not being in the scope. This has been addressed.
SR-A97752 · Issue 271947
Test Suite operator ID error fixed
Resolved in Pega Version 7.2.2
After creating and executing a Test Suite, the error "Unable to open an instance using the given inputs: pxObjClass = "Data-Admin-Operator-ID", pyUserIdentifier = "System" appeared on the Dashboard landing page of the Automated Unit Test. This was due to the system not setting the operator identifier when doing the agent login, and has been corrected.
SR-A100251 · Issue 271797
Editing a decision table works on hardened system
Resolved in Pega Version 7.2.2
After enabling URL Encryption and URL Obfuscation in the Production Environment per Pega best practice recommendations to secure/harden an environment, an HTTP 400 error was thrown when attempting to Edit a Decision Table in Pega Marketing. This was an error in the URL decoding for the DisplayModalDialog HTML rules, and has been fixed.
SR-A88818 · Issue 261452
New pzPreMergeSave activity Rule-File- for multiple node propagation
Resolved in Pega Version 7.2.2
After merging rules of type Rule-File-Text across four nodes, there was a delay in the changes being reflected on the other nodes. The issue was caused by a simple save of Rule-File-Text not propagating pulseChange directly, and has been fixed by creating a new pzPreMergeSave activity Rule-File- to handle this merge.
SR-A87492 · Issue 256199
Strip "()" from Page name for Loop and Parameters for post-upgrade compatibility
Resolved in Pega Version 7.2.2
After upgrade, a change in system behavior with RUF Utilities.findClassOfPageReference returned the incorrect class name for pages that contained the string "()". For example, existing pages and classes has the entry TestPage.pxResults(), but the system is looking for an input page named TestPage.pxResults, and the startsWith check failed. To resolve this, the code has been updated with added logic in findClassOfPageReference to remove the empty () if it is present at the end of page and classes entry.
SR-A93033 · Issue 260830
Better visibility for preconditions after upgrade
Resolved in Pega Version 7.2.2
After upgrade, all preconditions (e.g.. WHEN rule) in Collection rules appeared to be missing. Though pyPreconditionWhen was populated, pzShowPrecondition was not set for a collection that was imported from v6.2 and did not display. To resolve this and create better backwards compatibility, pzShowPrecondition will be set to true/false based on whether pyPreconditionWhen is blank or not. This will be set in openDefaults activity for Rule-Declare-Collection .