SR-B76526 · Issue 326533
Backwards compatibility enhancement for @when() validation
Resolved in Pega Version 7.3.1
After upgrade, a Strategy rule which referred a 'when' with the syntax @when(isOnlineApplication) was failing with design time validation saying that when rule was not found in the SR and instead it had to find it in the Customer/Applies to class. For the @when() issue, the root cause was that the validation context of @when() was switched from Applies-To class to the Step Page class due to a change in the core engine. The behavior of expression parsing for when rule calls was changed in release 7.2. It used to take the Apply-to class to validate the existence of the rule, but not it is taking the Step Page class. And Strategy rule doesn't push/pop stackframe due to performance reasons, thus StepPage on stack for Strategy is always the same as Primary page. For greater compatibility, the system will set the PageContextClass to the Apply To class so the expression parser can validate the setup which is expected at run-time.
SR-B50434 · Issue 317985
Struts mapping updated to compensate for behavior change
Resolved in Pega Version 7.3.1
The expectation was that after system startup in a zOS multi-servant environment where each servant has two JVMs which are running at any given point of time, launching SMA after adding a primary node should cause the servant node to show up in the edit page and upon submit the servant nodes should be listed under the primary node under left navigation links. However, after upgrade new nodes added to the cluster in the SMA were not visible due to behavior change between struts releases. This has been addressed by modifying the mapping in struts.xml and tuning some JSP syntax issues in AddNodeIDs.jsp.
SR-B56125 · Issue 317516
WebLogic deployment guides updated for dual user setup
Resolved in Pega Version 7.3.1
The WebLogic deployment guides have been updated to specify that dual user setup requires the addition of the jdbc/AdminPegaRULES datasource with entries added to prconfig.xml. This is similar to the method used for the Tomcat app server.
SR-B56437 · Issue 317515
Schema handling enhancement added for Alternate database option in list view
Resolved in Pega Version 7.3.1
A List view configured to use the Alternate Database setting generated an error when the report was run, due to the schema used by the Reporting Database (defined in the Sandbox-Work database table rule) having a different name than the default Pega database. The main Pega database schema is PEGA721, and the Reporting Database in this case was a schema called PEGA721REP in the same database, causing the table to not be found. As support for the reporting database being located on an alternate database with user specified schema is not available, an enhancement has been added to provide a prconfig that takes the schema for an alternate database and provides the support for ReportDefinition to use it.
SR-B69409 · Issue 317548
CLOB type handling enhanced in Marketing
Resolved in Pega Version 7.3.1
Pega Marketing uses the out-of-the-box DSM activity pxRunDDFWithProgressPage for triggering Data flow runtime. After upgrade in DB2 environments, the DF execution completed but the activity returned a failure. It was found that if a CLOB column is present in the filter of a NativeSQL object invoked from an activity, the status had an error message even though functionality was fine. To ensure consistent behavior, CLOB has been added to supported data types so the severity of the exception can be changed so as to not show error message in activity's status.
SR-B77148 · Issue 325930
Handling added for importing PostgreSQL database Application Bundles
Resolved in Pega Version 7.3.1
Application Bundle imports were failing on db2/MSSQL systems due to syntax differences, generating the message "FATAL ERROR: Encountered an issue applying DDL". Postgres database view definitions include ":: and character varying", but other databases do not require those characters. To ensure compatibility when importing the archives to non-Postgres databases from the Postgres instance, "character varying" will be removed through removeTypeCastingFromPostgreSQL in databaseschemaUtils. It will not be removed for import to another Postgres system.
SR-B77536 · Issue 326544
Check added to keep "::" in imports between PostgreSQL systems
Resolved in Pega Version 7.3.1
Application Bundle imports were failing on db2/MSSQL systems due to syntax differences, generating the message "FATAL ERROR: Encountered an issue applying DDL". Postgres database view definitions include ":: and character varying", but other databases do not require those characters. To ensure compatibility when importing the archives to non-Postgres databases from the Postgres instance, "character varying" will be removed through removeTypeCastingFromPostgreSQL in databaseschemaUtils. It will not be removed for import to another Postgres system.
INC-121460 · Issue 569118
IH Summaries correctly loads aggregated count
Resolved in Pega Version 8.4.2
After the IH Aggregated DataFlow has processed more than 34 million records from an Oracle database, the IH Fact table contained only ~120,000 records. Running a browse on the pxInteractionHistory DS resulted in an infinite loop. Investigation showed that this was caused by the handling of Oracle timestamps: using Pega DateTime in query parameters generated Oracle DATE instead of TIMESTAMP, causing all query parameters to be rounded to the second and interfering with the IH pre-aggregation. This has been resolved by updating the handling.
INC-122180 · Issue 563270
Null check added for Entity Extraction result
Resolved in Pega Version 8.4.2
Training data for an Entity Extraction model was not getting distributed correctly, as per the given % data. This was due to the result of the Entity Extraction result being null, and has been resolved by adding a check that will consider detected types as primary candidate for grouping if the result column is null.
INC-125838 · Issue 561484
Ignore Case feature updated
Resolved in Pega Version 8.4.2
In Pega Marketing 8.4 on the Action rule form, configuring an eligibility criteria and selecting the option for the comparison to ignore case did not copy this part of the criteria to the back proposition filter rule, so the case of the comparison was not ignored at runtime. This has been corrected.