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-143363 · Issue 604365

Added handling for maintaining on-change event descriptor

Resolved in Pega Version 8.4.4

The multiselect control was not reliably posting the values to the configured page list property if the change actions were performed very quickly. Multiselect calls triggerCustomEvents, which handles the schedule for an event: when change actions are entered in a paced way they are not added to a queue, but when performing on-change very fast events are added to a queue and processed later. In this case, the queuing caused the correct event descriptor to be lost because the original event flows were not followed. This has been resolved by adding custom handling which will maintain the event descriptor.

INC-146339 · Issue 600745

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

Resolved in Pega Version 8.4.4

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 612370

Enhanced socket timeout logging

Resolved in Pega Version 8.4.4

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 596470

Scheduled tasks landing page shows all tasks

Resolved in Pega Version 8.2.8

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-143191 · Issue 596467

Scheduled tasks landing page shows all tasks

Resolved in Pega Version 8.4.4

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-138317 · Issue 591179

PDF/A generation supported

Resolved in Pega Version 8.2.8

When calling the HTMLToPDF activity and passing the pyPDFGeneratePDFA=true parameter, the outcome was a plain PDF document. This has been resolved by updating the pd4ml jar to 3113 to support pdfa format.

INC-139054 · Issue 598151

PD4ML library updated

Resolved in Pega Version 8.4.4

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 601013

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

Resolved in Pega Version 8.2.8

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.

INC-144358 · Issue 601014

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

Resolved in Pega Version 8.4.4

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.

INC-137255 · Issue 584906

Resolved Cassandra query read/write latency

Resolved in Pega Version 8.2.8

Read/write latency was seen when certain Cassandra queries were triggered by the system. This was traced to an unusual case where a flush was not done for an exceptionally long time period, and has been resolved.

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