SR-D28476 · Issue 500889
Corrected exceptions report appearing on user screen
Resolved in Pega Version 8.1.7
When "Break on all exceptions" was enabled, the exceptions report was visible on the end user screen when using Microsoft Internet Explorer 11. This has been resolved with updates to the 'pzpega_ui_dynamiccontainer' and 'pzpega_ui_doc_tabsupport.js' files.
SR-D34214 · Issue 511814
API available to skip defer loading in Single Page Applications
Resolved in Pega Version 8.1.7
The wait message "Loading ..." was displayed on check on defer load in Single Page Applications. The browser refresh worked as expected if 'defer load' was unchecked. This was traced to SPA not containing the handling necessary to publish the forced replace to other modules: in SPA cases, the dashboard is forcibly replaced with workobject harness, causing defer loads in dashboard to be processed in the wrong thread. To resolve this, there is now an exposed API pega.ui.DCUtil.skipDeferredLoadFrom() to skip defer loading when true in SPA.
SR-D37348 · Issue 514841
Added handling for placeholder in Multi-Select List Control
Resolved in Pega Version 8.1.7
After adding a placeholder in Multi-Select dropdown properties to hold the default value as 'please specify' by way of a refresh section on the action tab of multi-select property, the multi-select drop was showing the 'please specify' placeholder after refreshing the section even though there was value in it. This has been resolved by adding handling to make the placeholder empty when there are values.
SR-D40607 · Issue 509392
Empty pyIsDirty attribute will not be set to false on browser refresh
Resolved in Pega Version 8.1.7
After customizing Recents to show entries based on whether the "pyIsDirty" property was false or true, it was seen that the pyIsDirty attribute was being set to false on refresh of the browser window even when the WorkObject was not open. The normal behavior of the Declare_pxRecents data page is that the pyIsDirty value is set to false when a Work Object is opened and set to true when it's modified. For other Work Objects the value will be empty. To support the customized use, the code has been modified to skip setting the property to false if the value is "".
SR-D41984 · Issue 510014
Added handling to correct '&' displayed as '&' in custom tab name
Resolved in Pega Version 8.1.7
When using a data transform and custom properties to set the tab title, clicking on a link containing "&" in the label opened a tab name which included "&" instead of "&". This has been resolved by modifying the handleGadgetLoad method in the pzpega_ui_dynamiccontainer file to handle the Cross Scripting FIlter and display the character.
SR-D42583 · Issue 514488
Label of a field is correctly rendered when a section is re-used with a visiblity condition
Resolved in Pega Version 8.1.7
The label of a field was not being rendered/visible when a section with a 'visible when' condition was re-used in different Page Contexts. The label was displayed correctly if 'Run visibility condition on client' was checked. As part of performance improvements made in a previous version, label generation was moved under the dlcellvisibility flag. Because of this, if a section was re-used at multiple places with different contexts and one place had visibility false and another had visibility true, the labels were not getting generated for the visible section. To resolve this, Label Generation has been moved out of dlcellVisibility to ensure label metadata will always be generated. Updated performance improvements have been made instead by way of a DSS setting (generateCellMetadata) so that when generateCellMetadata is true, the label generation will honor dlcellvisibility to generate the label metadata.
SR-D42701 · Issue 510924
Cross-site scripting security added for Case Manager
Resolved in Pega Version 8.1.7
Cross-site scripting security has been added to the Document features in the Case Manager portal.
SR-D45360 · Issue 510101
Support added for non-decimal currency notation
Resolved in Pega Version 8.1.7
Previously in the pxCurrency control, the options allowed either specifying Decimal places (2 by default) or using the locale to decide decimal places when "Use currency standard" was selected (creating the default for 2 for en_US, 0 for jp_JP and 3 for ar_JO.) However, this did not account for currencies like JPY, TWD, and HUF, which do not use decimal precision. In order to support these currencies, handling has been added to formatNumaber js and pxFormatNumber for locales which do not have decimal precision in their currency.
SR-D48887 · Issue 512947
Read-only text inputs remain read-only after browser refresh
Resolved in Pega Version 8.1.7
Read-only text inputs were changing to editable after a browser refresh. This was traced to work done to better handle a displayOnPage GET request that was sent with all of the parameters in the parameter page (data-model) that was causing a 400 Bad Request due to the browser URL length limitations. That issue was resolved by removing the parameters which are not actually required for the displayOnPage GET call during the refresh case; to resolve this issue, the readonly parameter for displayOnpage action has been restored and will be passed.