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-146339 · Issue 600744

ViewID parameter passed as part of DX API response payload for level 5 applications

Resolved in Pega Version 8.5.2

Recent work to not consider production level and always pass 'viewID' parameter as part of DX API response payload was not working for cases where the APIProductionLevel was 5. This was a missed use case based on a condition that remained on the ViewID parameter, and the condition has now been removed.

INC-153877 · Issue 612371

Enhanced socket timeout logging

Resolved in Pega Version 8.5.3

In order to assist with diagnosing issues with socket timeouts such as a Data Flow Daily Run failing, logging to print the SocketTimeout value has been added when case info is enabled.

INC-143191 · Issue 596469

Scheduled tasks landing page shows all tasks

Resolved in Pega Version 8.5.2

Due to pzGetScheduledTasks listview having a hardcoded limitation of 500 records to be fetched, not all scheduled tasks were being shown in the scheduled tasks landing page. This has been resolved by modifying the pyCreateSummary activity to use a newly created Report Definition to fetch data instead of list view.

INC-140848 · Issue 596461

Button row correctly added for click on exception list

Resolved in Pega Version 8.5.2

After upgrade, clicking on an exception list button in the mobile app was not adding a row to an existing PageList as expected. Investigation showed that pega.u.d.refreshSection was not executing correctly from RunScript, which was traced to a missed use case for handling an empty repeating dynamic layer in this scenario. This has been corrected.

INC-156094 · Issue 621064

Access control updated for non-auto-generated finishAssignment

Resolved in Pega Version 8.5.3

After upgrade, a flow containing a flow action that called an out of the box HTML rule was triggering a SECU0019 alert and blocking functionality. This was a missed use case for BAC where all non-auto generated rule actions should be registered, and has been resolved by registering finishAssignment.

SR-C76668 · Issue 424444

skipDocsRecreation option added to remove flickering during application launch

Resolved in Pega Version 8.2.1

In order to avoid visible flickering resulting from a dynamic container refresh conflicting with custom code during application launch, an enhancement has been added that can be used to skip the SDM refresh functionality based on the "pega.u.d.skipDocsRecreation" JS property. This can be enabled in Userworkform.

INC-207320 · Issue 701083

Email Approver shown in audit

Resolved in Pega Version 8.7.1

Email Approver activity was not being shown in Audit. This was traced to the queue instance primary page missing the necessary pyInboundEmail page property from pyCreateAndManageWorkFromEmail, and has been resolved by updating the listener activity to copy the needed value to a property called pyEmailFrom which will be used to record the events in the audit.

INC-193847 · Issue 695974

DSS added to allow masking of subjectID in alerts

Resolved in Pega Version 8.7.1

In order to allow customizing whether or not a subjectID is included in alerts, a DSS has been added to conditionally mask the subjectID from being logged. To use this, set the "alerts/maskIHsubjectID" DSS in the Pega-DecisionEngine ruleset to true to hide the pySubjectID.

INC-139054 · Issue 598153

PD4ML library updated

Resolved in Pega Version 8.5.2

When generating a PDF, lines were broken up for the content boxes. This was an issue with the included version of PD4ML, and has been resolved by updating the version from 4.0.6 to 4.0.9fx1.

INC-144358 · Issue 601012

Localization added for "Automatically" and "Manually" field values

Resolved in Pega Version 8.5.2

The Dutch translation of "Child case [Case_type] [Case_id] has been [Instantiation_mode] instantiated" used the hard-coded English expression "manually". This has been resolved by adding the "Automatically" and "Manually" field values to localization.

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