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-C91501 · Issue 428972

Support added for base64Binary type in the SOAP envelope

Resolved in Pega Version 8.3

In order to support the sending of files more than 10 MB in size as a SOAP attachment, a condition has been added to populate base64Binary type as a multipart message in the SOAP envelope. This allows a text node with binary content to be optimized for xop/MTOM.

SR-C59014 · Issue 429039

Inline error messages linked to input for accessibility

Resolved in Pega Version 8.3

In order to support accessibility for server side inline messages, the controls have been mapped to the error message div and an aria-describedby attribute has been added for the same. This allows JAWS to read the error message specific to the control where the error occurs.

SR-C86972 · Issue 429208

Resolved error in editing flow rule assignment shapes

Resolved in Pega Version 8.3

The submit of an assignment properties modal window was not closing the modal, and instead opened a new window with an error page indicating a NullPointerException. This happened whether or not there were changes made to the assignment properties, and occurred for the assignment shapes on any flow. This was traced to a UI limitation in the backward compatibility of the "parent.parent.pyWorkClass" property which caused the property reference to not be resolved for hidden controls in client side template. To correct this, updates have been made to "pzAssignmentTab" (in Data-MO-Activity-Assignment class ) and "pzPropertyPanel" (in Data-MO-Activity-Assignment-WorkAction class).

SR-C92082 · Issue 429438

Corrected ADP sections rendering twice

Resolved in Pega Version 8.3

ADP sections were being rendered twice due to the inclusion of lazyloadinfo in pzModalAction which loaded multiple divs during the initial expand onload configuration of expand pane. This has been corrected.

SR-C89156 · Issue 429485

Blank paramter passed as inshandle invokes NoWorkID harness instead of exception

Resolved in Pega Version 8.3

In releases prior to 8.1, the Obj-Open-By-Handle method was used to set an ActivityStepStatus error if a blank parameter was passed as inshandle. The activity step 8 would show as failed and invoke the NoWorkID harness. As of Pega 8.1, the code was refactored and modified to throw an InvalidArgumentException and quit the activity. In order to ensure better backwards compatibility, the error handling has been reset to show the NoWorkID harness when instanceHandle is empty.

SR-C92020 · Issue 429568

Export of report definition does not open a new tab

Resolved in Pega Version 8.3

When a report definition was exported to PDF or Excel, a new tab was generated in Safari which was not closed even after download. This has been corrected.

SR-C89619 · Issue 429573

Custom section filters retained during refresh

Resolved in Pega Version 8.3

Filtered values were not retained on refresh when filtered using a custom section. This has been resolved.

SR-C91370 · Issue 429578

System updated to jackson-databind-2.9.8.jar

Resolved in Pega Version 8.3

The jackson-databind jar has been upgraded to v2.9.8.

SR-C90467 · Issue 429607

Validations are correctly run on rescheduled reports

Resolved in Pega Version 8.3

When using the out-of-the-box schedule report functionality, UI validations were bypassed if the existing schedule was deleted and the report was rescheduled. This has been corrected by updating the Review harness to display the Perform harness when clicking Update.

SR-C91750 · Issue 429615

Summarized report after editing shows Count as expected

Resolved in Pega Version 8.3

When creating a report with a number of fields and summarizing it in the report browser, the summary gave proper counts. However, after clicking on "edit report" and then running summarize on the same column, the generated report gave the Sum of the number column instead of the Count. To resolve this, the implementation used to update a hidden value for the dropdown has been set to initialize to the Count option.

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