SR-B1495 · Issue 273198
Workaround to resolve HP NonStopDB column label bug
Resolved in Pega Version 7.3
Using HP Non Stop DB as an external DB with Type 4 driver caused Connect-SQL with Browse to generate the error "UNKNOWN_COLUMN_0: Column number 0 has an invalid name errors in clipboard" but still return the data. This was traced to a bug in the HP driver that caused the getColumnLabel() to be returned as empty, and the system has been updated to return the Column Name when Column Label is null or empty to overcome this.
SR-D71977 · Issue 535599
Obj-Browse will retrieve more than 50 records
Resolved in Pega Version 8.3.2
After performing multiple skims, a newly added property was not retrieved when an Obj-Browse was performed. In Obj-Browse action, when a class is mapped to an external table and does not contain BLOB column pzpvstream, in a specific case where pxObjClass value is a reference to a parameter, a list of properties mapped to the class explicitly by querying pr4_rule_property table using NativeSQL is fetched. This call by default returns only 50 records: in cases where there are more than 50 properties for an external class, some of the properties from the obj-browse response mapping are therefore missed. To resolve this, the limit of 50 records has been removed from this NativeSQL call.
SR-D66674 · Issue 538971
DSS added for fall back to legacy decision table format
Resolved in Pega Version 8.3.2
After upgrade and switch to IL, non-working decision tables created in one class had pyWorkPage mapped to another class. In the column, the properties were mentioned as "pyWorkPage.xxxxx", but at runtime when the non-working decision tables ran as standalone, the system did not ask for values to be entered to evaluate the result. Tracer showed the error as "Goal seek requires missing input property pyWorkPage.All_Offln_Trans_In on page pyWorkPage; details: (unknown)". Investigation showed that the Legacy assembly for the decision table used the lazy evaluation pattern to resolve the expression in the column header in the generated Java code. This resulted in the property for the column header only being read when it was used. However, for IL-based decision tables all properties are read immediately before any rows are evaluated, which requires the property already be present on the page. This missing property from the lazy assembly then resulted in the exception. To resolve this, Executable.generateOrCompileSource and Virtual tableassemblyHandler.useIL() have been modified to fall back to legacy decision table format if the DSS InternalLanguage/disableIlBasedDecisionTable is enabled.
INC-174716 · Issue 656441
Updated handling for validating/saving circumstanced rule on branch
Resolved in Pega Version 8.7
Using 'save as' for an already circumstanced rule with a new property/template caused the Rule-.DictionaryValidation activity to register the error "StandardValidate-CircumPropAlreadyDefined". The same activity Step did not throw an error when saving into Branch. This was traced to the ruleset name not being the same for the branch ruleset due to having _BRANCH_Branch-Name appended to its name, and has been resolved by adding a condition to check for circumstanced rule in a branch.
SR-D62840 · Issue 534123
Updated HashMap logic for better concurrent thread handling
Resolved in Pega Version 8.3.2
The Pega execution engine was getting stuck at com.pega.eclipse.util.collections.HashtableOfIntValues.get for many thread within thread dumps. Investigation showed that when the key was not present in keytable, a thread would be stuck in an endless 'while' loop related to mapping. To resolve this, the data structure that is used for ruleset mapping from HashtableOfIntValues to Concurrent HashMap has been modified to better handle concurrent threads, and the handling for get and put has been updated.
SR-B7942 · Issue 284735
PDF barcode generation from eForm given configurable parameter checkbox
Resolved in Pega Version 7.3
When generating a PDF file based on an eForm that contains barcodes displayed via base64 encoded images, making the file read-only by using ConcatenateEForm's PerformFieldFlattening option prevented the barcodes from displaying. This was due to an "append" flag being passed to the 3rd party iText Library API "PdfStamper", and has been resolved with the addition of a flag (EnableNewVersion) in the "GenerateEForm" activity. The parameter will be by default true and may be unchecked for false, and is accompanied by a tool tip on hover of the checkbox as well as iText help.
SR-B7942 · Issue 285735
PDF barcode generation from eForm given configurable parameter checkbox
Resolved in Pega Version 7.3
When generating a PDF file based on an eForm that contains barcodes displayed via base64 encoded images, making the file read-only by using ConcatenateEForm's PerformFieldFlattening option prevented the barcodes from displaying. This was due to an "append" flag being passed to the 3rd party iText Library API "PdfStamper", and has been resolved with the addition of a flag (EnableNewVersion) in the "GenerateEForm" activity. The parameter will be by default true and may be unchecked for false, and is accompanied by a tool tip on hover of the checkbox as well as iText help.
INC-183728 · Issue 665133
Oracle handling updated for primary key in upgrade DDL
Resolved in Pega Version 8.7
Previously, when a primary key of a table was created Oracle would automatically create a unique index with the same name as the primary key. However, with the introduction of Oracle 19, an optimization was added which will not do that if there is another unique index on the table which contains the column(s) of the primary key. This difference can cause updates to fail with the error "cannot drop index used for enforcement of unique/primary key". This has been resolved by updating the handling for primary key constraint and the corresponding index name.
SR-B12474 · Issue 282553
BIX extraction config documentation updated
Resolved in Pega Version 7.3
When using command-line BIX 7.1 to extract records and write them to a secondary database, it appeared that some of the records got skipped. This was actually expected behavior: as the records got updated while the extract was running, those particular updated records got skipped as they did not fall into the time range that user was passing. To eliminate this confusion, the log message has been clarified. In addition, the information in the Guide indicated that if bix/useHistoryClasses was set to true, the generated query should always use the history table and not the actual work object table. However, it was not made clear that the BIX code does not use this option for explicit command line arguments. Therefore, the following text has been added to the BIX documentation under "Configuring the extraction environment" -> "Configuring optional prconfig.xml settings": Including class instances added during a batch run To ensure that class instances added to the Pega Platform database after a batch run begins execution are included in the extract, add the following property:
SR-D33003 · Issue 511229
Queue Batch activity correctly passes chlld process access group
Resolved in Pega Version 8.3.2
Attempting to create an index using the schema tools landing page was throwing an error in the table history stating "Create index failed". Investigation showed that this happened when a user was authenticated without the PegeRULES:DatabaseAdministrator role and then switched to an Access Group with the PegeRULES:DatabaseAdministrator role. The issue was traced to the activity that launched the batch requestor missing the parameter pzUseCurrentAccessGroupForChild due to the Queue Batch activity only passing the default access group authorization. This has been resolved by adding code to pass the additional authorization which will allow users to create an index in this scenario.