SR-C96362 · Issue 433332
XSS filter added to API form handling
Resolved in Pega Version 8.2.2
An XSS scripting filter has been added for properties that can be changed via API.
SR-C77121 · Issue 423113
Looping issue with CyberArk resolved
Resolved in Pega Version 8.2.2
In order to avoid looping issues when using CyberArk integration, the reference to PRMiniLoader has been removed from PRBaseLoader.
SR-D114 · Issue 435313
Grid menu dropdown properly hidden while editing filter
Resolved in Pega Version 8.2.2
After opening the filter options as if to change the filter, summarizing any of the available columns without closing the filter resulted in a screen showing a broken filter. This was traced to the implementation of the navigation menu for auto-generated grids, which was not allowing other functions while any of the "inline modals" are being used, such as editing a filter. To correct this, the grid menu dropdown will not be shown while editing a filter. This is consistent with the rest of the UI actions which are hidden while editing a filter.
SR-C88882 · Issue 431068
External mapping definitions will be used for exported property names
Resolved in Pega Version 8.2.2
Under the "External Mapping" tab on the class definition, if the property names specified were not the exact format as the column names defined in the database table, an exception was generated when using the "Export" feature. For this functionality, the system was generating an SQL which used the property names instead of column names. This resulted in an invalid column exception and the export did not work. To correct this, updates have been made to NativeSqlApiResolver in the function resolver to check for the property name and replace it with mapping defined in external mapping.
SR-D2457 · Issue 437345
Stale transaction error resolved for Robot Manager deletions
Resolved in Pega Version 8.2.2
The UI was hanging and displaying a stale transaction error after multiple entities were deleted from the Robot Manager UI. This has been resolved by adding clientFrame handling for SPA cases separately in the pega_ui_modaldialog js file.
SR-D13 · Issue 434982
Memory leak repaired
Resolved in Pega Version 8.2.2
A server side memory leak was traced to heap utilization increasing due to a Stream control assembly problem where the CleanForReuse() function was not cleaning up pzAuto. The cleanForReuse method in generated HTML properties is used to either initialize local fields, in which case aContext will be non-null, or to clear the object for pooling, in which case aContext will be null. Because the pzAuto variable was not being properly nullified, pooled controls were retaining stale references to StreamTools, LayoutRuntime, PRThread, and others. This has been resolved by adding code to ensure the pzAuto variable is correctly nullified.
SR-C90358 · Issue 433296
Updated Attach Content Control for use in repeat grid
Resolved in Pega Version 8.2.2
When using Attach Content Control in a repeat grid, selecting a file via attachcontent control and submitting the page resulted in the message "The operation completed successfully, but returned no content". This was traced to the newassignPage being removed after closing the modal, causing finishassignment to fail. To resolve this, the Attach Content Control function has been modified to set the needed grid attributes for desktop implementation to ensure newAssignPage will be available to the attach content modal action.
SR-C89463 · Issue 433821
Corrected tab name handling in Report Browser
Resolved in Pega Version 8.2.2
When using the report browser, refreshing the page after subscribing and unsubscribing to a report changed the tab name to the task id (eg. "PX-ST-123") and an extra tab appeared. This has been corrected.
SR-C97610 · Issue 435223
Enhanced backwards compatibility for Attachment Gadget
Resolved in Pega Version 8.2.2
After upgrade, information was missing from Attachments. This included the case number being absent from between the parentheses on the Attachment name; the time stamp was missing on the attachment; and checking the 'Show Subcase Attachments' checkbox did not provide the expected information for the attachment. This was traced to a reworking of the attachment gadget in Pega 7.1.5, and logic modifications have now been added to enhance backwards compatibility with the 6.x versions of Pega.
SR-C98214 · Issue 435684
Decision Table keeps proper values when a column is deleted
Resolved in Pega Version 8.2.2
When the first column in a Decision Table was deleted and the rule saved, the value that was in the second column was replaced in the first row. This has been corrected.