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.
SR-B95701 · Issue 341895
Fixed localized non-operators seeing rule status
Resolved in Pega Version 7.4
A UI discrepancy in the new ruleform creation form led to Rule status dropdown being shown to non-operators who were using localization. This was due to a missing 'when' rule, and has been fixed.
SR-B96109 · Issue 344391
Calendar control fixed for Buddhist dates
Resolved in Pega Version 7.4
The Calendar control was not showing the Buddhist calendar when using the Thai locale (th_TH). This was an inadvertent result of an implementation update in calendar, and has been fixed.
SR-B96378 · Issue 342548
Error importing RAP with Japanese characters fixed
Resolved in Pega Version 7.4
When trying to import a RAP that contained Japanese characters (including application, organization, case type, data type, flow, flow action, property etc.), the preview was fine but the import wizard finished with the message "This archive is empty -- it contains no instances". This was due to a null pointer exception, and has been fixed by ensuring ClassTableMap.properties from the schema.jar will be read with UTF8 when needed.
SR-B97032 · Issue 342812
Target stale check added to cascading dropdowns
Resolved in Pega Version 7.4
The system was hanging when hovering on the drop down after selecting a parameter for which the dropdown did not have any values. This was due to the target element becoming stale when cascaded dropdowns were used, and has been fixed by adding a check for this condition.