SR-B30305 · Issue 288126
Fixed double encoding from Authorize URL scope
Resolved in Pega Version 7.3
If a scope had multiple values in Authentication Profile, then Pega Platform inserted '+' between them in run-time. This was due to the scope parameter value being double-encoded for the Authorize URL, and has been fixed.
SR-B30403 · Issue 290587
Layout group contents now load fully during a tab overflow
Resolved in Pega Version 7.3
Layout group contents were only partially loading when encountering a tab overflow in nested layout groups with defer loads. This was caused by an incorrect Layout Group height calculation, and has been fixed.
SR-B30410 · Issue 294913
Report drilldown works with 'do not display group headings'
Resolved in Pega Version 7.3
When sub-report properties were used in the main reports column source, the report definition displayed the expected results when clicking on a configured drilldown report and chart but displayed no results when listview dataset was clicked. This was traced to having "Do not display group headings" enabled in combination with drilldowns, and has been resolved.
SR-B30416 · Issue 292621
Removed extraneous showerrors check from onfocusinlistener
Resolved in Pega Version 7.3
After configuring a Grid item with validation rules, adding multiple records to the grid and clicking on submit without providing the values on the required fields as expected resulted in all of the error messages based on the configuration showing. An unneeded check to showerrors as part of the onfocusinlistener function has been removed to resolve this.
SR-B30423 · Issue 287970
Event Strategies enhanced for rolling windows
Resolved in Pega Version 7.3
incorrect counts were being created intermittently by Event Strategies used with a rolling window due to timing issues. To resolve this, the Event Strategy rule has been enhanced to better handle sliding time windows where intervals between incoming events are longer than the option value "Store state every N seconds" (given in the advanced settings of New: Data Flow Work Item).
SR-B30423 · Issue 280138
Event Strategies enhanced for rolling windows
Resolved in Pega Version 7.3
incorrect counts were being created intermittently by Event Strategies used with a rolling window due to timing issues. To resolve this, the Event Strategy rule has been enhanced to better handle sliding time windows where intervals between incoming events are longer than the option value "Store state every N seconds" (given in the advanced settings of New: Data Flow Work Item).
SR-B30426 · Issue 287706
Event Strategies enhanced for rolling windows
Resolved in Pega Version 7.3
incorrect counts were being created intermittently by Event Strategies used with a rolling window due to timing issues. To resolve this, the Event Strategy rule has been enhanced to better handle sliding time windows where intervals between incoming events are longer than the option value "Store state every N seconds" (given in the advanced settings of New: Data Flow Work Item).
SR-B30431 · Issue 287604
Enhancement to support encryption of Cassandra
Resolved in Pega Version 7.3
In order to build a HIPAA compliant Pega stack, support for encryption of Cassandra internode and client traffic has been added
SR-B30438 · Issue 292802
Audit window close button function change
Resolved in Pega Version 7.3
If an Audit--View history action was configured on the KYCWorkActionsPerform navigation rule, the link worked as expected from the case manager portal but generated an error if 'audit from other actions' was used and closed before accessing the link. This was due to the close button invoking the doclose function that clears the pyworkpage. To resolve this, the Advanced/history attachments tab close button will instead invoke self.close() .
SR-B30485 · Issue 287734
Tenant ID check added to Ruleset Wizard for MT
Resolved in Pega Version 7.3
Attempting to deleting a ruleset in a multi-tenant environment using the Ruleset Wizard resulted in the error message 'Getting records from the database' and the application would hang. This was due to a missing tenant ID in the SQL statement, and a check has been added to the query generation to ensure the prepared values for "pzTenantID" are included.