SR-B11927 · Issue 280995
pyContentType column populated in recents table
Resolved in Pega Version 7.3
After upgrade, the new column "pyContentType" was visible in the pr_data_recents table, but data was not getting populated into this column when work objects or rules were opened. This was due to the recents tab missing the pyContentType column query from the custom population queries, and this has now been added.
SR-B9916 · Issue 283675
Hyperlink works on custom HC login page
Resolved in Pega Version 7.3
In a Hybrid Client App with a custom login page, a simple HTML link which calls the function to load the mashup code for the gadget worked in the browser but not in the HC. This was caused by window.open not working inside HC. To enable this, the _launchPopup api of compositegadgetmgr.js has been modified to use launchbox.Browser.start instead of window.open and the isCookieConsentRequired API has been updated to return false for popup case.
INC-170041 · Issue 655252
Check and error message added for filename containing "%00"
Resolved in Pega Version 8.6.1
At the time of file attachment or upload, if the file name contained % followed by two 0s (%00), the file upload mechanism distorted the UI and the Pega logo screen popped up. The file was saved properly in the ServiceExport directory, but while fetching the attachment info, the file was split in two because the engine considered %00 as a delimiter. This has been resolved by adding a file name check and a pyInvalidFileName field value to be used for an error message.
SR-B7965 · Issue 291732
Resolved mobile case switching exception
Resolved in Pega Version 7.3
The console error 'Exception while trying to set work item as completed in assignment list' was seen while context switching a case in a custom mobile app. This was caused by the configuration calling submit during preprocessing, and has been fixed by ensuring the onSuccess callback of finishAssignmentAction is called when there is no next Task.
INC-175205 · Issue 652530
Agent restart made more resilient
Resolved in Pega Version 8.6.1
During a timeout outage, agents intermittently encountered a NoClassDefFound error and were disabled. After the database connection was restored, the agents were not automatically restarting. This has been resolved by making the code more resilient to errors; agent will be restarted when a temporary issue is detected, and the restart will be immune to most exceptions.
INC-174921 · Issue 652321
Client Side required validation applied to dropdown Date field
Resolved in Pega Version 8.6.1
The mandatory validation on submit of the screenflow screen was not being triggered even though 'Required' was configured on the Date field.This was traced to the validation being applied to a hidden field when the date time control is configured in dropdown mode, and has been resolved by adding a condition for validating this configuration.
SR-D65034 · Issue 529564
Check added for malformed query on F5 refresh
Resolved in Pega Version 8.1.8
A 500 Internal Server Error occurred when F5 was clicked to refresh the screen. This was traced to a malformed URL that was missing the '?' before the query parameters, and has been resolved by adding a check in the pzpega_ui_dynamicContainer_lite js file replaceHistory method that will insert the question mark if it is not present.
SR-D58927 · Issue 522289
Added expiration for orphaned tracers
Resolved in Pega Version 8.1.8
After tracing a REST service, the tracer was persisting but not showing in the requestor list from Admin studio. The operator shown in the error did not have access to the system anymore, and other users were not able to trace the service rule. Trying to clear the requestors in all the nodes using API POST /nodes/{nodeID}/pools/requestor/clear also did not resolve the issue. To address this, a distributed rule watch expiration has been added.
SR-B14153 · Issue 284939
Only relevant records shown for work objects in select property picker
Resolved in Pega Version 7.3
The select property picker for all work objects with record identifiers was showing all records whether or not they were relevant. This was an issue where show relevant was being set to false when record identifier and show relevant was true in pyGetCategoryItems for all classes, and has been corrected by skipping this step for work object classes.
SR-B16328 · Issue 286668
BLOB data save performance improved
Resolved in Pega Version 7.3
In an installation with many large work objects, performance issues were seen when saving a BLOB. This was due to the BLOB still saving data for properties that had been removed, and has been resolved through better tracking of orphan entries of list type properties like string list and java object list.