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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-A103203 · Issue 276928

SQL alias function getLastDayofYear repaired

Resolved in Pega Version 7.3

After upgrade, the SQL alias function getLastDayofYear generated an error. This was due to missing format conversion for the date value parameter, and has been corrected.

SR-A21111 · Issue 268559

Performance improvements for embedded page reference checks

Resolved in Pega Version 7.3

Significant performance differences were seen between opening custom rules in the developer portal and opening the same rules in an embedded page. This was traced to each embedded page in the stream checking to see if reference properties are present. To resolve this, DirectStream has been modified to cache the value of containsAnyReferenceProperties if it has already been checked so that it is not repeatedly checked when it is not necessary.

SR-A23571 · Issue 279027

ExtractSection data transform optimized

Resolved in Pega Version 7.3

The code in pzExtractSectionPostDT and pzExtractSectionPostActivity has been optimized to improve data transform processing time.

SR-A80436 · Issue 278157

Federated Case Management GetNextWork function resolved

Resolved in Pega Version 7.3

When an operator had Work Basket configured with Federated Case Management, the Get Next Work function generated an error. This was due to the GNW settings from the operator IDs of the 'remote' systems not being correctly respected, and has been resolved.

SR-A80436 · Issue 278967

Federated Case Management GetNextWork function resolved

Resolved in Pega Version 7.3

When an operator had Work Basket configured with Federated Case Management, the Get Next Work function generated an error. This was due to the GNW settings from the operator IDs of the 'remote' systems not being correctly respected, and has been resolved.

SR-A80436 · Issue 279629

Federated Case Management GetNextWork function resolved

Resolved in Pega Version 7.3

When an operator had Work Basket configured with Federated Case Management, the Get Next Work function generated an error. This was due to the GNW settings from the operator IDs of the 'remote' systems not being correctly respected, and has been resolved.

SR-A83892 · Issue 264462

CreateOperator parameter added to HaveAttachmentSpecificAccess RUF

Resolved in Pega Version 7.3

The HaveAttachmentSpecificAccess RUF has been updated to better handle custom 'when' rules for restricting the ability to delete an attachment. To support cases where only the operator who attached the file has permission to delete it, the pxCreateOperator parameter has been added to the attachment page for use in checking whether the creator of the attachment is the current user.

SR-A86522 · Issue 272062

Event Late triggers expanded

Resolved in Pega Version 7.3

If "Limit passed deadline events" was not set to any value and the enqueue item was still in defer-save and not committed to DB, 'Event Late' was not triggered. Code has been added to properly check and trigger the late notice based on this scenario.

SR-A86522 · Issue 272065

Event Late triggers expanded

Resolved in Pega Version 7.3

If "Limit passed deadline events" was not set to any value and the enqueue item was still in defer-save and not committed to DB, 'Event Late' was not triggered. Code has been added to properly check and trigger the late notice based on this scenario.

SR-A87830 · Issue 258083

PD4ML JAR updated

Resolved in Pega Version 7.3

Metadata dates in a PDF generated with PD4ML are expected to follow ISO 8601 format "YYYY-MM-DDThh:mm:ss+##:##", with "+##:##" being the time zone adjustment based on UTC, but when the time zone was given as UTC (or a time zone with zero adjustment), PD4ML was setting the date as "YYYY-MM-DDThh:mm:ssZ00:00". This consequently generated errors with various PDF/A tools. To resolve this, the PD4ml jar has been updated.

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