SR-C5234 · Issue 360596
openIfStale() AP updated to ensure aUnlockOnCommit flag is honored
Resolved in Pega Version 8.1
Resolve- Pega-ProcessEngine:07-10-26 (Final out-of-the-box) was acquiring a lock on case but not releasing it later due to Opener not properly honoring the aUnlockOnCommit flag that was passed in via the openIfStale() API. This meant the the database value was always taking precedence over the passed-in flag. To correct this, the openIfStale API has been updated to remove a problematic "else" case. In addition, the system will check whether the lock is available in the map already: if it is, it will set unlockOnCommit to true, or otherwise, under all cases, honor the passed-in unlockOnCommit value.
SR-C53091 · Issue 391230
AddOnly bulk import correctly does not check for existing records
Resolved in Pega Version 8.1
When doing an extremely large bulk import using Addonly, the import API code was performing an existing record check when mapping pagelist properties. This was not the expected behavior, and has been corrected by updating the import java code.
SR-C5318 · Issue 388898
Silverlight digital signature updated
Resolved in Pega Version 8.1
Silverlight Prerequisites have been updated with the latest digital signature.
SR-C5347 · Issue 352087
Catch added for trailing backslash in case pyLabel
Resolved in Pega Version 8.1
Case pyLabel properties with a trailing backslash were failing to render in the UI. To correct this, a try catch and proper escaping have been added before the evaluation.
SR-C5347 · Issue 354157
Catch added for trailing backslash in case pyLabel
Resolved in Pega Version 8.1
Case pyLabel properties with a trailing backslash were failing to render in the UI. To correct this, a try catch and proper escaping have been added before the evaluation.
SR-C5569 · Issue 356377
Fallback method added to handle non-Java SQL timestamps
Resolved in Pega Version 8.1
After the pxCommitDateTime was added to a Business Intelligence Exchange (BIX) extract rule, the property was not extracted in the BIX output. This was traced to the getObject method returning a type of oracle.sql.timestamp when the system was expecting the getObject method to return a java.sql.timestamp. To handle Oracle or other databases that return a non-java SQL type, the resultset metadata will be used as a fallback method to return the java SQL datatype needed.
SR-C5608 · Issue 351744
Configuration for Decision Analytics Settings can be saved
Resolved in Pega Version 8.1
A change made to the default Database for analytics from "Decisioning > Infrastructure > Analytics Center Settings" was not getting saved due to the checkbox for posting the data being enabled which restricted the changes in the saved data. This has been resolved by unchecking the condition to refresh clipboard data on submit after editing the DB configuration.
SR-C56144 · Issue 394014
Keep-alive HTTP headers support added
Resolved in Pega Version 8.1
Long routing latencies to the stream tier were observed, and logging showed long times in the routing to the target of 50ms to 1 second. The Stream data set REST endpoint closed HTTP connections after every message, making it impossible to reuse connections and resulting in an overall slowdown of throughput of the system. To address this, keep-alive HTTP headers support has been added so clients can reuse connections and increase processing throughput.
SR-C6165 · Issue 353439
Block trimming fixed for rules with '@'
Resolved in Pega Version 8.1
While upgrading a rule from old version to new version some of the information was getting trimmed during parsing, resulting in a save-as error. This affected expression with syntax that included a leading '@' sign, including @(NPSPlusFW:NPSPlusUtilities).SIAppRateLookup(tools, myStepPage, .InquiryAmountCurrency, .InquiryAmountBaseCurr) is getting trimmed to .SIAppRateLookup(tools, myStepPage, .InquiryAmountCurrency, .InquiryAmountBaseCurr). This has been fixed by preventing the trimming of the block.
SR-C6360 · Issue 358392
Performance improvements for hotfix installations
Resolved in Pega Version 8.1
Hotfix installation was hanging at the 'Catalog.getRemovedJars' call, a performance issue which was traced to the string comparisons performed in order to identify the removable jars in a hotfix. Previously, the logic did not consider ignoring the comparison of already identified jars, resulting in running unnecessary comparisons. To improve performance, the system will cache the result of getRemovedJars for a specific product/version pair to help reduce unnecessary comparisons.