SR-B92410 · Issue 342342
Password prompt localized
Resolved in Pega Version 7.4
Localization has been added for the "Please Enter A Password" message in the Password update section.
SR-B92436 · Issue 341864
Content type of mashup scripts set correctly
Resolved in Pega Version 7.4
The content type of mashup scripts was not being set correctly when the X-Content-Type-Options: nosniff header was enabled. To fix this, the code has been modified to use (set content type)pzGetURLHashes activity to set content to the response.
SR-B93133 · Issue 345828
Fixed unexpected scroll down in UI
Resolved in Pega Version 7.4
The expand button on a tree was not working the first time, but the focus was shifted to the bottom of the screen and caused scrolling. This was caused by the highlight field function attempting to scroll the focusable element into view, and has been addressed by introducing a new API scrollIntoViewIfNeeded() which invokes scrollIntoView() only when the element is not in the current view.
SR-B94216 · Issue 345203
Support added for buttons using simple image
Resolved in Pega Version 7.4
When using a customized Perform Harness set to use images instead of the icons class for Action buttons, performing the flow and closing the dirty Step Section generated a confirmation popup with the work area behind grayed out as expected. However, after pressing Cancel the image on the button was still greyed out even though the work area was not. This was due to the system not enabling the buttons using simple image as a source, and has been fixed by adding code to enabledisable.js to re-set the opacity for the buttons with simple image.
SR-B94341 · Issue 342033
Text Area control resize fixed
Resolved in Pega Version 7.4
The Text Area control was not getting resized as per the content when the window was compressed in Google Chrome or Microsoft Internet Explorer. To fix this, heightUpdate will be called for harness-resize event and registered at the harness level.
SR-B94512 · Issue 343457
Improved handling for attached PDF with '$' in PDF name
Resolved in Pega Version 7.4
If an attached file contained the "$" symbol in its name followed by any other character (such as 'paid$34.pdf'), it was not getting opened / downloaded from the Microsoft Internet Explorer attachment section. This was traced to the system attempting to cross-OS encode and then decode the filename, which resulted in corruption of the "$". To correct this, the system will decode only those character sets which will be cross-OS encoded in general.
SR-B94638 · Issue 342211
Selective localization added
Resolved in Pega Version 7.4
In order to support desired customized configurations like the Designer Studio being in English while the application is localized, a check has been added to pzGenerateDatePicker to get the default locale from tools.findPage("pxRequestor").getString(".pxReqLocale") if the portal is Developer and "Ignore locale" preference is selected. If this is not used, the system will get the default locale from tools.findPage("pxRequestor").getString(".pyUseLocale).
SR-B94720 · Issue 342356
Fixed disable when on button with two expressions
Resolved in Pega Version 7.4
When selecting Visibility condition (when Rule) and Disable Condition (expression) and adding two expressions, the second one failed with an "Invalid property reference" error and the Save button was disabled. Attempting to remove the 2nd expression still resulted in the Save button still being disabled due to the clipboard continuing to hold the incorrect entered value. Closing the expression outside the modal window and reopening it enabled the Save Changes button. This behavior was due to incorrect validation resulting from the lack of a 'when' check in pzValidateExpressionDialog for the secondLeftOperand, and this check has been added.
SR-B95191 · Issue 342664
Conditional Required fields fixed when working with accessibility
Resolved in Pega Version 7.4
When Accessibility is in place, the Conditional Required for fields was not working as expected, instead making the fields always required. To correct this, the tag will be generated conditionally after evaluation of required configuration.
SR-B95191 · Issue 341933
Conditional Required fields fixed when working with accessibility
Resolved in Pega Version 7.4
When Accessibility is in place, the Conditional Required for fields was not working as expected, instead making the fields always required. To correct this, the tag will be generated conditionally after evaluation of required configuration.