SR-131522 · Issue 200840
Localization added for report name tooltips
Resolved in Pega Version 7.1.8
Tooltips in reports for report names are now available for localization.
SR-131538 · Issue 200108
Removed extra blank line from exported SV report
Resolved in Pega Version 7.1.8
An Excel spreadsheet exported from any Summary View (SV) report contained a blank row at the top. This has been corrected.
SR-132135 · Issue 202410
Smoothed 'save as' for private reports without checkout privs
Resolved in Pega Version 7.1.8
When a user did not have checkout option either at the operator level or at the design time rule-set level, trying to use 'Save As' on Report definition rules reports in Private category resulted in an error but actually saved the report at the back end. Opening the Case Manager portal and trying to do a 'save as' of an existing report led to the report category being populated as private but the standard categories got populated in the drop down. If OK was clicked, then the standard categories were replaced with private category. To improve this, a check has been added to detect a non-developer operator, who is then allowed to save in their personal category.
SR-132569 · Issue 201349
Corrected portal refresh after chart unload
Resolved in Pega Version 7.1.8
When a chart is unloaded, a separate request was sent to the server to remove all chart-bounded data pages, i.e. pzRuntimeChartCleanup. If nothing is returned, the ActivityStatusSuccess Message was seen instead of the Work Item when the portal was refreshed. The API has been updated to return the correct information.
SR-128463 · Issue 193907
Create KeyRing updated for split schema
Resolved in Pega Version 7.1.8
If a command line script is configured (viz. keyringGen.sh) to encrypt user passwords for prconfig.xml databases using Keyring utility, a prconfig.xml could have three database entries but the keyring tool only prompted for two databases and did not allow encrypting password for the user for the third database. The prconfig.xml file requires very specific location information to run: to resolve this, the variables to hold schema name in case of split schema configuration have been added.
INC-127102 · Issue 602699
Synchronized BatchStatus email available for multi-node
Resolved in Pega Version 8.4.4
An enhancement has been added which will handle synchronization between BatchStatus used in different events on different nodes and send email notifications.
INC-133482 · Issue 605004
Corrected isExternal flag not resetting
Resolved in Pega Version 8.4.4
If an extraction referred to external tables, an isExternal flag that was set to true during the Extraction process did not get reset to false for the tables which were not referring to external. This has been corrected.
INC-140110 · Issue 600400
Large filter values accepted in Report Definition edit
Resolved in Pega Version 8.4.4
Report definition edit filter values were not accepting large comma separated values properly. This has been resolved by modifying the logic in RRFilters_Logic to use ReportFilter.getReportFilters.
INC-143191 · Issue 596467
Scheduled tasks landing page shows all tasks
Resolved in Pega Version 8.4.4
Due to pzGetScheduledTasks listview having a hardcoded limitation of 500 records to be fetched, not all scheduled tasks were being shown in the scheduled tasks landing page. This has been resolved by modifying the pyCreateSummary activity to use a newly created Report Definition to fetch data instead of list view.
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.