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.

SR-D5904 · Issue 490489

Discard changes dialog now showing for local actions

Resolved in Pega Version 8.1.7

After having modified case data without saving and clicking on a menu entry (left menu, search, ...), the system shows a dialog box to ask the user to confirm it is ok to discard changes. However, this confirmation dialog did not work with local actions, leading users to lose their work without any warning nor any way to step back. This was traced to a difference in the dirty form check, which was not present when launching a local action from a case. An enhancement has now been added to the handleMenuAction js function in pypega_ui_harnessactions.js which will perform a dirty form check with a prompt.

SR-D23723 · Issue 503090

pxGenerateExcelFile updated for handling blank dates

Resolved in Pega Version 8.1.7

When using a custom template for exporting to Excel, blank DateTime property column values defaulted to the current date. To resolve this, the pxGenerateExcelFile activity has been updated to ensure that an empty date will be exported as blank and that given dates will appear in the correct datetime format.

SR-D24950 · Issue 494566

Added explicit step page to resolve null-pointer exception with custom error message

Resolved in Pega Version 8.1.7

A null pointer exception was generated during case run time harness refresh after a custom error message was inserted. This was traced to a blank step page related to the custom message, and has been resolved by adding a primary step page at step 10 of the New(Work-) activity to prevent the null-pointer exception on harness reload.

SR-D42679 · Issue 509565

oLog.infoForced has been replaced with oLog.debug in GetAssignmentDetailsInternal to reduce excessive logging

Resolved in Pega Version 8.1.7

The Rest API used by Robotics was generating excessive logging on the application server due toPzGetAssignmentDetailsInternal generating several lines of logs with each REST call. In a high volume system, this can make the logs difficult to utilize. To resolve this, oLog.infoForced has been replaced with oLog.debug.

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-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-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.

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