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-B95980 · Issue 343245

Fixed set focus timing issue

Resolved in Pega Version 8.1

Set focus was not working on tab keys after upgrade due to an event in the queue conflicting with the set focus event, and has been fixed by adding a conditional setTimeout for tabkey.

SR-B96528 · Issue 378824

Failed service requestors return status along with error message

Resolved in Pega Version 8.1

Queue items related Service requesters were going to broken status with a "Database rollback caused queue item rollback" exception. Investigation showed BatchRequestorTask was not returning error messages in case of failure on a service activity, but rather displayed a generic error message in all error scenarios. This has been fixed by modifying ProcessServiceRequestMethod to return the status of a service activity along with an error message in cases of queue process failure.

SR-B96842 · Issue 355769

JAWS reads collapsible header title sourced by JSP

Resolved in Pega Version 8.1

JAWS was not reading expanded/collapsed headers properly if the title was sourced by a JSP property reference. This has been corrected.

SR-B96909 · Issue 357163

Enhanced features for SecureAll settings

Resolved in Pega Version 8.1

Previously, the option existed to support secureAll (i.e. securing all streams and activities) or to list the streams or activities which needed to be secured against CSRF attack. An enhancement has now been added to support the list of allowed activities or streams for which CSRF attack is skipped so that secureAll can be set to True with a provided exemption list of activities or streams. 1) A new DSS setting security/csrf/AllowSameDomainReferrer which allows either True or False has been added. 2) When DSS security/csrf/AllowSameDomainReferrer is set True then the current behavior is retained, i.e. if the referrer is in the allowed referrer list or the request is from same domain of the Pega app then the request is considered as valid even if the token validation fails. 3) When DSS security/csrf/AllowSameDomainReferrer is set False and if the token validation fails. it will be considered a CSRF attack. If the token validation passes then that success is returned. 4) New DSS settings security/csrf/allowedActivities and security/csrf/allowedStreams have been introduced to take the list of activities and streams for which CSRF validation is skipped when security/csrf/secureall is set True. 5) The new DSS settings security/csrf/allowedActivities and security/csrf/allowedStreams will take precedence over the existing DSS settings security/csrf/securedActivities and security/csrf/securedStreams

SR-C10058 · Issue 352947

Validation error persists for focus out

Resolved in Pega Version 8.1

The Field Validation Error massage was lost when the error field was clicked and then any other area was clicked. This has been fixed.

SR-C10071 · Issue 354506

SignatureMethod Algorithm attribute in Authentication Activity now obtained from certificate

Resolved in Pega Version 8.1

When creating an authentication request in pySAMLWebSSOAuthenticationActivity (step 6), the system was generating the wrong SignatureMethod Algorithm if the site was using certificates with RSA - SHA256 encryption. This was due to the signature algorithms being hardcoded in SAML code, and has been resolved by getting the signature algorithm from the certificate.

SR-C10215 · Issue 356670

Invalid editable field correctly hidden

Resolved in Pega Version 8.1

When a 508 Accessibility user logged in to any harness, an editable field was added after the main layout and sections. This was shown visually with the web accessibility toolbar, and accessibility users were able to navigate to this field via Tab navigation. This field was added intentionally to address an issue, but recent updates to the accessibility tools made it visible. The code has now been updated to correctly hide it.

SR-C10216 · Issue 359979

Removed extraneous tabIndex in Microsoft Internet Explorer

Resolved in Pega Version 8.1

An extra tabIndex on <th> in Microsoft Internet Explorer which was not required and causing additional issues has been removed.

SR-C10229 · Issue 360442

pxAssignDateTime updated during GetNextWork

Resolved in Pega Version 8.1

The property pxAssignDateTime of an assignment was not getting updated using GetNextWork to fetch a case from the workbasket and assign it to a worklist. This has been corrected.

SR-C10270 · Issue 355775

Added client side validation for manually entered date

Resolved in Pega Version 8.1

In a Date Time control defined on date type property, if the date was entered in yyyy/MM/dd format manually, a client validation error was thrown on the screen stating the format was invalid. Clicking on the submit button even after this the client side validation error submitted the form. This did not happen if the property type was Date Time. To correct this, code changes have been made to get the client side validation for an invalid date format.

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