Skip to main content
circle-square
Outline Circle
square-square
Little Circle
square-square
Little Circle

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 SR ID number in order to find the associated Support Request.

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.

SR-A76763 · Issue 252485

Ensured Dirty pop up appears for mobile log off

Resolved in Pega Version 7.2.2

While closing a dirty form on a mobile device, the warning popup was not shown while logging off. A check has been added to control_actions so logging out will return 'if dirty' to resolve this.

SR-A103064 · Issue 270247

Schema Change Tracking query performance improvements

Resolved in Pega Version 7.2.2

A query which was used in Schema Change Tracking (Designer Studio -> System -> Database -> Schema Change Tracking) was causing high CPU usage. This was due to the query having a full table scan which was using Information_schema, and the query has been rewritten for better efficiency.

SR-A88372 · Issue 259463

BIX log now includes BIX version info

Resolved in Pega Version 7.2.2

In order to enable better system tuning, the system has been updated to specify the BIX version in use in the logs. i.e. BIX Version : 7.1.9

SR-A89295 · Issue 258931

Result count option added to Campaigns for performance tuning

Resolved in Pega Version 7.2.2

Slowness was seen when launching and running Field Marketing Campaigns. This was an issue with loading results using pxRetrieveReportData with paging enabled, as it fetched the total result count for each page. To resolve this, an option has been added to pxRetrieveReportData to disable fetching of total result count. This is available as Embed-QueryInputs property of type TrueFalse called 'pyReturnResultCount' when running report using pxRetrieveSearchData's pyReportParamPageName Parameter.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us