SR-B94230 · Issue 342360
Defer loaded UI in review harness checks for parent editability status
Resolved in Pega Version 8.1
When a layout was defer loaded, it appeared as editable in the review harness instead of read only as expected. This was caused by Dynamic layouts not honoring the readonly parent status from the section level when using defer loading, and has been fixed by adding a check for the parent status.
SR-B94928 · Issue 362772
Reworked conflicting timeouts for PRThread
Resolved in Pega Version 8.1
If a PRThread was activated when a Requestor was in TIMED_OUT state, then pages like Application, Accessgroup and properties like pxPortal were cleared from the PRThread and never restored even after re-authentication of the requestor. This happened when the authentication timeout value specified in the access group was less than the passivation_timeout for the requestor, and has been fixed.
SR-B94951 · Issue 343587
Section assembly escapes quotes
Resolved in Pega Version 8.1
Quote marks were being removed from an action string with a value containing a quote during section assembly. To correct this, the quote character will be escaped rather than removed.
SR-B95671 · Issue 357201
DST issues fixed for RD chart date/time labels
Resolved in Pega Version 8.1
Date and Time labels on a Report Definition chart axis displayed incorrectly for operators in certain time zones when the Date property was configured as "Date" or "Time" only rather than "DateTime". To correct this, the Fusion Chart data generation has been modified to change the parseDate() and formatDate() to use GMT for Date and TimeOfDay properties instead of the server's time zone, and to change normalizeDateCal() and createDateTimeCategories() to set time zone to GMT for Date and TimeOfDay properties. DateTime properties will not be affected.
SR-B95713 · Issue 354215
Added default value for AssociationClass
Resolved in Pega Version 8.1
pxGetAssociations was failing if no value was provided for AssociationClass param. To address this, the default value for this will be set to Link-Association in the @baseclass pxGetAssociations activity in Pega-ProcessEngine rule set > step 2 property set.
SR-B95820 · Issue 355562
Added ignorecase to filter pxAssignedOperatorID
Resolved in Pega Version 8.1
SOAP service GetPMFAssignments622 was not returning tasks when the operator ID had uppercase characters; this has been fixed by modifying the list view GetPMFWorklist to have Ignorecase selected for filter pxAssignedOperatorID.
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