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-C65438 · Issue 406711

Added SAML parameter page generation for local use to bypass null auth object

Resolved in Pega Version 8.1.2

After defining any step which used parameters in the Post authentication activity of a SAML authentication service, the authentication failed with a java.lang.NullPointerException at com.pega.pegarules.session.internal.mgmt.Executable.putParamValue(Executable.java:3030). This was traced to local logic inserted to iterate through the SAML attributes that used a null parameter page. To resolve this, code has been inserted that will generate a new parameter page for the iteration rather than getting it from the authentication object.

SR-C65576 · Issue 405497

Data-WorkAttach-File made available for use of custom pxCreateSystemID

Resolved in Pega Version 8.1.2

An enhancement has been added to allow storing the pxCreateSystemID from pyWorkPage to Data-WorkAttach-File and Link-Attachment instances which were created on attaching a file. Previously, the Data-WorkAttach-.Default Data transform and Work-.AttachFile both set the pxCreateSystemID property to pxProcess.pxSystemName for Data-WorkAttach-File and Link-Attachment instances respectively. While Data-WorkAttach-.Default is ‘available’ and can be overwritten to set pxCreateSystemID as desired, the Work-.AttachFile was ‘Final’ and it was not possible to overwrite that to set a pxCreateSystemID manually. In order to support this use, extension points have been provided for the pyDefault data transform in the activities Work-.AttachFile and Work-.WorkURL which can be overridden.

SR-C65633 · Issue 408044

Improved handling for parsing multiple formats of DateTime

Resolved in Pega Version 8.1.2

In order to further correct an issue with DateTime formats, the system will now use the parseAsDateTime and parseAsDate functions to properly handle the parsing of the date and date time values. The Pega format will be tried first, and if that doesn't work then the UTF formats will be used. If there is still an issue, the system will call back on the original parseAsXSDDateTime/Date which should catch all cases. An exception will no longer be thrown until after all parsing methods are tried.

SR-C65757 · Issue 404535

Support added for POST binding in SAML logout

Resolved in Pega Version 8.1.2

Enhancements have been added in code and rule changes to support POST binding for SAML logout. In addition, handling has been added to resolve an ArrayOutOfIndexException error that was appearing if IDP sent parameters without any value.

SR-C65757 · Issue 406953

Support added for POST binding in SAML logout

Resolved in Pega Version 8.1.2

Enhancements have been added in code and rule changes to support POST binding for SAML logout. In addition, handling has been added to resolve an ArrayOutOfIndexException error that was appearing if IDP sent parameters without any value.

SR-C66114 · Issue 408082

Resolved pg empty error after db.open and improved error message

Resolved in Pega Version 8.1.2

When opening the data page D_RepositorySettings, the error "pg empty after db.open" appeared in the logs. This was due to the data page referring to the files webwb/zchecked.gif and webwb/zchecked.gif in many sections of the data page rule form despite these files having been removed as part of a recent cleanup meant to reduce storage requirements. In order to resolve this error, the zunchecked.gif and zchecked.gif images have been added back and the error message generated in the RUF pzGetbase64encodedImagehas been improved to add the target filename: "error occurred while opening the image:webwb/zunchecked.gif".

SR-C66283 · Issue 411634

Report Usage updated to always fully populate statistics regardless of page source

Resolved in Pega Version 8.1.2

After creating a report under the Log-ReportStatistics class, it was seen that reports under report usage were not reflecting the exact data. The inconsistency observed with embedded reports was due to grids being sourced by virtual RD, for which the report page had already been loaded elsewhere. In this case it was assumed that the statistics were already populated because the report page was already loaded. To ensure that reports are consistently accurate, pxRetrieveReportData has been updated to always call pzPopulateStatisticsInfo.

SR-C66624 · Issue 406226

Case type validation localized

Resolved in Pega Version 8.1.2

Localization has been added to the Case type validation description.

SR-C66627 · Issue 412779

Reject step placeholder text localized

Resolved in Pega Version 8.1.2

Localization has been added to the placeholder text of the approval reject step.

SR-C66633 · Issue 408774

Corrected DADT mapping for PegaDATA tables during upgrade

Resolved in Pega Version 8.1.2

After upgrading, old data tables being upgraded to new data tables (local storage) had the DADT table mapping changed from PegaDATA to CustomerDATA schema even though the tables themselves remained in PegaDATA format. This was traced to a missed use case in an enhancement that allowed creating a data type only in a CustomerData data base. To resolve this issue, the validation for restriction of PegaDATA has been removed and the param.nonPegatable will be set to false in cases where the database type is PegaDATA in pzCreateLocalDataStorage.

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