SR-D14591 · Issue 485930
Check added to resolve intermittent console errors
Resolved in Pega Version 8.3
An intermittent issue where an autocomplete control was hanging after repeated use has been addressed by adding an additional check (dispElem && dispElem.parentNode) to avoid console errors.
SR-D14573 · Issue 485986
Wait corrected for sub case after reopening
Resolved in Pega Version 8.3
A re-opened parent case was not waiting for the sub case when a sub case was reopened, but it did wait if there was no sub case on the reopened parent case. This has been resolved by enhancing the system to better handle the reopen of activator and dependent work objects by checking the reopen time: - pzGetAllStatusforDepClass activity: added step 2 to consider activator reopen time - pzGetMessageKeysForFlowDependencies list view: added criteria to filter on reopen time
SR-D15747 · Issue 486019
CSP policy added to login page
Resolved in Pega Version 8.3
CSP policy was not being added to the login page as expected. This was due to the application context not yet being established for the session because the login had not occurred yet. To resolve this, the functionality has been enhanced to set the CSP headers for the login page by getting the application list information from pxSecuritySnapshot.
SR-D16762 · Issue 486032
Search initialization logic updated to ensure consistent node member information
Resolved in Pega Version 8.3
The search function was intermittently failing across nodes after restart. Investigation showed that this was due to inconsistent results from search initialization cluster logic using Hazelcast APIs to tell whether or not a given node was part of a Pega cluster. To resolve this, the logic has been updated to rely on ES APIs instead of Hazelcast cluster membership to determine offline nodes.
SR-D15242 · Issue 486125
Removed unneeded TrackSecurityChanges warning for Field Level Auditing
Resolved in Pega Version 8.3
When creating a TrackSecurityChanges data transform for Field level Auditing and providing the text in the source, the system produced warnings such as "The source 'Number of covered objects' is ambiguous and is being treated as text. If it is a page, add it to the Pages and Classes tab." These warnings were generated by pzIsAmbiguousSource when a rule modified to check for Top.pyModelName did not equal pyTrackSecurityChanges. Because the way the system processes the data transform for field level auditing is not the same as that used for the usual data transform, this warning is not necessary. To avoid confusion, the system has been updated with a check so warnings of the source being ambiguous will be ignored when the DT name is pyTrackSecurityChanges.
SR-D14189 · Issue 486282
Recent Content updated to accept more than one URL attachment
Resolved in Pega Version 8.3
An error was seen when opening Recent Content and attempting to attach more than one URL. Investigation showed that Assign Page was getting cleared after adding the first URL attachment so it did not have a page value available for the second use. The logic has now been modified so the value will not be cleared in the Recent Content gadget preprocessing activity.
SR-D15875 · Issue 486380
Spinner wheel dom correctly cleared after incomplete case closure
Resolved in Pega Version 8.3
Incorrect behavior of the spinner wheel during a case search following the browser being closed while a case was open has been resolved by updating pzpega_ui_doc_actionRouter to ensure the wheel dom is correctly cleared.
SR-D14521 · Issue 486529
Added support for sorting by field value instead of localized value
Resolved in Pega Version 8.3
In a datapage-sourced dropdown with 'group by functionality' enabled in ascending order, the values were being sorted according to their localized value and not their field value. This was a difference between templatized and non-templatized handling, and has been resolved by adding the ability to sort the group label by field value in the templatized UI.
SR-D7381 · Issue 486565
Purge/archive locking issue corrected
Resolved in Pega Version 8.3
Updates have been made to resolve a locking release issue for the pzBatchPurgeArchive activity.
SR-D15895 · Issue 486593
Strict checking inserted to better handle database keywords in string constant
Resolved in Pega Version 8.3
After upgrade, a report was failing with the message "Rule Alias Function cannot reference a SQL function that performs a subquery." This was traced to the report having a function alias used in the columns which compared two strings and returned another string (constant - static value) if the condition was met. However, in two of the returned string constants there was the word "select", which is a keyword in all database languages. Even though the word "select" was a referred part of a string constant, the system treated it as a keyword and tried to perform a subquery within the Function Alias because ABAC was enabled. The report only exhibited this behavior post-upgrade because while ABAC defaulted to disabled in previous versions, it was changed to default to being enabled beginning with v8.1. To resolve this and create more robust backwards compatibility, a more strict check for subquery validation will be performed when ABAC is enabled which will parse and check whether the RAF has the standard 'select from' clause syntax of SQL.