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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-A52484 · Issue 251721

BIX Extract retains pre-upgrade filenames and columns

Resolved in Pega Version 7.2.2

After upgrade, extract rules were created with underscores replacing dashes in the original filenames and ExtractIndentifier and ExtractDateTime columns were added to the output csv file. This was an inadvertent change related to enhancements made to filename conventions, and has been corrected with the prconfig "bix/retainOriginalFileNameForCSV" to retain the filename as provided in the extract rule and the prconfig "bix/ignoreAdditionalColumnsInCSV" to not add the new additional columns pxExtractIdentifier and pxExtractDateTime when upgrading rulesets.

SR-A24412 · Issue 249993

Calendar icon display fixed for Microsoft Internet Explorer11

Resolved in Pega Version 7.2.2

Calendar icons were not displayed in a data table in Microsoft Internet Explorer 11 due to the browser not supporting the icon rendering. A meta tag has been added in the ReviewHarness to correct this.

SR-A23686 · Issue 249793

Support extended for NUMERIC types in RD SQL joins/filters

Resolved in Pega Version 7.2.2

Support has been extended for NUMERIC types in Report Definitions, more specifically to support references to NUMERIC properties in join and filter conditions in RDs using SQL Server 2012, by updating the IDENTITY column type handling in the RUF pzCheckCompatibilityOfColumnTypes function.

SR-A75946 · Issue 252101

pxCommitDateTime BIX extraction more robust

Resolved in Pega Version 7.2.2

The exported XML file was not including the pxCommitDateTime column even when that column was included in the BIX extraction. This was traced to the site trying to perform the commit on the same work object more than once: performing the commit the second time caused the previous value to be overridden by the new commitdatetime. That led to the pxCommitDateTime not being stored in the BLOB, and since BIX extracts the data from source table's BLOB, it cannot extract the value of pxCommitDateTime. To resolve this, the source query that BIX uses has been modified to get both pzPVStream and pxCommitDateTime (if the column is present in the source table) and use the value of pxCommitDateTime from the resultset while writing to the output file.

SR-A21761 · Issue 250141

Check added to ensure proper descendant class report building

Resolved in Pega Version 7.2.2

A declare page initially accessed from an operator runs a query against the implementation class in order to populate the declare page, but if the declare page is initially referenced by a service, the report is run against the framework class instead. This difference could lead to an issue where authorization switching would cause some declare pages to be built with the wrong class if the user's AG matched the service package AG. To avoid this, the Authorization.setActiveAccessGroup() method has been updated to include an additional check to continue the flow if the requestor has service package pool name set.

SR-A23560 · Issue 250384

Check added to ensure proper descendant class report building

Resolved in Pega Version 7.2.2

A declare page initially accessed from an operator runs a query against the implementation class in order to populate the declare page, but if the declare page is initially referenced by a service, the report is run against the framework class instead. This difference could lead to an issue where authorization switching would cause some declare pages to be built with the wrong class if the user's AG matched the service package AG. To avoid this, the Authorization.setActiveAccessGroup() method has been updated to include an additional check to continue the flow if the requestor has service package pool name set.

SR-A97401 · Issue 265625

DASS validation can be switched from ERROR to WARN

Resolved in Pega Version 7.2.2

An enhancement has been added to allow optional switching of the validation of the column type mismatch to WARN as a save-time error/Guardrail warning instead of ERROR. This is based on the new DASS function 'reporting/validateColumnTypeMismatchAs', and the owning ruleset is 'Pega-Reporting'. Note : Even though save-time and run time validations are skipped using this DASS, the query may fail if the database does not support varchar and decimal comparison.

SR-A89836 · Issue 262431

Fixed error from Sales Automation CreateQuote button

Resolved in Pega Version 7.2.2

An exception was being generated by a button click on Sales Automation application due to the reference in the when rule and in the expression being the same but belonging to different loadContexts. This confused the legacy network, and has been modified so the legacy network stops evaluating expressions' tracking refs when the ACR belongs to a decision rule.

SR-A76647 · Issue 253238

Resolved ConcurrentModificationException in mContent iteration

Resolved in Pega Version 7.2.2

When adding or removing the items from a repeat grid and submitting the modal dialog, an intermittent ConcurrentModificationException was coming from the API ClipboardPageImpl.clearMessages(). This was traced to the function iterating over mContent and has been fixed by making a copy of mContent and iterating over that.

SR-A87807 · Issue 260853

Sequencing improved for RDE triggering

Resolved in Pega Version 7.2.2

While data was being mapped from one page to another page using data transform and a page property referred to a data page that was being freshly loaded, then R-D-E expressions were not getting fired even though input properties of R-D-E's were getting changed. If data page instance was found for the referenced page property, then R-D-E expressions were fired as expected. This was traced to the forward chaining not completing before the loader was triggered, and the sequencing has been adjusted to resolve this problem.

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