INC-151401 · Issue 615716
Context set for progressive scroll load of dynamic layout
Resolved in Pega Version 8.4.4
When setting pagination as 'Progressively load on scroll' for a repeating dynamic layout in a section with pagelist as the source, scrolling resulted in a null pointer exception and no further scrolling was possible. The issue was not seen when 'Progressively scroll on user action' was used. Investigation showed the activity Reload Section was failing because of the failure in the pre-processing activity, and this has been resolved by setting the correct context before making the pagination call.
SR-C68993 · Issue 416162
Expression exngine correctly evaluates boolean type property with expression
Resolved in Pega Version 8.3
Expression exngine correctly evaluates boolean type property with expression When using a dynamic layout with a visibility condition expression and 'Run Visibility Condition on client' checked, a condition such as .VehicleDetails != '' && .VehicleDetails = true was not being evaluated as expected after upgrade. This issue was related to changes made to the expression engine to get the initial evaluation result at the server side, and was caused by a missed use case for a boolean type property with expression. This has been corrected.
INC-143121 · Issue 610734
Timeout for loading predictors made configurable
Resolved in Pega Version 8.4.4
When using an extremely large number of predictors, the Report definition pzADMPredictorsFilter was suffering timeouts due to the time for loading predictors from the database exceeding the time threshold allowed. This has been resolved by marking the rule as editable to allow custom setting of the threshold according to need.
INC-147166 · Issue 601801
AvailableProperties cleanup added after save
Resolved in Pega Version 8.4.4
The Report filter value auto-complete was displaying an incorrect list of values. This was traced to pyAvailableProperties not being cleaned up after being created and used in a prior process, and has been resolved by ensuring pyAvailableProperties is removed on save so it can be cleanly built when needed.
INC-150188 · Issue 613653
Dirty dialog flag reset added for custom modals
Resolved in Pega Version 8.4.4
When a discard button in a custom Cosmos modal dirty dialog was clicked, pega.u.d.isDirtyDialogOpen was not reset to false. This caused the modal dialog to not be shown the next time. This has been resolved by modifying pzpega_ui_doc_dirtyhandling to support this dirty handling discard use case.
SR-D9922 · Issue 481416
Case Notes view has proper line wrapping in Google Chrome
Resolved in Pega Version 8.3
When case notes were opened in the Google Chrome browser, the view did not wrap. This was traced to a style attribute for white space which caused the line breaks to be collapsed in Google Chrome, and has been resolved by modifying the DisplayNote HTML to handle the wrap use case.
SR-D6695 · Issue 482516
Predictive model now handles database oeprations progress states
Resolved in Pega Version 8.3
When attempting to create a predictive model, the page was hanging and would not process. Investigation indicated that this was a result of a missing use case from recent changes made to the progress bar logic for termination conditions, and has been resolved by adding handling for database operations progress states.
INC-145119 · Issue 601713
Client side validation works with Reference page property
Resolved in Pega Version 8.4.4
A reference page property in a 'when' rule was not evaluating properly for checking a Date field when client side validation or Client side template UI was checked on the Harness level. This was traced to pyRequired being boolean: the boolean being compared to a string false value yielded a wrong comparison, leading to the wrong validation type required. To resolve this, the system will use the === comparator to compare boolean false in datetime to remove the required validator.
INC-147140 · Issue 604371
Email listener update for Microsoft Exchange server
Resolved in Pega Version 8.4.4
After upgrade, TooManyObjectsOpenedException/MapiExceptionSessionLimit errors were seen when starting the email listener. Investigation showed that when the listener was started, two sessions were getting opened and then not closed properly. This was a method originally intended to allow the system to re-use the session to minimize performance overhead, but it is not well-suited for use with Microsoft exchange server as the Exchange server is unable to cleanup idle sessions. As a result, too many MAPI sessions were opened and led to an authentication exception while opening additional sessions. To resolve this, an update has been made so the system will close the session while the listener sleeps. This stop, restart and graceful shutdown scenario for single threaded email listener scenarios will create a new session every time and close it properly.
INC-144864 · Issue 599147
Unneeded AUC error percentage calculation removed for better system performance
Resolved in Pega Version 8.4.4
When generating snapshots of the ADM models, an inefficiency in the metric calculation for the AUC error percentage caused an excessive amount of memory to be allocated which could cause slowdown or require a system reboot. This has been resolved by removing the problematic AUC error percentage calculation as it is not used in the UI.