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.
SR-D14159 · Issue 493056
Toggle added for displaying exception stack trace
Resolved in Pega Version 8.1.6
When text like "%25" was added to the login URL, the full exception stack was displayed on the screen. To resolve this, when the prconfig 'initialization/displayexceptiontraceback' is set to false (default value), the system will render the status.jsp instead of error.jsp and will not populate any sensitive data in the request object. If its set to true, the system will fall back to the old approach which renders error.jsp and emits the stacktrace.
SR-D24900 · Issue 494309
Security update for RequestMap error logging
Resolved in Pega Version 8.1.6
In HttpAPI, the RequestMap contains Cookie information. In error conditions, this map gets logged. An update has been made to ensure that the Cookie value is not logged if there is an error.
SR-D16624 · Issue 490929
Table layout filter popover position corrected for Pega mashup
Resolved in Pega Version 8.1.6
When using an exposed harness with table layout using Pega web mash up, the mash up worked but the apply and cancel buttons were not visible when any column was clicked to filter the result. This was traced to the filter popup having a hardcoded position offset set in its div element, and has been resolved by delegating the responsibility of the filter popover height calculation to the popover.
SR-D19177 · Issue 492340
Mashup refined to not trigger resize from popup
Resolved in Pega Version 8.1.6
The parent window was being refreshed when an action was performed on the child window or the child window was resized from the mashup script. This has been resolved by altering the logic to avoid triggering resize from popups in a mashup scenario.
SR-C96552 · Issue 488913
WordMacroManager updated to support both 32-bit and 64-bit
Resolved in Pega Version 8.1.6
After upgrade, the FlowAction=> CreateMergedWordDoc was not working. This was traced to Word Merge failures due to 64-Bit incompatibility with the WordMacroManagerDot template file, and has been resolved by updating WordMacroManagerdot.dot so it supports both 32-Bit and 64-Bit.