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.
SR-C66654 · Issue 406218
Pulse App Studio localization added
Resolved in Pega Version 8.1.2
Localization has been added to the Developer collaboration text in Pulse App Studio.
SR-C66998 · Issue 404593
Thread name implementation fixed for FCM use with micro DC
Resolved in Pega Version 8.1.2
When attempting to invoke a remote case in the Interaction Manager portal via FCM with the Customer Service for Insurance application which uses micro DC, the case was not invoked and an empty screen was displayed. Invoking the case from the interaction portal resulted in a JavaScript error. Invoking the case from a WSS or directly from the Create button in Designer Studio worked correctly. This was traced to a recent change to the implementation for generating the thread name. Because of this, CRM apps could not load the Federated cases via micro DC. This has been fixed through changes in "pzFCMMashupGadget" to replace the slash with underscore for the FCM thread. In addition, a modification was made to use the pega:onlyonce tag so mashup scripts are not loaded multiple times and will maintain their unique data-pega-gadgetname attribute values.
SR-C67376 · Issue 406719
SOAP Connector Wizard 'Create' button conditionally accessible
Resolved in Pega Version 8.1.2
Previously, the 'create' button in the SOAP Connector Wizard was disabled if the application was password protected. As an enhancement, the create button is now accessible if the existing ruleset and version is selected.