SR-A92306 · Issue 260466
Enhancement added to configure Hazelcast threads
Resolved in Pega Version 7.2.2
An enhancement has been added to configure the number of threads used by Hazelcast via Data-Admin-System-Settings. The following 4 settings can be used, all associated with the Pega-Engine Ruleset, corresponding to Hazelcast System Settings: - hazelcast/operation/generic/thread/count - hazelcast/operation/thread/count - hazelcast/io/thread/count - hazelcast/event/thread/count If these settings are undefined, the system will fall back to Hazelcast default values.
SR-A93324 · Issue 260101
Pega-RULES DateTime handling corrected for backwards compatibility
Resolved in Pega Version 7.2.2
An error was found in the function Pega-RULES DateTime dateTimeToDecimal--(String,String,PublicAPI) that caused issues with backwards compatibility and possible XML Parsing Errors. Handling of the second parameter to the dateTimeToBigDecimal function has now been updated to be consistent with with previous versions.
SR-A22436 · Issue 252908
Handling added for ObjClass property status
Resolved in Pega Version 7.2.2
An issue was found with creating or updating SFA operators from the Sales Ops portal due to security tracking conflicts while working with pages that have pxObjClass as a normal property and pages with pxObjClass as a special Java property. To resolve this, a check has been added to verify the presence of pxObjClass both as a normal property as well as special java property to avoid conflicts.
SR-A87988 · Issue 255841
Resolved Null Pointer Error for static rule assembly
Resolved in Pega Version 7.2.2
An Null Pointer Error was being generated in some cases of static assembly due to the handling of the deletion of the used rules. This has been fixed.
SR-A86152 · Issue 255318
Resolved Null Pointer Error for static rule assembly
Resolved in Pega Version 7.2.2
An Null Pointer Error was being generated in some cases of static assembly due to the handling of the deletion of the used rules. This has been fixed.
SR-A76749 · Issue 252664
Changed cache behavior for DecisionParameters rule java class
Resolved in Pega Version 7.2.2
An OOM error was occurring due to multiple instances of the class loader "com.pega.pegarules.exec.internal.util.classloader.PRClassLoaderDB$Loader" being cached and each then loading an independent instance of the decision data rule Rule-Decision-DecisionParameters without subsequently invalidating the cache. To correct this, the PRSecurityPolicy.java has been updated to remove pdcache from PRSecurityPolicy..getProtectiondomain(...) so Policy Objects will not be cached. The expected impact on the system is minor.
SR-A75899 · Issue 256349
Character parsing improved for overridden sort function
Resolved in Pega Version 7.2.2
An overridden sort function could not be found when being called from a grid. This was due to the method name having two hyphens, and has been corrected by adding handling to strip and parse the methodName properly even when it contains "--".
SR-A75899 · Issue 260981
Character parsing improved for overridden sort function
Resolved in Pega Version 7.2.2
An overridden sort function could not be found when being called from a grid. This was due to the method name having two hyphens, and has been corrected by adding handling to strip and parse the methodName properly even when it contains "--".
SR-B2905 · Issue 273518
Obj-Save of large numbers of classes with CLOB properties
Resolved in Pega Version 7.2.2
Clob code for Oracle has been optimized to support Clobs > 4K in size
SR-A98978 · Issue 266552
Property references work on parameterized data pages
Resolved in Pega Version 7.2.2
Doing a property reference between data pages from a parameterized source page to target page loaded both pages, but also created a 'phantom' D_SourcePage[] loaded on the clipboard. This was traced to having the Property-Ref of a property in the data page refer to another data page property using the syntax D_SourcePage[test].pyNote. When such a syntax is written, instead of the parametrized overloaded method, the unparameterized version of the method is called. Later display of the data page XML only acted on the source page name since keys weren't set during setAsReference, effectively doing a findPage without a parameter. To correct this, the reference will use the data page source while doing setAsReference to ensure that the keys are available while trying to display the data page XML and thereby load the data page with the correct parameters.