SR-B13775 · Issue 286916
Resolved error in adding Association's Page Property in report browser
Resolved in Pega Version 7.3
Adding an Association's Page Property while creating a report in the Report browser generated an error on the screen. This was caused by incorrect passing of the class, and has been corrected.
SR-B13785 · Issue 284733
Added tenant ID check for batch thread in MT environment
Resolved in Pega Version 7.3
When attempting to build a Hybrid Container app in the mobile tab (landing page) in tenants, the build did not complete. The same build did work correctly in the main requestor. The issue was traced to a missing tenant ID if a secondary instance had been written to the database by a background thread, and has been resolved by explicitly checking and if necessary adding the tenant ID to PRThreadwhen using batch thread in a BuildServer client.
SR-B13785 · Issue 284743
Added tenant ID check for batch thread in MT environment
Resolved in Pega Version 7.3
When attempting to build a Hybrid Container app in the mobile tab (landing page) in tenants, the build did not complete. The same build did work correctly in the main requestor. The issue was traced to a missing tenant ID if a secondary instance had been written to the database by a background thread, and has been resolved by explicitly checking and if necessary adding the tenant ID to PRThreadwhen using batch thread in a BuildServer client.
SR-B13785 · Issue 278965
Added tenant ID check for batch thread in MT environment
Resolved in Pega Version 7.3
When attempting to build a Hybrid Container app in the mobile tab (landing page) in tenants, the build did not complete. The same build did work correctly in the main requestor. The issue was traced to a missing tenant ID if a secondary instance had been written to the database by a background thread, and has been resolved by explicitly checking and if necessary adding the tenant ID to PRThreadwhen using batch thread in a BuildServer client.
SR-B13872 · Issue 290520
StartDependencies RUF logging updated from Error to Debug mode
Resolved in Pega Version 7.3
After calling a utility to create a child case through an activity on a parent sub-flow, updating the parent case status with the "UpdateStatus" activity logged an error message that the dependent had not been created successfully. This was an unintended side effect of a logging change made for diagnostic purposes, and has been fixed by changing the logs from Error mode to Debug mode in the pzStartDependencies RUF.
SR-B13882 · Issue 283566
Cassandra processing improved to resolve OOM related to cluster keys
Resolved in Pega Version 7.3
A dataset defined with multiple cluster keys caused OOM errors when used as a source in a data flow. This error was caused by an inefficient method of processing Cassandra records that was not scalable, and has been resolved.
SR-B13929 · Issue 289408
Instances Count updated to better handle external DB checks
Resolved in Pega Version 7.3
Opening the Data table list from the Designer studio DesignerStudio > Data Mode > Data Tables > Data Tables generated an exception related to obtaining a count of instances from an external DB. This has been resolved by adding a check which modifies the activity based on whether the call is to an internal or external DB.
SR-B13931 · Issue 286184
BIX extract Inskey error fixed for nested page lists
Resolved in Pega Version 7.3
BIX Extract was failing with the message "Inskey of the corrupt Instance" if it encountered nested page lists. To resolve this, the PropertyReferenceImpl.filter() method will add missing elements in cases with nested pagelists.
SR-B13960 · Issue 284420
Cassandra config updated to get proper native transport port setting
Resolved in Pega Version 7.3
Adding a Decision Data Store node failed with an error due to the native transport port setting in prconfig.xml not being properly read. The CassandraConfiguration method responsible for reading the port has been updated to get the proper value.
SR-B14059 · Issue 286249
Dimensions caching and size limit modified to resolve OOM
Resolved in Pega Version 7.3
When adding VBD nodes into VBD Services LP, an OOM error occurred due to VBD caching the whole IH Fact table along with associated Dimensions. The caching behavior has been modified to reduce the amount of memory used by only loading the columns from the IH Fact table that correspond to dimensions or measurements, as they are defined in Data-Decision-IH-Config. Additionally, Dimensions will be limited to 10K entries per dimension.