SR-A86896 · Issue 259811
Column filters appear on horizontal iPad
Resolved in Pega Version 7.2.2
When a grid was configured with enough columns to require a horizontal scroll bar, scrolling to the right and trying to filter on the right side columns did not show the filter popup on an iPad in Horizontal orientation. The expected behavior is that the popup would appear near the column the user filtered. This was seen in iPad Safari due to hardware acceleration, and has been corrected with the inclusion of a CSS rule and the popover JS to trigger reflow for popover loader.
INC-148853 · Issue 609318
Corrected password comparison handling for CopyMerge Ruleset Wizard
Resolved in Pega Version 8.4.4
When running the CopyMerge Ruleset Wizard, entering the password failed with the error "pyPassword: Invalid Password for" <Temp:01-01-01> for each ruleset. Investigation showed that the system was calling an activity which encrypted the user input, causing the comparison with the stored password of the system to fail the match. This has been resolved by removing the extra encryption so the call to the comparison evaluates correctly.
INC-217159 · Issue 721071
German locale preserves semicolon as CSV separator
Resolved in Pega Version 8.8
When manually importing CSV files in the German locale which has special characters, special date format and the semicolon as a separator, the staging environment worked as usual and separated the imported records, but attempting to import the same CSV file to the staging clone did not split the records into the separated fields. This was traced to the pzGetLocaleListSeparator decision table returning a comma for the separator instead of semicolon for the de_DE locale, and has been corrected.
SR-A102018 · Issue 270086
Creating REST integration works from JSON file
Resolved in Pega Version 7.2.2
Creating REST integration from JSON file was failing due to the same name attribute 'agent' in the JSON having different modes - page and string. Code to perform a rename in case of conflicts was already present, but in the given case (JSON file) properties were created in descending order but saved in ascending order and the error occurred. To resolve this issue, the conflicting properties will be renamed when created such that the order of creation does not affect the creation of the properties.
SR-A91238 · Issue 259751
Radio button clicks improved for groups in repeat grids
Resolved in Pega Version 7.2.2
Clicking on radio button labels in a repeat grid layout resulted in a selection from the first row while clicking exactly on a radio button icon worked as expected. This was due to the IDs generated for radio buttons not being unique when a section has a radio group and that section is included inside a repeat grid. To fix this, radio button generation has been changed to generate unique IDs for the radio buttons and corresponding labels.
INC-143908 · Issue 606551
Data Page Save correct in batch mode
Resolved in Pega Version 8.4.4
After configuring a List type savable Data Page with save activity in Code-Pega-List, the save data page was triggered from utility of flow from the queue processor to handle queueing 10k data items and creating 10k work objects. When this was run, a field dpClassName was being changed by different threads in DataPageSaverImpl.java. This has been resolved by making the class DataPageSaverImpl.java stateless to ensure thread safety.
INC-145756 · Issue 619293
Logging for MultiNodeSynchronize lock attempts changed from error to warn
Resolved in Pega Version 8.4.4
The File Listener was logging numerous errors stating "Unable to establish MultiNodeSynchronize lock while trying to determine if listener is enabled for this node". Handling has been previously established for error cases when the Listener is unable to establish a MultiNodeSynchronize lock, but this condition continued to be logged as an error even though it was not related to any failures in functionality. To resolve the logging issue, the logger level has been changed from ERROR to WARN.
INC-149370 · Issue 619990
Logging for MultiNodeSynchronize lock attempts changed from error to warn
Resolved in Pega Version 8.4.4
The File Listener was logging numerous errors stating "Unable to establish MultiNodeSynchronize lock while trying to determine if listener is enabled for this node". Handling has been previously established for error cases when the Listener is unable to establish a MultiNodeSynchronize lock, but this condition continued to be logged as an error even though it was not related to any failures in functionality. To resolve the logging issue, the logger level has been changed from ERROR to WARN.
INC-150809 · Issue 611855
Loading timing updated for openAPI content
Resolved in Pega Version 8.4.4
Open API content loading was taking too much time and interfering with working on other REST rule configurations. To resolve this, the loading of openAPI contents has been removed from the opening or saving of REST rule and shifted to lazy loading. Clicking on the openAPI tab will load the contents, and any modification in REST rule or service package rule will update the contents of openAPI when "Action->Refresh" is clicked.
INC-215354 · Issue 712666
Data- flow actions working in Bulk Process
Resolved in Pega Version 8.8
When trying to render a flow action whose 'applies to' class was inherited from Data-, an error was generated indicating that the flow action could not be found. This was traced to non Work- flow actions not being correctly populated, and was an inadvertent side effect of work done to set class for inheritance if Work- is not present. This has been resolved by updating the pzPreBulkProcessModal activity to set the TempWorkPage class to Work- only if .pyActionName is pyTransferAssignment.