SR-C87757 · Issue 431645
Country Code for Austria saved correctly
Resolved in Pega Version 8.1.4
When trying to save an address with CountryCode=AT, the code was saved as "at" instead. This was caused by a temporary field value not being correctly cleared, and has been resolved.
SR-C76668 · Issue 424445
skipDocsRecreation option added to remove flickering during application launch
Resolved in Pega Version 8.1.4
In order to avoid visible flickering resulting from a dynamic container refresh conflicting with custom code during application launch, an enhancement has been added that can be used to skip the SDM refresh functionality based on the "pega.u.d.skipDocsRecreation" JS property. This can be enabled in Userworkform.
INC-207320 · Issue 701082
Email Approver shown in audit
Resolved in Pega Version 8.6.4
Email Approver activity was not being shown in Audit. This was traced to the queue instance primary page missing the necessary pyInboundEmail page property from pyCreateAndManageWorkFromEmail, and has been resolved by updating the listener activity to copy the needed value to a property called pyEmailFrom which will be used to record the events in the audit.
INC-210864 · Issue 706385
Tooltip added to specify Display Confirmation Message works for for template table only
Resolved in Pega Version 8.6.4
The Display Confirmation Message check box is a feature only available in template table and is not supported for legacy tables and Repeating Dynamic Layers. Text has now been added for an info tool tip to specify that use. There is a workaround for other areas to call the 'removeFromRepeatSource' function in UserWorkForm.
INC-195586 · Issue 698861
Updated access group handling for CurrentWorkPool property
Resolved in Pega Version 8.6.4
After update, the pxThread.pxCurrentWorkPool property was not properly populated in App Requestors when the activity was called from Rest service. This was caused by a difference in the authentication check after a security modification, and has been resolved.
INC-210771 · Issue 708811
Updated access group handling for CurrentWorkPool property
Resolved in Pega Version 8.6.4
After update, the pxThread.pxCurrentWorkPool property was not properly populated in App Requestors when the activity was called from Rest service. This was caused by a difference in the authentication check after a security modification, and has been resolved.
INC-211349 · Issue 709605
Service API called directly in CDH simulation
Resolved in Pega Version 8.6.4
Running a simulation from the Customer Decision Hub with strategy and dataflow that used customer data resulted in with either a failed run or blank explain detail reports. Investigation showed synchronization was not triggered due to the pxVBDAvailable call returning false, and this has been resolved by directly calling the service API without additional checks.
INC-211480 · Issue 712419
Handling added updates involving Oracle descending column
Resolved in Pega Version 8.6.4
The build was failing when attempting to update to Pega 8.6, and an error indicating an issue with Oracle columns was generated. Investigation showed that when a column changed that belonged to an index which had a 'desc' column (even if the changed column was not specified as desc), an Oracle restriction was triggered. This occurred with any column size increase if the column participated in an index containing a descending column or a function index. This has been resolved by adding a step to drop the index before altering the column if a Descending index is involved, and to catch the case where the resized index is part of an index that has a descending column but is not necessarily a descending column itself.
INC-213189 · Issue 707344
Addressed performance issues for classless DSMClipboardPage
Resolved in Pega Version 8.6.4
The DSMClipboardPage implementation handles Page Group access as a classless page (i.e. pxObjClass = ""), creating potential performance issues in implementations where the page group is used with a very large number of distinct AccountIDs in a short period. This has been resolved by updating the system to not cache keys for page group classless page.
INC-202793 · Issue 698056
Corrected malformed URL
Resolved in Pega Version 8.6.4
The function used in the session timer to log off the user was not working consistently, and attempting to discard a checked-out delegated Rule did discard the rule. Both issues reported the error "HTTP Status 400 - Bad request". This was traced to a badly formed URL, and has been resolved by wrapping the URL with SafeURL_createFromURL.