INC-143363 · Issue 604363
Added handling for maintaining on-change event descriptor
Resolved in Pega Version 8.5.3
The multiselect control was not reliably posting the values to the configured page list property if the change actions were performed very quickly. Multiselect calls triggerCustomEvents, which handles the schedule for an event: when change actions are entered in a paced way they are not added to a queue, but when performing on-change very fast events are added to a queue and processed later. In this case, the queuing caused the correct event descriptor to be lost because the original event flows were not followed. This has been resolved by adding custom handling which will maintain the event descriptor.
INC-146339 · Issue 600744
ViewID parameter passed as part of DX API response payload for level 5 applications
Resolved in Pega Version 8.5.2
Recent work to not consider production level and always pass 'viewID' parameter as part of DX API response payload was not working for cases where the APIProductionLevel was 5. This was a missed use case based on a condition that remained on the ViewID parameter, and the condition has now been removed.
INC-153877 · Issue 612371
Enhanced socket timeout logging
Resolved in Pega Version 8.5.3
In order to assist with diagnosing issues with socket timeouts such as a Data Flow Daily Run failing, logging to print the SocketTimeout value has been added when case info is enabled.
INC-143191 · Issue 596469
Scheduled tasks landing page shows all tasks
Resolved in Pega Version 8.5.2
Due to pzGetScheduledTasks listview having a hardcoded limitation of 500 records to be fetched, not all scheduled tasks were being shown in the scheduled tasks landing page. This has been resolved by modifying the pyCreateSummary activity to use a newly created Report Definition to fetch data instead of list view.
INC-140848 · Issue 596461
Button row correctly added for click on exception list
Resolved in Pega Version 8.5.2
After upgrade, clicking on an exception list button in the mobile app was not adding a row to an existing PageList as expected. Investigation showed that pega.u.d.refreshSection was not executing correctly from RunScript, which was traced to a missed use case for handling an empty repeating dynamic layer in this scenario. This has been corrected.
INC-156094 · Issue 621064
Access control updated for non-auto-generated finishAssignment
Resolved in Pega Version 8.5.3
After upgrade, a flow containing a flow action that called an out of the box HTML rule was triggering a SECU0019 alert and blocking functionality. This was a missed use case for BAC where all non-auto generated rule actions should be registered, and has been resolved by registering finishAssignment.
SR-113149 · Issue 168421
Ensured tabbed section refresh for new sessions
Resolved in Pega Version 7.1.7
When a new session had only 2 tab groups configured with dynamic container, the first tabbed section refresh was not working as expected. This was caused by a missing null check, and has been corrected.
INC-139054 · Issue 598153
PD4ML library updated
Resolved in Pega Version 8.5.2
When generating a PDF, lines were broken up for the content boxes. This was an issue with the included version of PD4ML, and has been resolved by updating the version from 4.0.6 to 4.0.9fx1.
SR-115719 · Issue 165692
WebSphere WorkManager pool setting correction
Resolved in Pega Version 7.1.7
Due to a coding defect, the WorkManager thread pool setting configured through WebSphere was not being utilized. As a consequence, a large number of daemon threads could be created during certain scenarios and the ability to make connections could be reduced. This has been fixed, and the system will now use the WebSphere WorkManager setting.
SR-117573 · Issue 171739
Fixed disappearing menu in modal dialog for IE11
Resolved in Pega Version 7.1.7
After launching a local action in a modal dialog from a Navigation rule while using IE11, dismissing the local action caused the navigation rule to disappear until the browser was manually refreshed. This was caused by a routing issue with the menubar call that failed to correctly reload the menu, and has been corrected.