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.

SR-A100558 · Issue 271513

Oversized file null-pointer exception resolved

Resolved in Pega Version 7.3

A 413 exception was being generated by uploading files with a size greater than the Initialization/MaxFileUploadSize DSS value. The controls have been modified with a check to restrict properly restrict file size during this process.

SR-A100558 · Issue 274795

Oversized file null-pointer exception resolved

Resolved in Pega Version 7.3

A 413 exception was being generated by uploading files with a size greater than the Initialization/MaxFileUploadSize DSS value. The controls have been modified with a check to restrict properly restrict file size during this process.

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-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-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-A92512 · Issue 270130

WebLogic tool generation updated for complexType schema

Resolved in Pega Version 7.3

A red X error was seen for PRAsync MDB modules on the Resource Dependencies screen in the WebLogic console in deployments with WebLogic 11i or 12c. This was due to the EJB component (prbeans.jar) not being implemented to support complexType schema, and has been resolved by updating the Pega Platform WebLogic components to support complexType schema in the WebLogic tool generation.

SR-B10345 · Issue 281585

Command line jar import handling improved

Resolved in Pega Version 7.3

When installing Smart Dispute and related strategic applications, exceptions occurred when generating a DDL via prpcUtils (e.g. prpcUtils.bat generateDDL) if any of the files listed in schema.archive.input did not contain schema changes or did not have a delta. This has been resolved by updating the system to better handle files that do not require a DDL to be generated.

SR-B10347 · Issue 279670

Attachment icons display correct type

Resolved in Pega Version 7.3

The attachment icon was not reflecting the attachment type. This was caused by an error in the pzWorkAttachmentIcon control which caused the File name to be passed as empty, resulting in a failure to fetch the correct image name. This has been fixed.

SR-B10406 · Issue 279344

Custom operator images work in IE

Resolved in Pega Version 7.3

Custom operator images (using pxOperatorImage control) were not properly displayed in the Internet Explorer browser. This was traced to a malformed URL generated by the pxOperatorImage control, and has been fixed.

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