SR-D15970 · Issue 485233
Handling added for runtime exception on upgrade due to inaccessible external schema mapping
Resolved in Pega Version 8.1.6
If a system used external schema mapping, attempts to upgrade were failing with the error "Caused by: com.pega.pegarules.pub.database.ConfigurationException: Unable to obtain data source "java:comp/env/jdbc/PegaRULES", as it is undefined". This was traced to configuring external DADNs which were not accessible from the server where the upgrade was being run: an upgrade will fail if it cannot connect to an external datasource even if no changes need to be made to that datasource. However, because a PRRuntimeException was unexpectedly being thrown instead of a Database Exception, the exception was not properly caught and handled. This has been corrected.
SR-D14161 · Issue 490596
Cross-site scripting protection added to decryptURLString
Resolved in Pega Version 8.1.6
In order to secure against Cross-Site Scripting attacks, decryptURLString will return a blank string instead of plain text if it is not given valid encrypted text.
SR-D10545 · Issue 483628
Minimum width set for stage names to ensure all are properly displayed
Resolved in Pega Version 8.1.6
The chevron displaying stage names was not showing the complete stage name in Microsoft Internet Explorer and Google Chrome when there were more stages due to each stage not having its own width set. This has been resolved by adding a minimum width for the stages.
SR-C93292 · Issue 432663
Inline error messages linked to input for accessibility
Resolved in Pega Version 8.1.6
In order to support accessibility for server side inline messages, the controls have been mapped to the error message div and an aria-describedby attribute has been added for the same. This allows JAWS to read the error message specific to the control where the error occurs.
SR-D25306 · Issue 499529
Corrected multiplying errors on dirty flag
Resolved in Pega Version 8.1.6
The error message "Value cannot be blank" was appended on the screen every time the browser gave a dirty flag and OK was clicked. This was due to the context for the error message not being set correctly after toggleErrorMessage, and has been corrected.
SR-D6978 · Issue 481763
Mandatory field confirm popup text and focus corrected
Resolved in Pega Version 8.1.6
When a mandatory field is tabbed out (with TAB key), using cancel to proceed to the next field instead retained the focus in the same field. This was traced to work previously done to prevent an infinite confirm dialog loop, and has been corrected.
SR-D10281 · Issue 482813
Configuration settings introduced for VBD read/write consistency
Resolved in Pega Version 8.1.6
Exports of VBD data at different consistency levels showed data inconsistency between Cassandra nodes. VBD uses the default DSM consistency level of ONE for its reads and writes, which will not automatically repair data when inconsistency exists. Data inconsistencies can lead to VBD timeouts trying to load partition data. To support VBD read/write integrity, an enhancement has been added to allow configuration of VBD read/write consistency levels by way of the following DSS properties (Owning Ruleset: Pega-DecisionEngine): vbd/readConsistencyLevel and vbd/writeConsistencyLevel. R + W > N where R is the consistency level of read operations, W is the consistency level of write operations, and N is the number of replicas. These will override the default DSM read/write consistency levels (ONE).
SR-D26010 · Issue 500165
Modified VBD insertion logic to improve handling
Resolved in Pega Version 8.1.6
An issue with not being able to launch an additional VDB node was traced to two processes inserting into VBD with different field signatures and triggering unnecessary object creation. This was amplified when adding a second node as the objects were serialized. To resolve this, the insertion logic has been modified to avoid creating new data container/field descriptors after a new field is included, as well as a measurement with smaller data type than previous container.
SR-D7054 · Issue 445404
Corrected Actuals data re-sync failure after trim
Resolved in Pega Version 8.1.6
The Actuals data set re-synchronize was failing after the IH table had been trimmed to drop older records. This was due to the IH/Actuals sync failing if the measurement columns in IH Fact mixed null and not-null values within the same partition. This has been resolved by correcting the format specifier in the log statement.
SR-D17927 · Issue 490558
Reolved special characters appearing as HTML values in case audit history
Resolved in Pega Version 8.1.6
Field values represented in the Audit history of a case were displaying HTML values for certain special characters. This has been corrected.