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.
SR-D5404 · Issue 444566
Support added for nested grids with child categorization
Resolved in Pega Version 8.2.2
Show Details and Expand All were not working as expected in a repeat grid with a nested grid scenario where the parent grid had Show Details enabled and the child grid had categorization enabled with one column selected for categorizing. Investigation showed that a null page was being passed (final @baseclass pzGridSortPaginate activity) due to a lack of support for considering page lists that are embedded in a page different than the step page. To add this support, the activity has been modified to use tools.getProperty(...) instead of myStepPage.getProperty(...) if the data source page list is not an embedded property in the parent row page.
SR-D6265 · Issue 475306
Cursor action corrected for pyRecents section refresh condition
Resolved in Pega Version 8.2.2
If a “Layout Group” was used to add content in the left panel of the User Portals, the inclusion of the out-of-the-box pyRecents section with the standard refresh condition resulted in incorrect cursor behavior when selecting landing page options, displaying the content in a tab while the cursor in the left hand panel jumped up or down one position. Investigation showed that the index in the bar menu was wrongly set in sessionstorage when separators were present, and the issue has been resolved by updating the setstate and maintainstate methods to not consider the menu-separator in calculating the index.
SR-D6695 · Issue 482517
Predictive model now handles database oeprations progress states
Resolved in Pega Version 8.2.2
When attempting to create a predictive model, the page was hanging and would not process. Investigation indicated that this was a result of a missing use case from recent changes made to the progress bar logic for termination conditions, and has been resolved by adding handling for database operations progress states.