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.

INC-182332 · Issue 668691

Updated handling for DepStatusFromQueue parameter in CaseDependency

Resolved in Pega Version 8.6.2

The pyCaseDependency declare trigger was not considering the DepStatusFromQueue parameter when an agent was involved. This was a missed use case for a customized calling of the check flow dependency, and was traced to the "DepStatusFromQueue" parameter being empty. This caused the dependency to not be resolved so the parent case was waiting indefinitely even though the child case had reached the required status for resolution, and the system has been updated to handle this scenario.

INC-182776 · Issue 666940

CheckFlowDependencies updated for auto-instantiated child cases

Resolved in Pega Version 8.6.2

A parent case with more than one child case was producing an unexpected behavior during the child case creation process. The first child case was instantiated at the correct point of the case stage based on its dependency condition, but the following cases were instantiated at the same point where the first child case was created irrespective of the dependency conditions defined in the other child cases. Investigation showed that the pxCheckFlowDependencies activity called from the Resolve activity was removing the named pages "pyTopCaseMap" "pyTopCaseWork" which are required for starting and validating configured auto-instantiate child cases in the pzCanStart function. To resolve this, an update has been made to CheckFlowDependencies which will use the activity "pzResolveCaseHierarchyMap" for removing the "pyTopCaseMap" and "pyTopCaseWork" pages based on DependencyType.

INC-183751 · Issue 665892

Improved text contrast for Attach Content button

Resolved in Pega Version 8.6.2

In order to improve accessibility, the contrast between text and background colors has been increased for the Attach Content button by updating pzMultiDragDropControlStandard to change the color from gray to black in function pzInitHTML5DD().

INC-184271 · Issue 668412

Portal Header persists appropriately

Resolved in Pega Version 8.6.2

The Portal header was disappearing immediately after case attachments were opened from the right sidebar and did not reappear even after refresh. This was traced to the absence of pd(event), and has been resolved by adding pd(event) to the onclick attribute in the anchor tag in the attachment UIKit rules.

INC-184300 · Issue 666156

Deprecated status removed from StartCaseType

Resolved in Pega Version 8.6.2

After updating from Pega v8.4 to v8.6, guardrail warnings were seen for the deprecated pxStartCaseType flow rule. This occurred for old case types created prior to v8.5. A utility has already been provided to upgrade the case type to include create stage, but this warning has been resolved by removing the deprecated status on pxStartCaseType to allow processes to proceed without a guardrail warning.

INC-186654 · Issue 669114

GetStatusChanges performance improvements

Resolved in Pega Version 8.6.2

Performance issues were seen when running the GetStatusChanges report. This was traced to the filtering methods used, and has been resolved by updating the report definition and enhancing the filtering conditions.

INC-172785 · Issue 662333

Adaptive model retry mechanism enabled

Resolved in Pega Version 8.6.2

Adaptive models were missing from the Model Management page as well as in the Prediction studio while similar models for the same proposition, only differing by the Channel name, were visible. This was traced to data not being synchronized between the database and Cassandra. The pegadata.pr_data_adm_factory database table did not contain the record of the missing channel, but Cassandra did. Since the current Cassandra adm_scoringmodel contained model information, the system still believed the model was present. In order to ensure Cassandra and the database table are in sync, an update has been made to enable the retry mechanism "SyncFactoryKeysTask" to create the ADM model in factory table by periodically looking for scoring models without factories or an entry in adm_meta.

INC-173596 · Issue 660220

Google OAuth and Spring versions updated

Resolved in Pega Version 8.6.2

The Google-oauth-client jar has been upgraded to version 1.31.1, and SpringFramework libraries have been updated to version 5.3.9 .

INC-174781 · Issue 655122

Kerberos authentication added for external Cassandra

Resolved in Pega Version 8.6.2

Support has been added for Kerberos authentication with Cassandra.

INC-175207 · Issue 664360

Added handling for DSM Services stuck in leaving status after database outage

Resolved in Pega Version 8.6.2

During a database outage, the heartbeat would fail and DSM services would eventually try to enter safe mode and stop. As the first step they would try to change the state to LEAVING, but because the database was down saving the LEAVING state failed and the exception was not handled correctly. This resulted in the rest of the stop operation logic not being executed and the service being stuck in LEAVING. To resolve this, an update has been made to ensure the service goes to LEAVING_FAILED if anything fails during the stop operation including when setting state to LEAVING_FAILED. The state LEAVING_FAILED will get flushed to the database eventually when it comes back up. This will allow the aggregation service to start from the LEAVING_FAILED state and recover by itself after a database outage.

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