SR-B12737 · Issue 282869
Resolved harness error after using pagination 'load more'
Resolved in Pega Version 7.3
After using the Pagination 'load more' option and clicking on any of the newly loaded items, a blank harness was opened. This was traced to missing change tracking data for the newly loaded rows, and has been corrected.
SR-B40177 · Issue 297056
Resolved harness error after using pagination 'load more'
Resolved in Pega Version 7.3
After using the Pagination 'load more' option and clicking on any of the newly loaded items, a blank harness was opened. This was traced to missing change tracking data for the newly loaded rows, and has been corrected.
SR-B43621 · Issue 300812
Back/Previous years calculation fixed to use current year
Resolved in Pega Version 7.3
In the year dropdown for Date control, the number of back/previous years was calculated based on the selected year and not from the current year. The calculation logic has been fixed to resolve this.
SR-B7143 · Issue 281865
Div fixed for Add button using GridAction section include
Resolved in Pega Version 7.3
After upgrade, using the "Add" button configured as a section include with pzGridAction caused UI issues. This was due to pzGridAction (@baseclass) not closing the div tag properly after calling pzGadgetInclude, and has been fixed.
SR-B56216 · Issue 313130
fr_FR pyCurrency control corrected for using USD property qualifier
Resolved in Pega Version 7.3.1
Due to an incorrect currency evaluation, a pyCurrency property qualifier with a value set as USD in the corresponding property appeared in read only mode for operators using the fr_FR locale. With default locale, "1234567.89" was displayed as "1234567.89 USD" but with fr_FR it was shown as as "1 USD". This has been fixed.
SR-B43400 · Issue 307258
Localization added for field value used in 'Enter a Short Description' validation message
Resolved in Pega Version 7.3.1
Localization was failing for the 'Enter a Short Description' validation message when using a Field Value due to the message rule containing spaces. To fix this, a new message rule has been created without spaces in the same ruleset so that it is available for override use in the ruleset.
SR-B49520 · Issue 310724
Schema extraction over multiple DBs uses log table instead of class
Resolved in Pega Version 7.3.1
When running an extract, an Null Pointer Exception error was generated if the data being extracted was on a different schema / database than the Pega data schema. This has been resolved by reworking the sequence number generator to use a pr_log table connection of instead of using the class on which the extract was defined.
SR-B56540 · Issue 311961
Schema extraction over multiple DBs uses log table instead of class
Resolved in Pega Version 7.3.1
When running an extract, an Null Pointer Exception error was generated if the data being extracted was on a different schema / database than the Pega data schema. This has been resolved by reworking the sequence number generator to use a pr_log table connection of instead of using the class on which the extract was defined.
SR-B69420 · Issue 320400
Repeating Dynamic Layout can use source for base in Microsoft Internet Explorer
Resolved in Pega Version 7.3.1
When using Microsoft Internet Explorer, repeating dynamic layouts were only taking Data- as the base and could not be configured to add a source. Dragging and dropping a section did not provide the source either. oSectionBody, which is a DOM element, is sent to redrawSectionFieldSetCaptionInfo as a parameter. In Microsoft Internet Explorer this element is removed from the DOM and hence has no parentElement. This is the reason that the call to redrawSectionFieldSetCaptionInfo was failing. To resolve this, a check has been added to see if the oSectionBody is in the DOM by using the check oSectionBody.parentElement at the start of redrawSectionFieldSetCaptionInfo.
SR-B56648 · Issue 315674
Added security check when running out-of-the-box reports with ShowSelectorView
Resolved in Pega Version 7.3.1
A security issue was found where non-authorized users were able to access the out-of-the-box report details in their portal by manipulating the URL to pass a "short-cut" parameter that executed the Final "ShowSelectorView" activity. To avoid the need to set the explicit privileges manually, the ShowSelectorView activity will call a security check to prevent this.