Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-A13188 · Issue 228542

Apache HTTP client library updated for improved security

Resolved in Pega Version 7.2

The Apache HTTP client library version 4.3.5 was identified as containing a security vulnerability. Both DSM and PRPC have been updated to version 4.3.6 in the DSM & PRPC SVN repositories respectively. In addition, new ADM service archives (WAR/EAR) need to be created with the updated library. VBD (service) does not use this library, so is not affected.

SR-A14475 · Issue 228318

Local ADM 'Fail Safe' settings honored in PostgreSQL

Resolved in Pega Version 7.2

When the ADM to was configured to persist learnings, the learnings/training data of ADM models was lost when server is restarted. This was traced to the default FailSafeEnabled setting of TRUE in PostgreSQL overriding the disabling of the ?FAIL SAFE? mode option from Decisioning -> Infrastructure -> Services. This mode puts the JDBC connection away from auto-commit and fails to put it back to auto-commit, thereby making ADM backups not commit to the database. This was on a per connection basis, so some connections would still save, but others would not. This has been fixed by explicitly ensuring all connections have the required auto-commit settings on ADM Server connections.

SR-A13888 · Issue 227100

D-nodes automated for sequential startup

Resolved in Pega Version 7.2

D-Nodes require that servers are restarted sequentially one after each other. In installations with a large cluster, this restart may get out of sync and result in some nodes not joining the cluster properly because of being restarted together. To improve this, the D-Node bootstrap procedure has been automated for an orderly restart to ensure no two D-nodes start in parallel.

SR-A13157 · Issue 225924

Performance enhancements in DSM

Resolved in Pega Version 7.2

Performance enhancements have been made to DSM. These include improving the timing info for Switch, Champion Challenger, Exclusion, and Data Join, and adding a Smart clone feature of SR pages if a check indicates that cloning would minimize memory footprint.

SR-A13157 · Issue 224896

Performance enhancements in DSM

Resolved in Pega Version 7.2

Performance enhancements have been made to DSM. These include improving the timing info for Switch, Champion Challenger, Exclusion, and Data Join, and adding a Smart clone feature of SR pages if a check indicates that cloning would minimize memory footprint.

SR-A10575 · Issue 220506

DSM monitoring and troubleshooting enhancements

Resolved in Pega Version 7.2

Monitoring and troubleshooting improvements have been made to the DSM components D-Node, VBD and ADM. These include an HTTP call which returns a node status that can be integrated into monitoring tools and raise appropriate alerts, and services to provide diagnostics information about d-nodes that can be sent by the cloud team to engineers for troubleshooting.

SR-A10575 · Issue 221174

DSM monitoring and troubleshooting enhancements

Resolved in Pega Version 7.2

Monitoring and troubleshooting improvements have been made to the DSM components D-Node, VBD and ADM. These include an HTTP call which returns a node status that can be integrated into monitoring tools and raise appropriate alerts, and services to provide diagnostics information about d-nodes that can be sent by the cloud team to engineers for troubleshooting.

SR-A6903 · Issue 216455

Data Flow correctly handles table encountering null numeric columns

Resolved in Pega Version 7.2

When a data set was created on top of a exposed table which contains some null value in numeric columns, a Data flow executed using that data set used the value '0' instead of the expected null property. This was traced to the Data Flow batch run execution using the DSMClipboardPages, which weren't able to differentiate if a property was present or not and led to null being mapped to 0 in a numeric property. To correct this, the NativeSQLAPI will return null values as empty values when querying a DB and will not use them populate a DSM page or propagate them in the data flow.

SR-A6903 · Issue 216454

Data Flow correctly handles table encountering null numeric columns

Resolved in Pega Version 7.2

When a data set was created on top of a exposed table which contains some null value in numeric columns, a Data flow executed using that data set used the value '0' instead of the expected null property. This was traced to the Data Flow batch run execution using the DSMClipboardPages, which weren't able to differentiate if a property was present or not and led to null being mapped to 0 in a numeric property. To correct this, the NativeSQLAPI will return null values as empty values when querying a DB and will not use them populate a DSM page or propagate them in the data flow.

SR-A7401 · Issue 216480

Performance tune-ups in DSM

Resolved in Pega Version 7.2

Strategy Profiler was showing misleading timing information for Switch, Champion Challenger, Exclusion, and Data Join. This has been fixed. In addition, Strategy Set has been optimized to let it evaluate the customer-specific expressions once per component execution (instead of per SR page) , and it will not clone SR pages if it's unnecessary. The Prioritization shape has also been improved to only prioritize the Top N if that?s configured.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us