SR-A89295 · Issue 258931
Result count option added to Campaigns for performance tuning
Resolved in Pega Version 7.2.2
Slowness was seen when launching and running Field Marketing Campaigns. This was an issue with loading results using pxRetrieveReportData with paging enabled, as it fetched the total result count for each page. To resolve this, an option has been added to pxRetrieveReportData to disable fetching of total result count. This is available as Embed-QueryInputs property of type TrueFalse called 'pyReturnResultCount' when running report using pxRetrieveSearchData's pyReportParamPageName Parameter.
INC-137100 · Issue 604060
Added predictive text handler for Japanese on iOS
Resolved in Pega Version 8.4.4
The autocomplete function was not working well in MobileView when using Japanese IME on iOS. This has been resolved by adding a new input handler for IOS mobile, which will be triggered when predictive text is selected in mobile.
INC-147643 · Issue 605388
Corrected filtering logic for Report Definition with declarative join
Resolved in Pega Version 8.4.4
When using a report definition with declarative join enabled, running the report produced the correct results, but filtering on any other column resulted in all values being shown. This has been resolved by modifying the logic used for pzGetGridColUniqueValues.
INC-144103 · Issue 599682
Updated filter logic for filtering on a DateTime column
Resolved in Pega Version 8.4.4
When a class join was used in a report definition, the error "The Filter Logic used in the report is invalid" appeared while filtering rows of a report definition results on a DateTime column. This was a missed use case, and has been resolved by modifying pzGridSortPaginate to convert the data type value into the proper casing.
INC-147621 · Issue 604284
Updated filter logic for filtering on a DateTime column
Resolved in Pega Version 8.4.4
When a class join was used in a report definition, the error "The Filter Logic used in the report is invalid" appeared while filtering rows of a report definition results on a DateTime column. This was a missed use case, and has been resolved by modifying pzGridSortPaginate to convert the data type value into the proper casing.
SR-A100923 · Issue 269979
Property null check added to TrackSecurityChanges
Resolved in Pega Version 7.2.2
When using the out-of-the-box TrackSecurityChangesLogic activity in an application to track the property changes, an Null Pointer Error was generated when saving the property. This was due to a missing null check for the property, and has been fixed.
SR-A94690 · Issue 261686
Report Editor displays Associations
Resolved in Pega Version 7.2.2
When using a custom activity to display properties in the data explorer, the "More" link is not displaying the associations when added. This was an error in the logic which determined whether pyReportEditorProperties exists for the class or not, and has been fixed in pzGetCustomPropsForTreeGrid.
SR-A39964 · Issue 259183
Corrected unexpected rounding of decimal property
Resolved in Pega Version 7.2.2
Decimal value was incorrectly being rounded in the control for a decimal property which has Use Validate in place. This happened when the edit validate rule on the property failed and was then formatted using Double instead of BigDecimal. This has been fixed by updating the pxNumber control generation logic in the pzGenerateTextInput RUF to use BigDecimal instead of Double.
SR-A39964 · Issue 265562
Corrected unexpected rounding of decimal property
Resolved in Pega Version 7.2.2
Decimal value was incorrectly being rounded in the control for a decimal property which has Use Validate in place. This happened when the edit validate rule on the property failed and was then formatted using Double instead of BigDecimal. This has been fixed by updating the pxNumber control generation logic in the pzGenerateTextInput RUF to use BigDecimal instead of Double.
SR-A67007 · Issue 255075
Catch improved to close Message Explorer connections
Resolved in Pega Version 7.2.2
When using the Message Explorer functionality provided on the JMS Connect rule form, it only allows a number invocations equal to the size of the connection pool. Due to an issue with releasing the connections when using Resource Reference mode or IIOP protocol, the pool was being exceeded and the error "Couldn't create connection object" appeared. This has been fixed by changing the conditional catch for closing the connection with a more effective try catch.