SR-A34 · Issue 204505
Pega Lookup JSP tag correctly retrieves Chinese characters
Resolved in Pega Version 7.1.9
When the pega:lookup JSP tag did a field value lookup on pyCaption to retrieve the field value consistent with the locale, any Chinese characters embedded in the HTML pages used to generate the PDF rendered correctly but '?????' appeared in the PDF content instead of the Chinese characters configured in the Field-Value pair. This was caused by an issue in the code which caused the system to incorrectly identify NVARCHAR columns as being VARCHAR columns. This has been fixed., and the encoding for TestDatabaseNew has also been set to be UTF-8 to ensure the Non-ASCII characters in the tests are handled properly in all workspaces.
SR-A3428 · Issue 212424
Modified ClassName pass method for external DBs
Resolved in Pega Version 7.1.9
When DB2 is used as external DB (external table has a date column) and PRPC is hosted on a DB other than DB2, performing an obj-save into an external DB2 database failed with an SQL error. This issue occurred when a class was mapped to a table in an external DB which was not same as Pega hosting DB. In class PageDatabaseMapperImpl.java , function getDatabaseTypeFromEngine is used to check the database type when column type is Date, but the function was using a hardcoded value of class to determine the database type. This has been changed to pass className as parameter and use it to determine database type.
SR-A3744 · Issue 209253
Resolved Vtable NPE during engine start
Resolved in Pega Version 7.1.9
If a Rule-Access-When was defined on the class Data-Admin-System-Settings, search was initialized before the VTable is initialized. While initializing search, a DASS was set and a save operation was performed on the DASS which then tried to perform a security check and attempted to retrieve the Rule-Access-When from the unpopulated VTable cache. This led to an NPE. To resolve this, changes have been made so that search will be initialized after Vtable is populated.
SR-A940 · Issue 205402
Locking issue resolved for importing PUI jars
Resolved in Pega Version 7.1.9
Errors were being generated when importing PUI framework jars. This was an issue where the savepoints created in Saver.executeUpdate needed to be explicitly released on PostgreSQL to avoid locks from accumulating for each of the nested transactions, and the problem has been resolved.
SR-A990 · Issue 205075
Post-upgrade deferred list mapping reference inserted for new classes
Resolved in Pega Version 7.1.9
After migrating, the processing of the deferredlist while performing an updatestatus operation generated an exception from pzMapCases. This was caused by a class mapping issue where the new classes (InsertRuleSummary, UpdateRuleSummary, DeleteRuleSummary) added in DeferredOperationsImpl did not have interfaces in DeferredOperation. This has been corrected.
SR-A1139 · Issue 204433
Ensured threshold checkbox honored in Report Wizard
Resolved in Pega Version 7.1.9
Validation errors were being generated in the custom report wizard when 'threshold' was not selected. This was an issue where the validations were being added without checking the value of the checkbox, and has been corrected.
SR-A1220 · Issue 204961
Corrected SQL exception on Monitor Processes reports
Resolved in Pega Version 7.1.9
Some Pega out-of-the-box summary reports under 'Monitor Processes' like "Created in last 30 days by Operator", "Created in last 90 days by operator, etc., were throwing SQL exceptions on drill down if they had data. This was caused by the DrillDown activity getContentWeekly that was being used for some of the SVs not having the flags pyCanUseVirtualList and pyUseVirtualList set to true, unlike the default DrillDown activity getContent. This was causing the query generated for DrillDown to have the prefix "PC0" only for the drilldown filter condition. This has been resolved by modifying getContentWeekly to set the flags properly.
SR-A1267 · Issue 207657
Refined ScheduledTask-Reporting-pyExecuteTask to improve system performance
Resolved in Pega Version 7.1.9
An issue was found with performance degradation and excessive logging caused by the repeating of a scheduled report that had an exception and did not terminate after xx retries. Checks have been added to Pega-ScheduledTask-Reporting-pyExecuteTask in order to prevent this problem.
SR-A1733 · Issue 205403
Improved error handling for save-as of RD with invalid name
Resolved in Pega Version 7.1.9
Performing a SaveAs of a Report Definition with an invalid name was generating a stack trace Instead of showing a validation error for the name field of the save-as dialog. This has bene corrected.
SR-A185 · Issue 203599
All join values now showing in 'Pick value' pop-up
Resolved in Pega Version 7.1.9
PromptFieldValue and Table Type field values with a join were not being displayed in Valid Values. This was caused by the wrong Property name being passed to the query, and has been corrected.