SR-A90366 · Issue 258967
Removed incorrect pxObjClass addition during DSM optimization
Resolved in Pega Version 7.2.2
When the DSM page optimizer flag was on, trying to adapt a platform page group property to a DSM page group property was adding a pxObjClass into the DSM page group. This caused a class cast exception from String to ClipboardPage. This extraneous addition of pxObjClass when creating an empty DSM page group property has been removed.
SR-A80606 · Issue 254964
Data Import API updated to be case-sensitive
Resolved in Pega Version 7.2.2
When using a Data Import Shape for a Class Type which had a same named property identifier (but with a different case) as in the SR hierarchy, both the properties were considered valid and imported as SR properties. This caused issues in the strategy rule as the Set property components set the values for the incorrect instance and eventually led to strategy failures as the expected instance did not have a value set. This has been resolved by using a case-sensitive API to validate the source property against the target class.
SR-A24962 · Issue 250080
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-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-A77119 · Issue 255525
Fixed attaching files to pre-existing inflight cases after upgrade
Resolved in Pega Version 7.2.2
After upgrade, loading pre-existing inflight cases and attaching a file generated the error "Trying to save an invalid page: Trying to save an invalid page: page is not valid ". This was caused by a missing check for LinkPage.pyMemo if LinkPage.pyCategory is not set, and has been fixed by setting pyMemo from LinkPage.pyMemo.
SR-A88588 · Issue 256536
TopCasePage reference retained in CreateTopCase
Resolved in Pega Version 7.2.2
After upgrade, the "pyTopCasePage" page reference was missing in the Clipboard after a new case was created using the "pxCreateTopCase" activity in utility shape in a flow. This was traced to a step in the function that removed the pyTopCase page reference unnecessarily, and the pxCreateTopCase activity has been modified to preserve this.
SR-A90516 · Issue 258175
Resolved App Express error for new operator groups
Resolved in Pega Version 7.2.2
An error was appearing while creating a operator access group via App Express. This was an error in the commit while saving process if the entry in pyObjectsToCreate was FrameWorkAssets, and has been fixed.
SR-A86964 · Issue 256956
Corrected date value created by ShowConflicts
Resolved in Pega Version 7.2.2
An invalid format date value was being created by the "pzShowConflicts" activity, causing problems when trying to submit an assignment updated by another agent. This has been fixed by setting the value with the PRDateFormat.DEFAULT_DATETIME_MEDIUM format instead of DD-MM-YYYY.