INC-142036 · Issue 594578
Additional BIX logging added
Resolved in Pega Version 8.1.9
In order to improve the ability to trace and resolve issues related to BIX extract rule failures, additional diagnostic logging has been added.
INC-178923 · Issue 660887
Resolved startup error related to business calendar object
Resolved in Pega Version 8.5.5
An error recorded in the log file when the server started was traced to a cache update that removed the old business calendar object and added the new business calendar object to the business cal list. This has been resolved by updating the system to replace the business calendar object instead of removing the old one from the cache first.
SR-A9147 · Issue 220746
Documentation updated for command-line BIX extractions
Resolved in Pega Version 7.2
The documentation for "Using a stand-alone command-line BIX extract process" has been updated to refer to the BIX 7.1 User's Guide regarding configuring the necessary database connection properties set (prbootstrap, prconfig, etc.).
SR-A6422 · Issue 216542
Made busy icon visible during data upload wait
Resolved in Pega Version 7.2
The Busy Indicator was not being displayed during the wait period following the uploading of multiple records at a time from an Excel sheet to a flow action. This caused confusion about whether the process was still running. The issue was caused by poor positioning of the busy icon in a non-visible part of the screen, and the calculations for its location have been updated.
SR-A10487 · Issue 221146
Resolved BIX command line NPE for username/password
Resolved in Pega Version 7.2
Attempting to run a BIX extraction from the command line without specifying -a/-p (username and password) parameters failed with a NullPointerException. This has been corrected.
INC-128899 · Issue 578022
Resolved BIX Extract Summary Status Count mismatch
Resolved in Pega Version 8.1.9
A mismatch was seen between the summary of the Extract Summary Status Count in the Execution History stats versus the logs, for example the execution history saying 98.74% completed while the log says 100% or 100.45% completed. Investigation showed there was mismatch in the query based on the filter value given in the extract rule and the where clause in the query that resulted in an error in calculating percentage in case of any exception. This has been resolved.
INC-145810 · Issue 599463
BIX log shows correct corrupted BLOB pzInskey
Resolved in Pega Version 8.1.9
An update has ben made to ensure the correct inskey is shown in the BIX logs for a corrupted BLOB.
INC-211977 · Issue 713461
Handling added for large BIX Postgres data sets
Resolved in Pega Version 8.6.5
BIX extracts were causing timeouts or JVM out of memory errors. This was traced to the Postgres JDBC driver ignoring fetch size in auto-commit transaction mode, which led to everything being loaded into memory at once. To resolve this, changes have been added to support fetch size for large results when using PostgreSQL database for BIX Extraction.
SR-A12347 · Issue 212822
Added check for BIX extract that will exceed filesize name limit
Resolved in Pega Version 7.2
Running a BIX extract with the -i option failed with the error "Error while creating the csv file: The file name entered exceeds the maximum size allowed (255 characters)". This happened in environments where the codehit the OS limit on the filepath name. This can be avoided by ensuring the File Specification tab of the Extract Rule contains a directory path shorter than 255 characters and by taking care not to have another Extract Rule with the same name in a Branch or a higher ruleset version with file specification path longer than 255 characters. To assist this, a check has been added.
SR-A6089 · Issue 215650
Resolved Class name mismatch in root element in BIX XSD
Resolved in Pega Version 7.2
Running a series of comma separated extract rules to an XML file from the command line resulted in the class elements in the corresponding XSD file all having the same classname. This was caused by an error in the array list processing that caused the values to be overridden by the last extract processed, and has been corrected.