SR-C60129 · Issue 401825
Removed default height from pzTimeline_PresentationTab
Resolved in Pega Version 8.2
When using Timeline Control, the Default Height in the presentation tab was not being removed when it was changed to be blank and saved. When the control was opened the next time, it defaulted to show Height 300px and remained at that value despite repeated attempts to blank it. This was traced to a default height in the "pzTimeline_PresentationTab" section, and this default has now been removed.
SR-C61479 · Issue 403398
Bix extract performance improved by only checking cipher type for encrypted properties
Resolved in Pega Version 8.2
Previously, if no cipher was configured in extract Rules the cipher type defaulted to null and wasn't cached. This caused performance issues when running against the database. In order to improve performance, the code has been modified to only check for cipher type if the property is encrypted.
SR-C71527 · Issue 413129
Added ignorecase to correct authorization issue for username in all capitals
Resolved in Pega Version 8.2
It was not possible to delete a case note or attachment while logged in with a user ID containing all capital letters. This has been corrected by changing the equals comparison of .pxCreateOperator and pxRequestor.pyUserIdentifier to equalsIgnoreCase in CanDeleteAttachments access whens, HaveAttachmentDeletePrivileges when rule, pxHaveAttachmentSpecificAccess RUF, and HaveAttachmentSpecificAccess RUF.
SR-C61154 · Issue 411073
Improved DB stability and retry for issues with RetryContext$ExceptionForDatabase
Resolved in Pega Version 8.2
The agent was crashing when there was a report using a pr_read_from_stream for the 'where' clause combined with a postgres version with 'on pr_read_from_stream'. This has been addressed by improving the stability of the database and adding code to better handle reconnect and retry when there is a database problem.
SR-C44836 · Issue 410367
Drag and drop fixed for report editor
Resolved in Pega Version 8.2
An issue where it was not possible to drag properties to the report columns or filters in the report editor was traced to the HTML fragment RRBodyDiv outputting values from the paging settings in an unsafe manner, causing synactically invalid JavaScript to be generated when the "Previous and next only" paging option was used. To correct this, RRBodyDiv has been updated to generate valid JavaScript even if some paging settings are blank.
SR-C73608 · Issue 415510
Updates to controls and labels
Resolved in Pega Version 8.2
Issue 413604:When configuring a button with a disable condition, the condition was not returned in the readonly field. The PegaAPI has now been updated to support "disable". Issue 413597 / 413598: While calling the API to get the view of the screen as a JSON format, button type controls were not returning the label of the field using the OOB pxButton control. This has been fixed. Issue 413625: The PegaAPI section was missing when using clipboard page or data page with the rest method. To correct this, support for Embedded page has been added in the pyWorkPage for PegaAPI.
SR-C53759 · Issue 404973
Corrected revalidate and save of Service REST rule after upgrade
Resolved in Pega Version 8.2
After upgrade, opening an existing Service REST rule and trying to save it in a higher ruleset using the revalidate and save tool resulted in the error "pyResourcePathParams.pyParameterName : This field should not be blank". This was caused by the Service REST xml not getting updated and has been corrected by adding UpgradeOnOpen to the process.
SR-C64243 · Issue 403381
Data flow region switching method added to prevent truncating event strategy data
Resolved in Pega Version 8.2
An enhancement has been added to allow customers to switch data flow execution from one region to another without clearing event strategy data. This process looks like (1) Dataflow is started on one region. (2) Dataflow is paused in same region. (3) Dataflow is started in second region. Previously, step 3 would delete the existing event strategy data. To prevent that, a new run option has been added named 'pyDataFlowStorageTruncateOnStart'. By default, this is set to true and truncation will occur. If set to false, the event strategy data will not be deleted.
SR-C65633 · Issue 408042
Improved handling for parsing multiple formats of DateTime
Resolved in Pega Version 8.2
In order to further correct an issue with DateTime formats, the system will now use the parseAsDateTime and parseAsDate functions to properly handle the parsing of the date and date time values. The Pega format will be tried first, and if that doesn't work then the UTF formats will be used. If there is still an issue, the system will call back on the original parseAsXSDDateTime/Date which should catch all cases. An exception will no longer be thrown until after all parsing methods are tried.
SR-C65239 · Issue 411325
Check added to resolve nested grid component mismatch
Resolved in Pega Version 8.2
When using a nested repeating grid with expand pane option and expand multiple row options, running a screen flow resulted in a component mismatch error when moving from one assignment to another. This was traced to a limitation in the implementation that sometimes caused the parameter of the outer and inner grid to become corrupted or affect the wrong grid. In this case, the paramters startIndex and recordsInCurrentPage were resulting in a numberformatexception which in turn caused the component stack mismatch error. To fix the issue, an empty check has been added for startIndex and recordsInCurrentPage in the grid generation code.