INC-193289 · Issue 679210
Security updated for @baseclass
Resolved in Pega Version 8.7
After update, searching for a baseclass 'when' rule returned no results. Listing the rules under baseclass in App Explorer resulted in the error "Applies To: The Class with key value(s) %40baseclass does not exist". This was an unintended side effect of security updates, and has been resolved by creating an exception path for "@baseclass".
INC-175394 · Issue 661455
Date Time format corrected for Chinese locale
Resolved in Pega Version 8.7
The DateTime input field displayed the error message "not a valid date/time value" for the Chinese locale when the time zone source configuration was set as "CET". This has been resolved by setting the moment object's locale to the operator locale while converting the date time values to the operator time zone.
INC-133173 · Issue 573441
Landing page refresh modified to avoid frequent reloads
Resolved in Pega Version 8.1.9
Approximately every two weeks, clients were able to login but it was not possible to work as the landing page refreshed constantly until all of the nodes were rebooted and the issue was cleared. Investigation indicated the frequent reloads were related to the cacheing of the operator details, and this has been resolved by updating the datapage reload strategy based on 'when' so frequent reloads will be avoided.
INC-120326 · Issue 564437
Landing page refresh modified to avoid frequent reloads
Resolved in Pega Version 8.1.9
Approximately every two weeks, clients were able to login but it was not possible to work as the landing page refreshed constantly until all of the nodes were rebooted and the issue was cleared. Investigation indicated the frequent reloads were related to the cacheing of the operator details, and this has been resolved by updating the datapage reload strategy based on 'when' so frequent reloads will be avoided.
INC-140111 · Issue 594375
CSRF token handling added to Bulk Processing
Resolved in Pega Version 8.5.2
On click of submit button from the bulk transfer screen, the pzbulkprocess harness was loaded and the portal was automatically logged off. Investigation showed that when CSRF was enabled, loading pzBulkProcess failed with a 403 error that resulted in logging off the current session due to a missing fingerprint token. This has been resolved by adding both CSRF token and fingerprint generation logic to pzBulkProcessingList.
INC-150407 · Issue 605840
Validation error messages correctly cleared in nested markup
Resolved in Pega Version 8.5.2
A UI Freeze issue was seen whenever mandatory input was missed and the form was submitted. Continuing was possible after browser refresh, but a new Next>> button appeared. This was an unintended side effect of work done to correctly clear validation messages when areas had captions, and has been resolved by modifying that work so it performs as expected on nested markup.
SR-C15346 · Issue 357008
Label error CSS appended to drop down field
Resolved in Pega Version 8.1
When configuring a Repeat Grid layout with inline always editable mode and a section include containing drop down fields associated with required input fields like DateTime and Text Input fields, exiting out of the drop down did not append the input field label to the CSS class as expected. This was due to incomplete generation of the repeatindex for the ID, and has been fixed.
INC-181389 · Issue 668678
Unused class reference removed from CaseActionArea
Resolved in Pega Version 8.7
The rule Work-.pyCaseActionArea in Theme-Cosmos was logging error messages related to "clipboard.InvalidParameterException: Class not defined in dictionary: PegaMKT-Work" when opened in Dev Studio. This was traced to a reference to the section "pyCaseActionArea" which was not present by default in PegaMKT-Work, and has been resolved by recreating the section "pyCaseActionArea" to remove the unused class reference.
SR-D92590 · Issue 553059
PostgreSQL information updated in Platform Support Guide
Resolved in Pega Version 8.5.2
The Platform Support Guide has been updated to reflect the following:Postgresql-42.2.14.jar supports PostgreSQL 8.2 or newer, and requires Java 6 or newer (Pega only supports Java 8 and 11); this driver also contains support for SSL and the javax.sql package. Prior versions of this .jar file have known problems. Do not use these versions: • 42.2.11 – creates an exception which stops Pega Platform startup • 42.2.12 and 42.2.13 – known vulnerability issues (CVEs) reported
SR-C25202 · Issue 365395
Fixed offline sync flow processing corruption
Resolved in Pega Version 8.1
In offline sync, only differences are sent from the device to the server for each action. The server-based sync service merges the differences onto the full work object read from the database. In some cases, data with blank values in the received different JSON was not replacing existing values in the workpage, causing corrupted flow processing and completed cases being returned to the application inactive queue. This was traced to a missed use case for pxObjClass while sending data from client to server, and has been resolved.