SR-B35799 · Issue 277230
Alerts modified to correct logged interaction totals
Resolved in Pega Version 7.3
The PEGA0069 alert identifies when a client load of a screen takes longer than the threshold for the alert. A client load can contain multiple server interactions and the PAL for the alert should be the aggregate of all these interactions. However, the calculations for pxTotalReqTime were duplicated in the code for the PEGA0046 and PEGA0069 Alerts, causing incorrect data. This has been fixed.
SR-B3580 · Issue 275558
Error fixed for PMF application RAP
Resolved in Pega Version 7.3
An invalid database script error was being generated when attempting to execute SQL generated from RAP on PostgreSQL. This has been fixed by modifying the matcher logic to remove text[] from the SQL text.
SR-B35821 · Issue 296032
Extra space removed from "Filters: " in RD
Resolved in Pega Version 7.3
When a Report with a large number of columns was generated using Report Definition with enable add filters checked in the report definition rule, an unnecessary space appeared between the "Filters:" label and the filters. This has been removed.
SR-B35861 · Issue 292611
Corrected distorted tab layout
Resolved in Pega Version 7.3
A complex tab layout with visible when conditions combined with deferload and refreshonactive was causing a distorted presentation at runtime if the first tab's visible when defaulted to false. This has been fixed with modifications to the setActiveTabIndex function.
SR-B35863 · Issue 294534
Mobile visibility condition fixed
Resolved in Pega Version 7.3
A section with visibility condition expressions on two properties was not displayed on mobile when the conditions were satisfied. The root cause for the issue was two change trackers being created for the same thread, which caused an override of the tracker properties. To solve this, the isSingleTracker API in change tracker has been modified to count the number of trackers instead of using a stored variable.
SR-B3591 · Issue 277488
Unit Test Case for DataPage localized for comma decimal indicators
Resolved in Pega Version 7.3
When using Dutch language localization, the use of a comma in a decimal number caused a parsing error when creating a Unit Test Case for a DataPage. Proper handling has been added to handle this localization format.
SR-B3591 · Issue 278006
Unit Test Case for DataPage localized for comma decimal indicators
Resolved in Pega Version 7.3
When using Dutch language localization, the use of a comma in a decimal number caused a parsing error when creating a Unit Test Case for a DataPage. Proper handling has been added to handle this localization format.
SR-B35931 · Issue 293471
prpcUtils readme updated for importing to Oracle
Resolved in Pega Version 7.3
The readme regarding importing to an Oracle database has been updated to reflect the current state of prpcUtils.
SR-B35963 · Issue 292315
pyID displayed in Show relevant Records
Resolved in Pega Version 7.3
Class keys were not displayed on select picker when accessing relevant records. This was due to an misplaced 'when' condition, and has been fixed.
SR-B35963 · Issue 292466
pyID displayed in Show relevant Records
Resolved in Pega Version 7.3
Class keys were not displayed on select picker when accessing relevant records. This was due to an misplaced 'when' condition, and has been fixed.