INC-168695 · Issue 643014
String conversion logic updated for toFixed function
Resolved in Pega Version 8.4.5
The toFixed function of pzpega_ui_formatNumber.js was incorrectly converting a string while formatting the value. This potentially caused the UI to hang until manually refreshed. To resolve this, the logic has been updated to convert the string to a number before calling toFixed().
INC-169866 · Issue 653550
View content type updated to FIELD
Resolved in Pega Version 8.4.5
After upgrade table grids were not visible in the UI for some operators while other operators with the same access group were able to see the same table with the result rows. Investigation showed that the personalized view stored in 8.1.x did not have a content type set, causing all of the columns to be hidden after upgrade to 8.4+ due to the personal view not matching with the design time view. To resolve this, the content type has been updated to FIELD for views.
INC-171352 · Issue 653693
Focus set correctly on the modal window in theme-Cosmos
Resolved in Pega Version 8.4.5
in theme-Cosmos with touch enabled, clicking on a button to open a modal window set the focus on the background instead of in the modal window, forcing tabbing through the full page to reach the modal window. This was traced to the templates not using the pzModalCancel control which has the necessary container_close for the modal dialog close icon, and has been resolved by adding a check to set the focus correctly.
INC-171449 · Issue 649931
Added null check for expression ID in Disable-When-Condition
Resolved in Pega Version 8.4.5
A Radio Button was not disabled despite a 'when' rule if a Data Page was used as the List source in the Radio buttons control and the property was passed as a parameter of the data page. Investigation showed that the expression ID for the Disable-When-Condition was present, but there were no expressions to evaluate. This has been resolved by adding a null check to verify if expressionResults is an empty object.
INC-172178 · Issue 655023
TransID updated to trim spaces
Resolved in Pega Version 8.4.5
While preparing newTransID from a response, special characters slipped into "newTransID" param value and generated an error. This has been resolved by updating the system to trim spaces from newTransID.
INC-173345 · Issue 655040
Check added for empty geolocation values
Resolved in Pega Version 8.4.5
Latency issues were traced to Geolocation-related errors in the log files. To improve performance, changes have been added to check for empty pyLatitude and pyLongitude before adding in the postdata of an async request.
INC-174020 · Issue 650890
Performance improved for Directed Web Access (DWA)
Resolved in Pega Version 8.4.5
Slowness when using a Directed Web Access (DWA) link has been resolved by refining the code of the PZPEGA_UI_DOC_EVENTSCONDITIONSCHAINING script to improve performance.
INC-175990 · Issue 652087
Browser check added to ensure on-click event trigger
Resolved in Pega Version 8.4.5
Clicking Submit from the screen after opening the case from the worklist did not trigger the click event action when using Microsoft Internet Explorer 11. This was due to a change in that browser, and has been resolved by adding a check.
INC-176734 · Issue 655179
Invalid manual time value stops progress and displays error
Resolved in Pega Version 8.4.5
When an invalid time was manually entered, eg. 11, the system previously remained in an error state until the time was corrected. Post-update, the current time of the user's session / browser was populated into the time field when an invalid time was entered. Although the error still displayed, the current time was saved and the user could continue. This has been resolved by adding a condition to show the entered time value and not continue if the entered time value is invalid.
INC-176971 · Issue 655218
Web Mashup works from nested iframe
Resolved in Pega Version 8.4.5
Web Mashup was failing with the error "Browser cookies must be enabled for PRPC Internet Application Composer to function" when it was configured within a nested iframe setup. This has been resolved by adding a cookie check and the appropriate handling for this usecase.