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.
INC-177206 · Issue 655631
Date Time control accepts custom length
Resolved in Pega Version 8.4.5
The date time control was ignoring custom length and expanding the field to the layout width. This was an inadvertent side effect of work done around the visibility of the date picker icon for non-templated layouts, and has been resolved by ensuring the date picker will render with a custom width configured in design time.
INC-159836 · Issue 631206
Upgraded Apache UIMA Ruta libraries to resolve memory leak
Resolved in Pega Version 8.6.2
A memory leak issue that resulted in a reboot being needed every few days was traced to the class org.apache.uima.ruta.rule.RuleMatch. This has been resolved by upgrading the Apache UIMA Ruta libraries to v2.8.1.
INC-167606 · Issue 665869
Updated ConfirmHarness handling for case type creation
Resolved in Pega Version 8.6.2
If a new case type was created with the initialization stage and there were no assignments in the case type, the /cases API did not return a NextPageID in response. This has been resolved by setting the pyConfirmHarness parameter before calling addworkobject.
INC-168368 · Issue 651079
Correct flow actions loaded in multi-thread portal refresh
Resolved in Pega Version 8.6.2
The member authentication screen was displaying an incorrect flow action on doing browser refresh after creating a new interaction. Refresh is a special case where the parameter retention is different across single-threaded & multi-threaded portals alongside the execution order of activities. In this case, this inconsistency occurred in a multi-threaded portal when newAssignPage had the information to load the proper assignment but the parameter indicated an old index. This has been resolved by adding 'when' conditions to to populate and pass the correct references and labels and to honor the Param.TaskIndex set and sent by UI activities so it's retained in case of multi-thread portals.