INC-163469 · Issue 645952
Agent Schedule "Processed On" updated to allow extended schedule dates
Resolved in Pega Version 8.3.6
When scheduling or creating a queue entry in System-Queue-DefaultEntry using the Queue-For-Agent method in an activity, setting a value for "MinimumAgeForProcessing" of more than 24 days was passed as '2.074e+9' (the value in milliseconds). Because the parameter is interpreted as an integer value, this number caused an overflow Integer.MAX_VALUE error that then returned the incorrect value of 0 and events ended up scheduled for the current day. The queue item was created correctly when "MinimumAgeForProcessing" was less than or equal to 24 days. This has been resolved by updating the logic for reading the value.
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.
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-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-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.
INC-166631 · Issue 637021
Optimizing helper class enhanced to handle external databases
Resolved in Pega Version 8.3.6
Running a BIX extract that included a manifest for a target database was resulting in a null pointer exception for the manifest extraction. Attempting to generate the DDL for the manifest table also failed. This was traced to an issue with the helper class using a hardcoded default database for forming the queries, causing it to ignore the DB config/DADN/prconfig for the Oracle database and form a query using the PegaRules' database credentials. This only occurred when trying to do external database operations on a different DB platform; Oracle PegaRules worked as expected with an Oracle external DB and Postgres Pegarules worked with a Postgres external DB, but mixing Postgres PegaRules and an Oracle external DB would result in the null pointer error. To resolve this, the helper class has been enhanced to work with external databases by passing the database name as a parameter so it will properly calculate the query based on the type of target. The default for 'database/oracle/allowOptimization' is set to false: additional database privileges must be added or some configurations must be updated to provide the information needed in lieu of the privileges before making use of these optimizations. In addition, an error in the name of the class has also been corrected and is now available as PerformanceHelper rather than the previous "PerformaneHelper".
SR-B44280 · Issue 302124
Fixed REST call to JVM property http.non.ProxyHosts
Resolved in Pega Version 7.3
If JVM system properties are used to configure an HTTP proxy, it is applied unconditionally by all REST connectors. The JVM property http.non.ProxyHosts is normally used to exclude connections selected hosts from using the proxy, but due to an error this property was not being consulted by the REST connector. This has been corrected.