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-B6704 · Issue 289314

Auto-populate updated for better page copy references

Resolved in Pega Version 7.3

After upgrade, an error was generated at a page-remove step on the Group information screen while running the quoting process. This happened in cases where a copy was made of a page containing an auto populate property and the data page referred by the AP had Common Parent references, and was traced to the parent page of the reference property having been removed from the common parent page. To resolve this, the auto-populate function has been updated to better maintain references in copies.

SR-B6971 · Issue 285310

Error propagation corrected for RDB-Save with RunInParallel

Resolved in Pega Version 7.3

If several Connect SQLs were called via the RDB-Save activity method with RunInParallel selected, failure of one of the Connect SQLs was not being caught and no errors were captured. This was traced to a situation where an exception thrown at the childcase with this combination of settings was propagated to the parent, and has been corrected by adding a Data-Admin-System-Setting "isPropagateExceptionFromChildToParent" defined in "Pega-RULES" ruleset, which has a default value of "true" only for RDB-Save method (not for all RDB-methods).

SR-B6971 · Issue 279537

Error propagation corrected for RDB-Save with RunInParallel

Resolved in Pega Version 7.3

If several Connect SQLs were called via the RDB-Save activity method with RunInParallel selected, failure of one of the Connect SQLs was not being caught and no errors were captured. This was traced to a situation where an exception thrown at the childcase with this combination of settings was propagated to the parent, and has been corrected by adding a Data-Admin-System-Setting "isPropagateExceptionFromChildToParent" defined in "Pega-RULES" ruleset, which has a default value of "true" only for RDB-Save method (not for all RDB-methods).

SR-B6980 · Issue 278169

fixed naming in multiple extracts run from the command line

Resolved in Pega Version 7.3

When running multiple comma separated extracts at a time using command lineoption -i, all of the rules in the manifest file contained the value of the last extract name only. This was a missed use case, and ExtractImpl has been modified to correct it.

SR-B7225 · Issue 277783

BIX documentation updated for Extract Rules

Resolved in Pega Version 7.3

The documentation outlining best practices for using BIX has been updated to reflect that when extractions are being run asynchronously there must be enough threads for each of the concurrently running extractions. The section "Running an Extract rule using a Pega 7 Platform agent" has been updated to read: "Number of concurrent extracts scheduled has to be limited based on the prconfig "agent/threadpoolsize." Set the prconfig setting agent/threadpoolsize to the max number of concurrent extractions you will be executing. The default value for this setting is 5 and the maximum value is 10.

SR-B7620 · Issue 289885

PopulateCaseContents activity updated

Resolved in Pega Version 7.3

The PopulateCaseContents activity has been updated to better handle missing or empty properties to ensure the flow name and RefObjectClass values are populated properly.

SR-B7620 · Issue 289885

PopulateCaseContents activity updated

Resolved in Pega Version 7.3

The PopulateCaseContents activity has been updated to better handle missing or empty properties to ensure the flow name and RefObjectClass values are populated properly.

SR-B7942 · Issue 284735

PDF barcode generation from eForm given configurable parameter checkbox

Resolved in Pega Version 7.3

When generating a PDF file based on an eForm that contains barcodes displayed via base64 encoded images, making the file read-only by using ConcatenateEForm's PerformFieldFlattening option prevented the barcodes from displaying. This was due to an "append" flag being passed to the 3rd party iText Library API "PdfStamper", and has been resolved with the addition of a flag (EnableNewVersion) in the "GenerateEForm" activity. The parameter will be by default true and may be unchecked for false, and is accompanied by a tool tip on hover of the checkbox as well as iText help.

SR-B7942 · Issue 285735

PDF barcode generation from eForm given configurable parameter checkbox

Resolved in Pega Version 7.3

When generating a PDF file based on an eForm that contains barcodes displayed via base64 encoded images, making the file read-only by using ConcatenateEForm's PerformFieldFlattening option prevented the barcodes from displaying. This was due to an "append" flag being passed to the 3rd party iText Library API "PdfStamper", and has been resolved with the addition of a flag (EnableNewVersion) in the "GenerateEForm" activity. The parameter will be by default true and may be unchecked for false, and is accompanied by a tool tip on hover of the checkbox as well as iText help.

SR-B8478 · Issue 278805

ExtractSection data transform optimized

Resolved in Pega Version 7.3

The code in pzExtractSectionPostDT and pzExtractSectionPostActivity has been optimized to improve data transform processing time.

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