SR-C8193 · Issue 356930
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-C8312 · Issue 358397
Open URL in window maintains context
Resolved in Pega Version 8.1
The on-click of a tablegrid where a Report definition is rendered on this grid was configured to open a URL in a window and call an activity named DisplayAlert. This worked fine if the DSS value DATA-ADMIN-SYSTEM-SETTINGS PEGA-ENGINE!PRCONFIG/INITIALIZATION/URLENCRYPTION/DEFAULT is false, but did not work if the DSS value was set to true. This was traced to the event infrastructure not resolving the Property references in the encoded URL context, and the pzpega_ui_events.js file has been modified to maintain the references.
SR-C8352 · Issue 358657
Added aria support to read radio buttons
Resolved in Pega Version 8.1
In order to ensure JAWS reads radio buttons, ' aria-required true' has been added to them.
SR-C8399 · Issue 353551
Tab closing problem fixed for multi-node environments
Resolved in Pega Version 8.1
An error in the code for pega.desktop.support was causing 'isSafeToAskParent' to be invoked even in non-mashup/IAC scenarios, leading to it returning "false" in multi-node environments where the port number was not one of 80 / 443. This in turn caused a failure to properly close a tab on the customer system. To correct this, the code for the pega.desktop.support.isSafeToAskParent call has been updated to skip it for non-mashup / gateway scenarios.
SR-C8725 · Issue 351894
Check added to ensure pyRuleSetName is not empty
Resolved in Pega Version 8.1
An extra condition has been added to the existing db-query which checks if a ruleset is locked to now also ensure pyRuleSetName is not empty. This will prevent a blank ruleset value from being passed in.
SR-C8735 · Issue 356715
Updated log error for hotfix commitment fail
Resolved in Pega Version 8.1
If no catalog file is found after committing hotfixes, the System Scan fails with no error message to the user even though the display of Committed/Uncommitted hotfixes is not updated properly. The message "Could not run System Scan - there is no Catalog on the system" appeared in the logs after the list of commits, but it was not clear what this indicated. The wording of the logged error has now been updated to clarify that the Committed/Uncommitted list of hotfixes has not been updated.
SR-C8776 · Issue 369407
Added explicit cleanup of non-serializable objects in the Connect-SOAP ParameterPage
Resolved in Pega Version 8.1
In investigating an application continuously logging error messages for Serialization, it was found that Connect-SOAP execution leaves non-serializable objects in the ParameterPage, which in-turn caused this the error logging upon requestor passivation. To resolve this, code has been added to remove the pyServiceClient, soapHdr, and activityParamPage parameters from the ParameterPage after use.
SR-C9001 · Issue 353898
Column alias checks added for import
Resolved in Pega Version 8.1
As a followup to a corrected issue for an export not including a column alias list, an import missing a column list alias has been fixed as well. The code will check for the presence of aliases, do a pattern match to check if aliases exist for view, and if they are found then aliases will be added for view generation during the import process.
SR-C9139 · Issue 352594
XSS filtering added to searched filter values
Resolved in Pega Version 8.1
ListViewHeader has been updated to apply XSS filtering to searched filter values.
SR-C9145 · Issue 355278
DNode dataflow generation exception changed from warning to FAIL
Resolved in Pega Version 8.1
The DataFlow-Execute generated code has been updated to create a PRRuntimeException in case of error so the activity step will change its status to FAIL instead of warning.