SR-C81857 · Issue 420240
Enhancement added to support dropdown with page list property
Resolved in Pega Version 8.1.3
To enable the use of a dropdown control with a property of type page list, an enhancement has been added to support a clipboard page for drop down and autocomplete.
SR-C81946 · Issue 418711
Maintenance function operator ID will not persist in the system
Resolved in Pega Version 8.1.3
After a hotfix maintenance activity, an audit revealed that an extra operator created for the purpose called CloudMaintenanceUser persisted in the system. The code has now been updated to bypass saving operator records marked with pzPersistOperator="false" on user initialization; the CloudMaintenanceUser will be created with this property set to false, and updating this operator will be skipped during unauthentication.
SR-C82244 · Issue 421174
Enhancement made to allow passing of URL in actionset via the DX API
Resolved in Pega Version 8.1.3
When using the action "Open URL in Window" and the option "Use Alternate Domain" to pass a URL that is in saved in a property, the name of the property was passed when using the DX API instead of the URL. To allow this use, an enhancement has been added to support storing a last submitted value and a reference so that an action set with a property reference can return a reference object with lastSavedValue and the reference name attached.
SR-C82408 · Issue 422328
Repaired instance insertion for REST connection invoked via Queue
Resolved in Pega Version 8.1.3
After upgrade, the REST connection invoked in an activity which in turn called OOTB ProcessQueue was not getting the response into the SYSTEM-QUEUE-EXECUTIONREQUEST-CONNECT-CREATEBOOKING instance. The right response was observed coming from other source systems in the logs, and the work object status also changing as expected. This has been resolved by exposing a DSS to revert to the old behavior of Response being present in the queueItem when a connector is queued for execution.
SR-C82480 · Issue 421488
Column Headers properly aligned after expand/collapse of Tree Grids
Resolved in Pega Version 8.1.3
When using a hierarchical table - tree grid with a configuration that included Width of content-Pixels(Fit Content), a Fixed (pixel) size grid, and Freeze Header, expanding and collapsing back the contents resulted in a misalignment of the column headers. The fixed header implementation makes use of multiple table layouts which have to kept in sync via javascript; this issue has been resolved by rewriting the fixed header implementation to call setHeadersWidth on expand/collapse of a treegrid row.
SR-C82530 · Issue 420609
Atmosphere XSS Vulnerability fixed
Resolved in Pega Version 8.1.3
Atmosphere has been updated to close a potential XSS vunerability.
SR-C83808 · Issue 421299
FIRST aggregate in bucketed window fixed
Resolved in Pega Version 8.1.3
FIRST aggregates were not giving the correct results if used in a Sliding Time window together with an average aggregate.This was traced to an incorrect implementation of FirstAggregatorHolder.substractAggregate which used propertyIndex to get aggregate value (which was not correct in this context), and has been fixed by using the correct index in FirstAggregatorHolder class.
SR-C83915 · Issue 421169
Enhancement added to support property reference name for section include
Resolved in Pega Version 8.1.3
When requesting the view of a section from a repeating dynamic layout where the name of the section is taken from a property, the DX API returned an error on the tracer indicating "Invalid value for aReference passed to com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.getString(String)". This has been resolved by adding an enhancement to support using a property reference for section include.
SR-C85035 · Issue 421948
Added getIfPresent check for Field Value parameters with pzAPICreateJsonForView
Resolved in Pega Version 8.1.3
Calling pzAPICreateJsonForView was altering case values if localized field value parameters were added. This has been corrected by performing a getIfPresent and getIfString on the property pyFieldValueParams so field value parameters will not be added to the main page if they're not present.
INC-227878 · Issue 727855
UPDATE IMPACT FOR PEGA CALL
Resolved in Pega Version 8.7.3
Log4j-1.2.14.jar and Log4j-1.2.17.jar have been removed to address the security concerns with these versions, and logger jars have been upgraded to 12.7.2 version (from 12.7.1 version) to make Pega Call compatible. This change will impact Pega Call customer environments due to Avaya or Genesys, which are part of Pega Call, having an internal dependency on Log4j1.x version jars. As a result, the SDK logging for Avaya or Genesys will not be available in the 8.7.3 release unless the Log4j-1.x jar files are reimported locally.