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.
SR-C96291 · Issue 445254
ADM initialization modified to eliminate unnecessary keyspace creation triggers
Resolved in Pega Version 8.2.2
On startup, ADM issues a Cassandra query to create one of its keyspaces if it doesn't already exist. To do this, it was set to require creation level permissions whether it created the keyspace or not, but those permissions may be considered a potential security violation if the Cassandra instance is shared with other teams. If permissions were restricted to only below key spaces used by Pega, then the ADM node would not start up. To resolve this, the way ADM initializes its keyspaces and tables has been modified so that queries requiring 'create keyspace' permissions are not triggered if the keyspace already exists. These changes also include code that ensures that keyspace and table creation can only happen on one node in the cluster at a time.
SR-C93802 · Issue 445245
Rounding added to avoid exception for ADM number too small to save to Oracle
Resolved in Pega Version 8.2.2
An exception was thrown when trying to save ADMSnapshot agent predictor bin data that was too small (below 1 x 10-130) for the Oracle Number column it was written into. This blocked up-to-date reporting on adaptive models. To resolve this issue, the code has been modified to round the double type numbers to an acceptable scale before writing to the database.
SR-C96786 · Issue 438850
Controls updated to handle hidden values in finishassignment submission
Resolved in Pega Version 8.2.2
A SECU0001 alert was thrown from the out-of-the-box function finishassignment upon the submit of assignments. This was traced to an alert generated while attempting to post the feed even though there was no Pulse gadget used in the work object, and was due to the handling of hidden fields as read-only. Since the read-only values were not editable, they should not be submitted with the request body; this has been corrected by modifying the hidden control entry handle such that hidden property is considered as editable-filled. Controls have also been added to pxHidden to prevent potential misuse.
SR-D3257 · Issue 453290
Database connection retry logic to class loader
Resolved in Pega Version 8.2.2
In order to create a more robust environment in case of connectivity issues, an enhancement has been made to add retry logic to database connections in the class loader.
SR-C88776 · Issue 428378
Added check for blank Value List Property referenced in Dropdown Control
Resolved in Pega Version 8.2.2
When a value list property was referred in the Dropdown control, the dropdown was shown as empty. This was traced to a property of type value list / value group, ClipboardProperty.getName() api returning as empty. To resolve this, a check has been added to ensure the value is populated with the correct property name if it is blank.
SR-C96571 · Issue 435175
Added check for visible SmartInfo so focus is maintained
Resolved in Pega Version 8.2.2
After setting up a harness that displayed page-level messages at the top and bottom with "info" icons in a grid that displayed SmartInfo, hovering on one of the "info" icons when a page-level message was displayed caused the page to scroll up to the page-level message at the top of the harness instead of displaying the SmartInfo popup. This has been resolved with the addition of a check for visible SmartInfo in pzpega_ui_doc_errors.js so the focus is properly set.