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-C16122 · Issue 358344

Removed irrelevant Primary page properties

Resolved in Pega Version 8.1

Irrelevant properties were appearing on the primary page while using Address Map control. This was traced to an improper function call and has been corrected.

SR-C16126 · Issue 388052

XMLCipher.java implementation adjusted for updated JDK8

Resolved in Pega Version 8.1

Errors were seen when using the decryption feature of SOAP services To resolve this, the Pega implementation of XMLCipher.java has been adjusted to correlate to recent updates made to JDK8.

SR-C16229 · Issue 357687

Check added to SQL generation to exclude BOM

Resolved in Pega Version 8.1

When using the facility System Upgrade > "Upgrade Applications Schema" from Designer Studio to generate a SQL file (as opposed to running directly from Designer Studio), the downloaded SQL was found to contain the Byte Order Mark sequence (0xEF,0xBB,0xBF) at the start of the file. This byte sequence caused the DB2 command line client to fail. This has been corrected by adding a check that will set 'aIncludeBOM' flag to false for SQL file generation.

SR-C16281 · Issue 358133

Null check added for filterOutWithdrawnCandidates

Resolved in Pega Version 8.1

During RUF resolution, encountering a candidate that was outside of the current RSL generated an Null Pointer Exception. This has been corrected by adding a null check in filterOutWithdrawnCandidates. If the ruleset spec is null, the candidate will be removed from the list.

SR-C16365 · Issue 356219

Data Schema upgrade documentation clarified

Resolved in Pega Version 8.1

In order to eliminate confusion, portions of the Update and Upgrade guides relating to data schema upgrades have been clarified to differentiate "upgrade schema" and "temporary upgrade schema".

SR-C16479 · Issue 356880

Ruleset version check added to pzPackageParagraph activity

Resolved in Pega Version 8.1

The pzPackageParagraph activity was fetching Paragraph versions from different rulesets instead of only the highest rulesets. This caused performance issues on installations with large numbers of paragraph rules. To correct this, an 'if' check has been added to filter the Paragraph rules which belong to rulesets of lower hierarchy in rule resolution.

SR-C16490 · Issue 356910

Tuned layout visibility conditions

Resolved in Pega Version 8.1

In order to ensure the visibility conditions on layout are honored as expected, code has been added to avoid evaluating expressions from dom elements during the initial rendering of the screen.

SR-C16548 · Issue 360113

Fixed UDF calls schema prefix

Resolved in Pega Version 8.1

UDF calls were being prefixed with the schema name of the class rather than schema name in which the AllOf/OneOf functions are stored. To correct this, the UDF will instead be prefixed using the schema name of the PegaDATA database where the functions/UDFS are installed.

SR-C16693 · Issue 359290

Column name shows in filter section RD of drilldown report

Resolved in Pega Version 8.1

The Column name in the drilldown filter was displayed as a function in the 'column source' (of the main report definition) in the drilldown report, but the name was not provided in the 'column name' column in the query tab of the main report definition. This has been corrected.

SR-C16751 · Issue 360165

Code fixed for harness pyCMReports

Resolved in Pega Version 8.1

An error in the code was causing the report browser (harness pyCMReports) to fail if it was generated by the pxgetRRContentForRB activity. This has been corrected.

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