SR-D2788 · Issue 438261
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-D3371 · Issue 439506
Association Resolver updated to handle filters created on secured properties
Resolved in Pega Version 8.2.2
After creating a Report Definition in a class (Example Class A) that had an Association in that report with Class B, no results were generated from the report when an Access Control Policy and Access Control Policy Condition were created for Class A and Class B where the Class B had an ACPC with a Value field that referred to a Data Page or clipboard page property. Investigation showed the system was not able to resolve the actual value of the datapage property in the generated SQL query due to Association Resolver resetting the filter value (the Page reference in this case) of a filter that is created on a secured property. This has been corrected by updating Association Resolver to not reset the right operand for a filter that is created on a secured property.
SR-D3556 · Issue 444612
Requestor.OperatorID page updated to stay in sync with current OperatorID to enable post-Auth activity mapping
Resolved in Pega Version 8.2.2
The systems pages were not getting updated to the right operator's context when a post-Auth activity was used for mapping. To support this use, the UpdateOperatorID trigger has been updated to keep the pxRequestor.OperatorID page in sync with the current operatorID page during SAML. The operator will also be saved during provisioning.
SR-D3655 · Issue 438567
Resolved UI issues with TextArea control
Resolved in Pega Version 8.2.2
Two issues were seen with TextArea after upgrade: 1) The UI flickered when using a section where a checkbox click caused a TextArea to appear; and 2) When 'size to content' was specified for height in the TextArea, the area became unresponsive when the content was reduced. These issues have been corrected by setting height to auto instead of 0px while updating the text area height.
SR-D3929 · Issue 446437
Auditing for automatic stage transitions improved
Resolved in Pega Version 8.2.2
The logic for pzCheckForAndDoAutomaticStageTransition has been updated to provide better audits for the movements related to automatic stage transitions.
SR-D3947 · Issue 457300
XSS security added to GET Request Work-DeleteAttachment activity
Resolved in Pega Version 8.2.2
Security has been improved against a potential XSS vulnerablity on GET Request Work-DeleteAttachment Activity.
SR-D4304 · Issue 444436
Locale object handling added to SimpleDateFormat
Resolved in Pega Version 8.2.2
Configuring an Authentication Service with signing certificates failed at runtime with a invalid date exception in non-English locales. This has been fixed by passing the locale object as parameter to SimpleDateFormat.
SR-D5076 · Issue 457318
Table layout overflow fixed for Microsoft Internet Explorer 11
Resolved in Pega Version 8.2.2
When a table layout had more than 10 columns, the table layout was overflown to right side of screen in Microsoft Internet Explorer 11. This has been addressed with the addition of a display:inline-block.
SR-D5196 · Issue 446367
Hardcoded prweb reference removed from the REST connector to enhance flexibility
Resolved in Pega Version 8.2.2
The DASS for pegarobotics/RobotManagerHostDomain allows specifying the instance where Robot Manager is hosted. Previously, connect-REST pzInvokeRoboticAutomation contained a reference to the resource path {RobotManagerHostDomain}/prweb/PRRestService/robotics/v1/automations which forced the use of prweb. In order to add flexibility, the hardcoded prweb reference has been removed from the REST connector resource path, and the pegarobotics/RobotManagerHostDomain) DASS's default value has been updated to include 'prweb' in it. Local sites should update DASS accordingly to point to an updated URL with prweb if needed.
SR-D5388 · Issue 457347
Corrected dropdown focus issue with dynamic layouts
Resolved in Pega Version 8.2.2
The focus was not retained on the dropdown field whose property was used in the dynamic layout for the refresh condition. Investigation showed that in pzpega_ui_doc_focus.js, the function "focusNextElement" was setting pega.u.d.gFocusElement set to null after the first load. This has been corrected.