SR-C15869 · Issue 356792
Horizonal scroll fixed for business managed tables in Microsoft Internet Explorer
Resolved in Pega Version 8.1
After upgrading Pega Marketing, the horizontal scrollbar for business managed tables was not appearing when using Microsoft Internet Explorer . This was traced to an inline style 'overflow:auto' on DynamicLayout2 in the rule 'pzRecordsEditorWrapper' which is which was taking precedence in Microsoft Internet Explorer , and that inline style has been removed to resolve this issue.
SR-C15880 · Issue 360471
Modal dialog accessibility enhancements
Resolved in Pega Version 8.1
In order to ensure Modal Dialogs are accessible via screen readers and navigable using keyboard, the following criteria have been reviewed and updated as necessary for both editable and read-only use: - Modal dialog is accessible using the standard mix of screen readers (JAWS +Microsoft Internet Explorer + Windows / VO + Safari + Mac / Chromevox + chrome / NVDA / Firefox + windows) - Modal dialog is navigable using TAB key navigation - Modal dialog is dismissed on pressing ESC key - Modal dialog always has a aria label tied to the Title of the dialog - Modal dialog always has a close button
SR-C15887 · Issue 357943
Fixed Dataflow init issues
Resolved in Pega Version 8.1
An issue where Dataflow services failed to initialize service and the Add Node Button was disabled has been corrected.
SR-C15942 · Issue 358749
REST Connector Wizard Datamodel logic update
Resolved in Pega Version 8.1
The REST Connector wizard was failing to generate all the properties due to a problem with the DataModel generation. This has been corrected by adding two different Boolean properties in the property info map to separately tag request and response processing.
SR-C16004 · Issue 357445
Corrected additional instance being added when clicking on Dynamic Layout row with helper classes
Resolved in Pega Version 8.1
When adding helper classes (custom CSS) on a Dynamic layout or any others that use this feature, two instances were added when clicking on the row and not on the "+" icon. This happened when the layout had some action attached to it and that layout had children whose width was small (and there is no action attached to it) so that there was a lot of space remaining in the layout. In this case, actions were being appended to the queue twice, one from processBehaviorsOnElem call from processBehavior and another processBehaviorsOnElem call from processOtherBehaviors. To correct this, pzpega_ui_events .js has been modified to only call processOtherBehaviors when dynamic layout is used.
SR-C16062 · Issue 372412
ProcessAction will update pageName based on pyWorkPage
Resolved in Pega Version 8.1
A link which was configured to open a local action in overlay and then render a button which again referred to a menu in overlay was only working intermittently. On click, of some of the actions in menu worked while some resulted in a activity status error. This was traced to the method used to update the pageName in the "ProcessAction" activity, and modifications have been made to update pageName only if the primary page is "pyWorkPage".
SR-C16122 · Issue 358344
Removed irrelevant Primary page properties
Resolved in Pega Version 8.1
Irrelevant properties were appearing on the primary page while using Address Map control. This was traced to an improper function call and has been corrected.
SR-C16126 · Issue 388052
XMLCipher.java implementation adjusted for updated JDK8
Resolved in Pega Version 8.1
Errors were seen when using the decryption feature of SOAP services To resolve this, the Pega implementation of XMLCipher.java has been adjusted to correlate to recent updates made to JDK8.
SR-C16229 · Issue 357687
Check added to SQL generation to exclude BOM
Resolved in Pega Version 8.1
When using the facility System Upgrade > "Upgrade Applications Schema" from Designer Studio to generate a SQL file (as opposed to running directly from Designer Studio), the downloaded SQL was found to contain the Byte Order Mark sequence (0xEF,0xBB,0xBF) at the start of the file. This byte sequence caused the DB2 command line client to fail. This has been corrected by adding a check that will set 'aIncludeBOM' flag to false for SQL file generation.
SR-C16281 · Issue 358133
Null check added for filterOutWithdrawnCandidates
Resolved in Pega Version 8.1
During RUF resolution, encountering a candidate that was outside of the current RSL generated an Null Pointer Exception. This has been corrected by adding a null check in filterOutWithdrawnCandidates. If the ruleset spec is null, the candidate will be removed from the list.