SR-D2286 · Issue 439251
UIKit 12 updated to ensure data pages are cleared when switching applications
Resolved in Pega Version 8.2.2
When using UIKit 12, switching applications without logging off resulted in the 'Recent reports' list and Public Category containing reports and folders that belonged to the previous application. Investigation showed that the pyCMReportBrowserHeader function in UIKit 12 did not include the custom control "pzRBIncludes7", which clears the data pages. This has now been added to ensure that report browser data pages are now automatically cleared on app switch.
SR-C95667 · Issue 438854
Corrected UI distortion for the errors container format
Resolved in Pega Version 8.2.2
After upgrade, using pydisplay to case stages in a harness resulted in misalignment issues in the UI. Investigation showed that this issue was due to an incorrect margin value for the errors container format following recent redesign work in the UI Kit, and has been resolved by correcting the value.
SR-D3598 · Issue 439125
CSS updated to correct Microsoft Internet Explorer issues with Flexbox
Resolved in Pega Version 8.2.2
After launching a user portal from Dev Studio in Microsoft Internet Explorer 11, the screen appeared blank. Each table column was stretched out, and a horizontal scroll bar appeared at the bottom of the screen that scrolled infinitely. Investigation revealed that this issue was caused by Internet Explorer not completely supporting FLEX containers. To resolve this, the CSS code for the screen layout region content has been updated to compensate and properly display in IE.
SR-C93726 · Issue 435286
Work status icons work correctly when using localization
Resolved in Pega Version 8.2.2
The pyWorkAssignmentStatus control was not displaying the status flags/icons for localized work status values due to a match failure caused by the system using the localized text for the pyAssignmentStatus to perform a string comparison against the hard-coded English values. To correct this, the control pyWorkAssignmentStatus has been modified to run the comparisons with the new string "assignmentStatus" instead of with the localized text.
SR-D392 · Issue 438872
Behavior reset for using getLocalizedValue with an input string containing parentheses
Resolved in Pega Version 8.2.2
After upgrade, the getLocalizedValue function was not returning any value if the input string contained parentheses. This was a difference in behavior caused by a missed use case when correcting another issue, and has been resolved by resetting the system to the previous behavior of getLocalizedValue returning a localized string in cases where a Field value/Rule message is present, or otherwise returning the exact input string.
SR-C91264 · Issue 433439
Localization fixed for dropdown sourced with pystate
Resolved in Pega Version 8.2.2
When pystate was used to source a dropdown, the options were all uppercase but in the review harness used lower case for IN and OR. This difference caused a failure in localization. This was caused by the Field value instance being defined in lowercase in PyCaption while the UI was treating the active value as an instance of pyCaption, leading to instances of both "in" and "IN" being present. This has been resolved by consolidating the field value to use a single case in the pega-eventprocessing ruleset.
SR-C98177 · Issue 437224
Explicit modal close added to MSOFileTransferButtons control
Resolved in Pega Version 8.2.2
When using a MSOFileTransferButtons control that included buttons for Download Template and Import, clicking Import caused a popup for File Upload to appear with two options - Upload and Cancel. On clicking 'cancel', an Invalid Static Content error was thrown. This was traced to legacy code interaction issues with newer features, and has been resolved with the addition of a custom script to close the modal on click of the cancel button.
SR-D1386 · Issue 446262
Warning message visibility conditions updated for Records Editor
Resolved in Pega Version 8.2.2
The Report Definition Result screen was showing the message "Warning : We were unable to create columns to match the new properties added. This will cause performance problems when using this data type. Please click here to fix this." Along with the RD results screen, this particular warning message was also shown in the Records tab of the respective Datatype. Initially, the Records Editor was developed for Designer Studio and Express usage. When the delegation functionality was later given to portals, the 'when' condition for the warning message was not updated to restrict displaying it to portal users. This has been fixed by updating the pzManageRecords section to properly manage the visibility condition of the warning message.
SR-C97479 · Issue 439534
Database indexes added for better performance
Resolved in Pega Version 8.2.2
In order to improve performance, database indexes have been added to pegarules-master.xml.
SR-D190 · Issue 436867
Job Scheduler History correctly displays pyPerformer
Resolved in Pega Version 8.2.2
After upgrade, the pxcreate operator value for work objects was blank when the objects were created via job schedulers, leading to the History not displaying the pyPerformer. Investigation showed that the user details in the requestor page were not being set correctly by the agent used to populate the details due to a lack of agent parity. This has been resolved by ensuring the userName and userIdentitfier properties are populated in the requestor page.