SR-D3947 · Issue 456344
cross-site scripting security added to GET Request Work-DeleteAttachment activity
Resolved in Pega Version 8.3
Security has been improved against a potential cross-site scripting vulnerablity on GET Request Work-DeleteAttachment Activity.
SR-D5388 · Issue 456426
Corrected dropdown focus issue with dynamic layouts
Resolved in Pega Version 8.3
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-D6555 · Issue 457242
Access When check added for pyStartCase privilege
Resolved in Pega Version 8.3
If a privilege was defined in the pyStartCase flow rule and the access role to object assigned a privilege based on 'Access When' (not production level), the user was not able to start a case. This was traced to the havePrivileges RUF passing an incorrect primary page to evaluate the privileges in combination with the 'access when'. To resolve this, the engine API will call tools.getAuthorizationHandle().havePrivilege for each privilege until it finds a match.
SR-D3257 · Issue 457250
Database connection retry logic to class loader
Resolved in Pega Version 8.3
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-D8467 · Issue 461268
Resolved false alarm exception for Cloud BIX extraction
Resolved in Pega Version 8.3
BIX Extraction on Cloud was intermittently throwing an exception even though the BIX Extraction was successful. This false alarm was triggered by inconsistencies in an API within the BIX extraction module used to determine if files existed on a Cloud S3 location post-extraction, and has been resolved by removing the file check.
SR-D9132 · Issue 461282
Performance improvements for EventStoreWriter class
Resolved in Pega Version 8.3
The cache protocol has been modified In order to improve performance for the EventStoreWriter class.
SR-D10100 · Issue 464283
Bulk actions filter works properly when additional filters are added
Resolved in Pega Version 8.3
The Bulk Actions filter was not working if other filters were used in conjunction with it. Investigation showed that when 'assigned to operator' was given a value, the values were fetched properly. When an additional condition was added, the section 'pyBulkProcessingSearchSection' activity called 'pzDefaultOperators' which then set the 'pyUserIdentifier' value to null, and no results were returned. As the activity already had a step to check if the .pyUsage!="Operator" and only then property-set, pyUserIdentifier = "", the subsequent step to set the pyUserIdentifier = "" and override the previous step has been removed.
SR-D7798 · Issue 465259
Grid reordering has correct row numbers in embedded panes
Resolved in Pega Version 8.3
When using an expand pane grid with row numbering and row reordering enabled, normally reordering any rows handled the row numbers as expected. After a new record was added in the Embedded Pane and the rows were interchanged/reordered, the row numbers were not reordered with respect to the numbers. Expanding a row and reordering it with the previous row resulted in the numbers being correct and swapped, but collapsing that expanded row then showed its old number. Attempting to expand the above collapsed row/wrong number row instead expanded the previous row. To resolve this, the performModalAction function in ui_grid JS has been updated so the row page and primary page will be recalculated even for single expand reordering case.
SR-D7966 · Issue 465416
Documentation updated to clarify accessing Data Pages from another application
Resolved in Pega Version 8.3
The documentation has been updated to clarify that when the operator is pointing to one AccessGroup in the runtime environment, access for Data Pages created in applications other than the default one is not allowed in the API.
SR-D9511 · Issue 469238
pyPreTriage and pyPostTriage flows now default to Draft Mode Off
Resolved in Pega Version 8.3
The out-of-the-box pyPreTriage and pyPostTriage flows had draft mode turned on. Due to this, Email Triage cases in production systems were sent into the problem flow. This has been corrected by turning off draft mode for pyPreTriage and pyPostTriage flows.