SR-B35050 · Issue 292342
Repaired BIX extract rule filters
Resolved in Pega Version 7.3
pyFilters that existed in rule XLM on check-out were being removed automatically after check-in, causing several runtime problems. This was an unintended consequence of an enhancement that added additional BIX SQL filtering capabilities that were more in line with the other platform modules such as ReportDefinition, and has been fixed.
SR-B35050 · Issue 293637
Repaired BIX extract rule filters
Resolved in Pega Version 7.3
pyFilters that existed in rule XLM on check-out were being removed automatically after check-in, causing several runtime problems. This was an unintended consequence of an enhancement that added additional BIX SQL filtering capabilities that were more in line with the other platform modules such as ReportDefinition, and has been fixed.
SR-B35117 · Issue 292760
Split-for shape "open flow" works as expected
Resolved in Pega Version 7.3
When working with a flow that contains a Split-for each shape which loops pyWorkParty and executes a flow on Data-Party class, an error was generated if there was a right-click on the sub-flow shape and "Open flow" was chosen. The sub-flow opened properly if there was a right-click on the sub-flow shape, "View Properties" was chosen, then a click on the "Open" icon right of the flow name. This was traced to the Top Class being passed for opening the flow rule in the Navigation rule "pyMenu" of "Data-MO-Activity-SubProcess-SplitForEach" class. To fix this, the class has been changed from Top to ".pyPageClass" in the Navigation rule "pyMenu" of "Data-MO-Activity-SubProcess-SplitForEach" to open the flow rule
SR-B35405 · Issue 292363
AddressMap properly rendered
Resolved in Pega Version 7.3
Using pxAddressMap control showed longitude and latitude values on the review harness and did not render the MAP until refreshed. This was due to the Address map being generated with one more 'if' condition around the editable condition. If this condition is present for the address map it may be marked as Editable control while its behavior is Action, causing the rendering issue. This has been fixed.
SR-B35741 · Issue 292129
Corrected thread contention in BAC
Resolved in Pega Version 7.3
A thread contention condition was found in BAC due to the use of maccesscache. That function and the matching clearAccessCache() function are no longer used in Basic ApplicationContext and BasicApplicationContextImmutableimpl to resolve the issue.
SR-B35799 · Issue 293251
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-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.