SR-B9718 · Issue 286254
Corrected picking for mobile circumstanced harness
Resolved in Pega Version 7.3
On mobile devices the circumstanced version of tablet was getting picked instead of the mobile device. The invoke addSectionForOfflinePackaging_X method has been updated to resolve this.
SR-B9780 · Issue 286188
work object progression fixed after cancel/close with errors
Resolved in Pega Version 7.3
A repeat grid's modal dialog could be cancelled or closed without correcting the validation error fired by a field in it, but afterwards no actions could be performed on that specific work object even if the error was then fixed. This was caused by Messages added onto the pyWorkPage not being cleared on click of cancel if followed by clicking on grid pagination actions, and has bene resolved by changing the cancelmodal method from ModalButtonSubmit to ModalButtonCancel.
SR-B9879 · Issue 278433
RTE linkbox input handling corrected for modal windows
Resolved in Pega Version 7.3
In an "inline editable" grid with 'click to edit' selected, clicking on the RTE link inputbox in the modal window caused the grid row to be submitted as if the click took place outside the grid. The gridEventHandler has been updated to correct this.
SR-B9916 · Issue 283675
Hyperlink works on custom HC login page
Resolved in Pega Version 7.3
In a Hybrid Client App with a custom login page, a simple HTML link which calls the function to load the mashup code for the gadget worked in the browser but not in the HC. This was caused by window.open not working inside HC. To enable this, the _launchPopup api of compositegadgetmgr.js has been modified to use launchbox.Browser.start instead of window.open and the isCookieConsentRequired API has been updated to return false for popup case.
SR-B9998 · Issue 279141
Improved handling for apostrophe in email addresses
Resolved in Pega Version 7.3
In order to improve mail handling, the system will now only remove the the starting and ending apostrophe in an Email address and will not strip apostrophes in the middle of an address.
SR-B7729 · Issue 277669
Resolved file upload error for locales with special language characters
Resolved in Pega Version 7.3
Uploads to Pulse were failing when the file names or file paths contained special Turkish characters. This was an issue with the conversion to lower case changing the length of the string for some locale packages and has been resolved by swapping the call to string.toLowerCase for a call to StringUtils.indexOfIgnoreCase.
SR-C4920 · Issue 347563
Grid Header checkbox behavior modified for consistency
Resolved in Pega Version 8.1
Unexpected behavior was seen when clicking on the Checkbox present in Header: all other checkboxes changed their state (which was expected), but if the the Readonly checkbox was checked it was also changing the state the first time (which was not expected). After this first state change, the read-only checkboxes were not changing state (which is correct behavior). Previously, the behavior of Select All / CheckAll checkboxes was as follows: If the SelectAll / CheckAll checkbox is checked - Individual checkboxes are checked only when they are NOT disabled If the SelectAll / CheckAll checkbox is unchecked - Individual checkboxes are unchecked irrespective of their DISABLED state The behavior has now been changed as below: If the SelectAll / CheckAll checkbox is checked - Individual checkboxes are checked only when they are NOT disabled If the SelectAll / CheckAll checkbox is unchecked - Individual checkboxes are unchecked only when they are NOT disabled
SR-C7762 · Issue 350154
Commas removed from filter values to resolve validation errors
Resolved in Pega Version 8.1
When using a Grid layout configured in a section rule, clicking the Filter option and entering a comma separated value in the "To" field in a decimal-type column resulted in an "Invalid numeric range" option message. No error was seen if comma separated values were entered in both the "To" and "From" fields. Because the checkRangeFilter() function in ui_grid.js uses parseFloat() API to extract the decimal content entered in the search boxes, decimals after commas are ignored and validation failed due to the fields not matching. This issue has been fixed by implicitly removing any commas entered by the user.