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-A87552 · Issue 257706
Implicit privileges do not generate warnings
Resolved in Pega Version 7.2.2
RARO with implicit privileges was generating warnings that affected the compliance score. There is a particular format for declaring implicit privileges. i.e. Classname:ruleName, and the system has been updated with a check for this so implicit privileges will not be adding any guardrail warnings.
SR-A101006 · Issue 272734
JDBC password handling corrected
Resolved in Pega Version 7.2.2
After upgrade, a JDBC database connection on WebSphere 8.5/Oracle 11G indicated success on test connection, but a username/password "connection could not be obtained" error was thrown when attempting to save the connection. This was due to the handling of the encrypted password, and has been fixed.
SR-A101808 · Issue 269472
WebSphere deployment documentation updated to clarify JVM configuration advice
Resolved in Pega Version 7.2.2
The deployment guides for WebSphere have been updated to clearly distinguish between Oracle and IBM JVM when providing JVM configuration advice.
SR-A24989 · Issue 248910
WebSphere deployment guide updated to clarify scope settings
Resolved in Pega Version 7.2.2
The WebSphere Deployment Guide has been updated to indicate that the scope must be "server". If this is not set correctly in a split schema installation, the defaultSchema namespace bindings are defined at the cell level and will not be picked up at start, and the database user in the jdbc/PegaRULES datasource will not have the necessary privileges to run the system. Please see WAS deployment guides on the PDN for further information.
SR-B599 · Issue 270485
Flow Dependency queries performance improvements
Resolved in Pega Version 7.2.2
Case dependency queries executed by PEGA have been tuned to improve system performance when mid flow dependencies are getting fulfilled.
SR-A98702 · Issue 270066
Minor update to help doc for property optimization run time
Resolved in Pega Version 7.2.2
The help file for Property optimization using the Property Optimization tool has been updated with non-critical corrections to the phrasing regarding the length of time that might be required to perform background processing.