SR-D65917 · Issue 529628
Cross-site scripting protection added to ClientDynamicData
Resolved in Pega Version 8.5
Cross-site scripting protection has been added to various parameters in the pzClientDynamicData HTML rule.
SR-D86274 · Issue 552509
Resolved validation conflict with error message display
Resolved in Pega Version 8.5
Error messages set through property-set- messages or edit validate were disappearing when out of focus from the date field if the field had a mandatory condition. This was traced to an edge condition where required validation was conflicting with another error message, and has been resolved by modifying the code so the system will not validate required on blur if the input has another error message.
SR-D75205 · Issue 543567
Refresh with DT or pre-activity added to dirty pop up check
Resolved in Pega Version 8.5
Given a button which when clicked launched a data transform to set a few properties on the UI followed by a section refresh, a dirty warning popup did not appear when closing the work object even though the property changed via the refresh section. This has been resolved with an additional condition in the dirty pop up check to handle a refresh section using a DT or pre-activity.
SR-D62361 · Issue 534810
Read-Only harness takes precedence over editable section with when condition
Resolved in Pega Version 8.5
Given a harness which was marked as Read Only and contained sections which were configured as editable based on some conditions, when the condition became true, the section became editable and ignored the read only conditions applied on the harness. Investigation showed that when a read-only 'when' rule evaluated to false, it rendered the layout in Edit mode instead of falling back to the read-only status of parent. This has been corrected by ensuring that when read-only evaluates to false, the system will fall back to the parent read-only status.
SR-D85228 · Issue 548200
Focus retained after cascading dropdown selection in IE11
Resolved in Pega Version 8.5
Given two DropDown fields sourced with data pages where the first dropdown value was passed as a parameter to the second dropdown source data page, at run time using IE11, If the first dropdown field value was selected using the tab key, the focus shifted to the second drop down field and was immediately lost. Pressing the tab key again set focus to the top of the window. This has been resolved by updating the system to retain focus upon cascading dropdown refresh when using IE11.
SR-D66436 · Issue 529672
Correct Value shown for Helper Text controls with labels
Resolved in Pega Version 8.5
Helper Text sourced from a field value was displaying the field value's 'Translate From' value rather than the 'Translate to' value. Analysis showed that the 'title' attribute of the corresponding icon on the DOM was being populated differently depending on whether it was a control with labels (not working) or a caption on a checkbox control (worked as expected). To address this, a check has been added for datetime and checkbox controls to send fieldname as pyCaption and pyActionPrompt respectively instead of pyTooltip to resolve the value.
SR-D95367 · Issue 560741
Expanded debug logging for exception blocks
Resolved in Pega Version 8.5
In order to enhance debugging, logging has been expanded to capture more detail on exception blocks.
SR-D87203 · Issue 550995
Required field accessibility improved
Resolved in Pega Version 8.5
In some instances, there is no non-visual indicator that a field is required. Because the asterisk character is commonly ignored by screen readers, the <required> attribute or <aria-required> should be used so that non-sighted users have explicit information about the required status of the field. To enable this, when client-side validations are disabled on the harness and clientValidation attributes are absent, the system will run an additional check so that aria-required is added.
SR-D79526 · Issue 544788
ClassName will be updated when element model page is updated
Resolved in Pega Version 8.5
In the event of traversing from Parent to Child, The Declare_pyDisplay datapage in clipboard was not in sync for the Child as the Active UI Element. This was traced to reliance on the pyClassName field of data element model (Declare_pyDisplay.pyDisplay(Developer).pyUIActive(1).pyClassName) to update the client side UI based on a particular condition evaluation. Because some of the properties in the element model are updated only if the page is newly created, using a page which was already present and updating values with some other UI actions was only updating specific properties which did not include pyClassName. To support this use, modifications have been made so the pyClassName will also be updated whenever the page is updated.
SR-D86429 · Issue 551372
Badge text Control Format supports declare expression target
Resolved in Pega Version 8.5
In the user screen, some properties are shown in 'Text' control with 'Badge text' control format. When the value of this property was set in Data Transform, it appeared correctly. When the property value was set in Declare Expression, no background color was set. This was traced to a missed use case in the implementation work for vtable, which resulted in the control format mentioned in presentation tab of control not being applied on markup when the property was a declare expression target. This has been corrected.