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-C86952 · Issue 428816

Viewing screen capture attchments no longer requires Microsoft Internet Explorer/Silverlight

Resolved in Pega Version 8.3

Previous versions of the Pega Platform required the use of the Microsoft Internet Explorer browser with Silverlight to access old attachments added using the screen capture feature. In order to support multibrowser compatibility, the system has been updated to use javascript functions to display these images so IE/Silverlight are not required.

SR-C74784 · Issue 428819

Added file truncation to HCClient.txt to ensure data integrity

Resolved in Pega Version 8.3

When a work object model contained more than two embedded lists, simple save corrupted the JSON in the local storage work object browser. Investigation traced the issue to using the same file without truncating its content. Because the HCClient.txt file in Rule: webwb - pzpega_mobile_settings - js was reused while displaying items in DocumentViewer, writing a smaller amount of data into it than the previous write left orphaned content in the file that corrupted the new data. To resolve this, the file content will be truncated before writing new data into it.

SR-C81077 · Issue 428868

Support added for using OpenMobile app as a Navigation action

Resolved in Pega Version 8.3

After adding a menu item to the pyCaseWorkerNavigation navigation rule that was configured to use the open mobile app action with a mobile app ID of opensignal, the menu item was displayed in the mobile app but clicking on it did nothing for the user and the JavaScript console logged the error "Cannot open mobile app without scheme". The same action worked as expected when called from a button. This was traced to the "OpenMobileApp" action not containing support for being used as Navigation action, and the necessary code for that use has now been added.

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.

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