SR-B10103 · Issue 279865
Improvements in Export to Excel of very large files
Resolved in Pega Version 7.3
When exporting a very large (6000+ row) decision table into Excel, the process was very slow and the lack of a progress or busy indicator created the impression that the system was not responding. To resolve the processing issue, the code has been optimized to create lesser style objects. A busy indicator will also be displayed until the file starts download to indicate the operation is in progress.
SR-B10103 · Issue 279869
Improvements in Export to Excel of very large files
Resolved in Pega Version 7.3
When exporting a very large (6000+ row) decision table into Excel, the process was very slow and the lack of a progress or busy indicator created the impression that the system was not responding. To resolve the processing issue, the code has been optimized to create lesser style objects. A busy indicator will also be displayed until the file starts download to indicate the operation is in progress.
SR-B10103 · Issue 279866
Improvements in Export to Excel of very large files
Resolved in Pega Version 7.3
When exporting a very large (6000+ row) decision table into Excel, the process was very slow and the lack of a progress or busy indicator created the impression that the system was not responding. To resolve the processing issue, the code has been optimized to create lesser style objects. A busy indicator will also be displayed until the file starts download to indicate the operation is in progress.
SR-B10345 · Issue 281585
Command line jar import handling improved
Resolved in Pega Version 7.3
When installing Smart Dispute and related strategic applications, exceptions occurred when generating a DDL via prpcUtils (e.g. prpcUtils.bat generateDDL) if any of the files listed in schema.archive.input did not contain schema changes or did not have a delta. This has been resolved by updating the system to better handle files that do not require a DDL to be generated.
SR-B10347 · Issue 279670
Attachment icons display correct type
Resolved in Pega Version 7.3
The attachment icon was not reflecting the attachment type. This was caused by an error in the pzWorkAttachmentIcon control which caused the File name to be passed as empty, resulting in a failure to fetch the correct image name. This has been fixed.
SR-B10406 · Issue 279344
Custom operator images work in IE
Resolved in Pega Version 7.3
Custom operator images (using pxOperatorImage control) were not properly displayed in the Internet Explorer browser. This was traced to a malformed URL generated by the pxOperatorImage control, and has been fixed.
SR-B10620 · Issue 281882
Fixed disappearing cell value in grid row
Resolved in Pega Version 7.3
Entering a value in the first grid row cell configured with a post action change and then clicking outside of the cell caused the cell to disappear the first time, but worked as expected on subsequent clicks. This was caused by the postvalue action context parameter being lost, and has been corrected by adding an alternate way to get the active row in case it is not found using the getActiveRowIndex API
SR-B10667 · Issue 283291
IOS HC app login updated to better handle sync conflicts
Resolved in Pega Version 7.3
Intermittent HC iOS login failures or app crashes were accompanied by the error 'Client Store synchronization failed.' To resolve this, web-login has been updated to handle cases where login failure occurs while a sync is in progress.
SR-B10697 · Issue 282917
XSS handling added for pyCategory in Rule-Obj-Listview.ListViewHeader
Resolved in Pega Version 7.3
Cross-site scripting handling has been added for the pyCategory parameter in ListViewHeader to improve security.
SR-B10697 · Issue 280753
XSS handling added for pyCategory in Rule-Obj-Listview.ListViewHeader
Resolved in Pega Version 7.3
Cross-site scripting handling has been added for the pyCategory parameter in ListViewHeader to improve security.