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.
SR-C6567 · Issue 352049
Enhancement added to customize Cassandra consistency level
Resolved in Pega Version 8.1
Inconsistent results were seen when the Cassandra database was queried from the Connect-Cassandra integration connector ruleset. During the queries, data is collected from different systems and loaded into the Cassandra database. If there is a distributed architecture, there is a risk that not all replicas will receive all the insert/updates at the time of the data load for any number of reasons (node down, node overwhelmed, network, etc.).With the default of consistency level 1, the Pega Cassandra query may hit a node that is missing the data requested. However, consistency level 2 forces Cassandra to read matching data from two nodes and in the background will perform a read repair on the node that is missing data. In order to enable the setting of a preferred consistency level for all connectors and for all operations, a new single DSS setting has been introduced: RS: Pega-BigData purpose:connector/Cassandra/consistency available values: " ALL ANY EACH_QUORUM LOCAL_ONE LOCAL_QUORUM LOCAL_SERIAL ONE QUORUM SERIAL THREE TWO"
SR-C6572 · Issue 363801
Updated DesignerStudioHotKeySupport to ensure Harness messages are preserved and displayed
Resolved in Pega Version 8.1
If LiveUI was hidden on a manager portal, the generated Harness level messages were not shown on the screen. This was traced to pega.desktop.preferences.initKeyBoardPrefs being called on load, which was erasing the errors. To resolve this, pzDesignerStudioHotKeySupport.js has been updated to ensure the messages are displayed as expected.
SR-C6595 · Issue 351217
Handling added for empty Dropdown placeholders
Resolved in Pega Version 8.1
When a field value was referred for a place holder of a autocomplete, at runtime it varied whether the place holder or the property name was displayed. This was traced to the handling for an empty currentContext.getLocalizedValue; the actual value was being passed if there is no corresponding entry in the context tree. The system has now been modified to avoid a call to the pega.clientTools.getLocalizedTextForString API if the property name value is empty.