INC-130304 · Issue 567924
Retry logic added for downloading upgraded rules
Resolved in Pega Version 8.1.9
A Rules upgrade failed while downloading applications from the maintenance server due to an SFTP server connection failure. This has been resolved by adding logic to retry if the first connection attempt fails.
INC-130695 · Issue 587659
Enhancements for upgrading in multi-tenant environment
Resolved in Pega Version 8.1.9
Some muti-tenant installations use the same applications or rule instances with the same pzInsKeys for different tenants. This can cause upgrades to time out due to the system fetching all pzInsKeys (which will have duplicates) and working with them in a default batch size of 500 each over 4 threads. This led to the same keys potentially being allocated and processed in different threads, resulting in duplicate processing and timeouts. This has been resolved by updating the select query to fetch the tentantid and pzInskeys in the MT system to avoid duplicate work in multiple threads. In addition, running Generate Declarative indexes fetches the pzinskeys and generates indexes for each record, but before generating, the existing index for the record is deleted and then inserted. Because the delete query to generate the index was not tenant aware, all of the records for the key were deleted for the tenants for that key, but the new index was created only in one tenant. This has been resolved by enhancing the DELETE query to be tenant aware, which will avoid deleting the indexes for all the tenants given an index key.
INC-132218 · Issue 573359
Resolved buffer overflow for Migration loadDatabase
Resolved in Pega Version 8.1.9
A Rules upgrade failed in the Migration step at loadDatabase stage, involving the move of all the table records from old schema to new schema. This was traced to the inability of Migration to load blob of sizes more than 100 MB, and has been resolved by updating Migration to use byte[] to read the blob content with the help of metadata that contains blob length.
INC-133202 · Issue 574701
TableRenameUtil hashing improved
Resolved in Pega Version 8.1.9
During index name generation, the algorithm that was responsible for index name uniqueness was sometimes insufficient and cerated a loop condition. This has been resolved by using a stronger hash algorithm and refactoring the code that could result in a loop.
SR-D84364 · Issue 551402
Check for circular references added to SearchInventoryImpl to prevent recursive call
Resolved in Pega Version 8.1.9
An out of memory error was traced to SearchInventoryImpl infinitely recursing over a clipboard property, where the child property referenced a parent property and resulted in an endless loop. This has been resolved with the addition of a depth check to ensure that the search does not recurse infinitely.
INC-133986 · Issue 585431
Encryption documentation updated for embedded properties
Resolved in Pega Version 8.6
Documentation updates have been made to provide instructions on configuring property encrypt policies for embedded properties. This includes information on creating two policies, on the class where the property is referred/used and on the final property level, so these properties can be smoothly encrypted/decrypted at all the places in the UI.
INC-137757 · Issue 600489
Primary page setting updated for micro DC container
Resolved in Pega Version 8.6
In Cosmos, a "Cannot Render Section" error displayed on submit of modal dialogue. This was caused by a primary page calculation error for the micro DC container, and has been corrected.
INC-138443 · Issue 584680
SAML authentication documentation expanded
Resolved in Pega Version 8.6
Documentation for SAML authentication services has been updated to include more detailed information about app alias URL changes.
INC-139085 · Issue 589553
Documentation updated for using Custom Stored Procedure after upgrade
Resolved in Pega Version 8.6
Documentation has been updated to reflect that when upgrading an environment to Pega 8.3+, the following two prconfig/DSS settings should be removed. This is the preferred approach to use the new ID generation mechanism. Additionally, if a database sequence was previously used to generate IDs, pc_data_uniqueid should be added or updated to make sure each case type has a row defined, and that the pyLastReservedID matches the maximum of the relative database sequence value plus 1. env name="pega/sequenceid/useOldOOTBIDGenerator" value="true" or DSS: prconfig/pega/sequenceid/useoldootbidgenerator/default env name="database/databases/customUniqueIDproc" value="sppc_data_uniqueid_custom" or DSS: prconfig/database/databases/customuniqueidproc/default To keep using the old custom stored procedure, the following settings should be given either through prconfig or DSS setting (prefixed with "prconfig/"). The sppc_data_uniqueid_custom can be replaced with a custom procedure name with the same signature as the standard stored procedure. env name="pega/sequenceid/useOldOOTBIDGenerator" value="true" env name="database/databases/customUniqueIDproc" value="sppc_data_uniqueid_custom"
INC-139843 · Issue 594083
WSDL for Connect SOAP documentation updated
Resolved in Pega Version 8.6
SOAP integration documentation has been updated to include information regarding handling a WSDL that contains references to external XSD documents.