SR-B3208 · Issue 293911
Check added to ensure Tracer finds regular pages
Resolved in Pega Version 7.3
Page D_Properties was mentioned in pages to trace, it was present in clipboard, but was not passed to tracer due to an error in page handing. An extra check has been added as a fallback to look for a regular page if Tracer's data page check does not return a named page.
SR-B3208 · Issue 294773
Dot added to Rule Reference filename in Help
Resolved in Pega Version 7.3
The Rule Reference help file has been updated to insert a dot in the filename: "When you save a rule, the standard Declare Index rule named Rule-.RuleReference updates this table to reflect the references in that rule to other rules."
SR-B32118 · Issue 289472
PostgreSQL Date support added
Resolved in Pega Version 7.3
An "UnsupportedType: date" error message appeared when trying to create a Customer Data Class using the Database Table Class Mapping interface. This was caused by the activity 'pzLPRefreshColumnMappingsList'(class CL Pega-Landing-DataModel-DBClassMappings) not supporting DB specific column types. To fix this, isColumnTypeSupported has been replaced with a two parameter version (int aType, String aDBName) which has an additional check for "Platform specific supported types" in the activity 'pzLPRefreshColumnMappingsList'(class CL Pega-Landing-DataModel-DBClassMappings). DATE type support has also been added in PageDatabaseMapperImpl.java.
SR-B32119 · Issue 288996
Class Data-Admin-Connect-MQServer now cached
Resolved in Pega Version 7.3
The rule instance cache has been updated to include the type Data-Admin-Connect-MQServer.
SR-B32247 · Issue 291773
Resolved null-pointer exception at ReferencePropertyLinkToCommonParent
Resolved in Pega Version 7.3
When a reference property (liked via top level page) was copied with-in the page (intrapage), an null-pointer exception would be generated by a bad link if the number of levels in the new property differed from the original. The issue was traced to an error in the After Copy duplicator that did not correctly evaluate the target property in all environments. More robust testing has led to refinements on the duplicator to resolve this issue.
SR-B32559 · Issue 301028
New prconfig setting for auto-flipping Oracle optimizer
Resolved in Pega Version 7.3
Severe performance issues were seen while importing a RAP with Oracle 11g and 12c due to an Oracle bug related to SMA queries involving all_constraints. To fix this, the Oracle parameter _optimizer_push_pred_cost_based must be set to false before the execution of the SMA query and set back to true after its execution at the session level. This is not set on the system level since Oracle recommends against it. In order to ease this process, the flag setting can be controlled through the prconfig setting '"database/performance/smaqueryperformanceenabled". This prconfig setting will default to true in order to automatically set/unset the Oracle parameter each time it is needed.
SR-B32559 · Issue 297457
NexFlow requestor performance improvements
Resolved in Pega Version 7.3
The deployment of the Nexflow Application RAP was failing due to a requestor synch timeout if 'includeSynonyms' was enabled on the DB connection. Code updates have been implemented to improve performance to resolve this.
SR-B32559 · Issue 301682
Workaround for Oracle SMA query timeout
Resolved in Pega Version 7.3
A bug in Oracle can cause an SMA query involving all-constraints to take a long time to execute, which in turn can cause RAP/application bundle imports to hang. The workaround for this is to set the Oracle parameter _optimizer_push_pred_cost_based to false before the execution of the SMA query involving all-constraints, then set it back to true after its execution at the session level.
SR-B32616 · Issue 289417
New BIX feature to allow for the decrypting of TextEncrypted properties that are being extracted
Resolved in Pega Version 7.3
An enhancement has been added to allow text-Encrypted properties in the BIX extract to be available in cleartext so that BI tools consuming this output can draw insightful conclusions and make informed decisions.
SR-B32618 · Issue 289713
BLOB handling improved for empty properties in HistorySaver
Resolved in Pega Version 7.3
In HistorySaver, using ClipboardProperty.setValue to save snapshot data for the previous version of the rule had the side effect of stripping blank properties from the clipboard page. This caused rules relying on these properties to not be restored correctly. To correct this, special handling has been inserted for the instances History- class and its descendants to serialize blob with EmptyProperties.