SR-127380 · Issue 192186
Resolved problem importing work objects into tenant layer
Resolved in Pega Version 7.1.8
Trying to import a RAP containing several work objects into the tenant layer of a multitenant system generated errors including "Import cannot proceed due to conflicting rule instances." This was caused by certain import restrictions regarding work objects belonging to a shared content class that were set during the initial development of multitenancy which are no longer required; these have now been removed.
SR-127517 · Issue 199062
Fixed Listview filtering using manual entry
Resolved in Pega Version 7.1.8
List View filtering was not working when the filter string was explicitly typed in the filter section. Handling has been added to the Embedded list filtering to correct this issue.
SR-127803 · Issue 192265
Error information enhanced for Connector wizard working with external Teradata DB
Resolved in Pega Version 7.1.8
When using Teradata as an external DB, an exception was generated while using the SQL connector wizard and no rules were generated. This was caused by passing a date column that was not supported. The error has been addressed to make it more informative, but at this time the classes and properties for the fields and the mapping of the classes to the associated tables must be done manually. If the decision is made to use Date/Time properties that are mapped to Date fields, there may be time zone conversion issues. Further, mapping a Date property to the DATE column will allow the field to come across from a report definition but will not work as part of the filter (e.g. EFFT_DATE > "2014-12-01").
SR-128102 · Issue 193767
Resolved RD filter prompt not showing
Resolved in Pega Version 7.1.8
The Report Definition filter prompt was not displayed even when 'Prompt for filter changes' was checked. This was an issue with PXSHOWREPORT not using the correct step page, and has been fixed.
SR-128171 · Issue 196940
Drill down corrected for leaf node in RD summary report
Resolved in Pega Version 7.1.8
When a summary type report definition as used to source a tree grid, double-clicking a leaf node in the tree did not open the associated detailed view from the report definition. This was traced to a missing null check for the clipboard in the drill down activity, and has been resolved.
SR-128178 · Issue 192632
DataOnly upgrade modified to handle pr_data_products tables
Resolved in Pega Version 7.1.8
Running the upgrade.bat dataOnly true to upgrade the data schema failed while trying to insert values into the pr_data_products table. Promoting upgraded rules schema to higher environments and then upgrading the data schema is a supported upgrade procedure, but the dataOnly upgrade did not take this into account. The system has been updated such that when migrating post upgrade, it will not migrate pr_data_restore and pr_data_products tables and will fail if there are uncommitted hotfixes.
SR-128206 · Issue 192572
Added null check for RD column containing a function
Resolved in Pega Version 7.1.8
When running a report definition with a column that has a function, it showed the error "illegal zero-length identifier". This was due to the alias name for the Rule-Alias-Function with return type 'True or False' being empty in the pxSQLStatementPost function, and a check has been added to handle this.
SR-128285 · Issue 193082
Added handling for column size mismatch on Oracle import
Resolved in Pega Version 7.1.8
When upgrading versions of CMF, errors were generated when importing the Pega jar file. The exported schema has pyAccessibility and pyBrowserSupportLevel datatypes as "integer" with size 10, but on the target Oracle database the same column was defined as Number with default precision and scale (0, -127). While importing, the logic checks for column compatibility and was generating an alter statement based on this scale mismatch. This has been resolved by modifying the system to detect that the metadata is returning the new style of NUMBER column metadata handling it correctly.
SR-128320 · Issue 193581
Updated chart export handling for Safari
Resolved in Pega Version 7.1.8
The charts in reports are getting disappeared on click of When using the Safari browser, clicking on Export to Excel/Export to PDF caused the charts in reports to disappear. This was traced to the form target being blanked in the browser handling, and a browser check has been added to invoke special handling for Safari..
SR-128475 · Issue 194266
DB Trigger logic refactored for better vw table syncing
Resolved in Pega Version 7.1.8
There are many times in customer environments where for whatever reason the database triggers are disabled for a period of time and thus the vw table gets out of sync. Typically in that case the triggers are reenabled and a statement like "update pr4_rule_file set pzinskey=pzinskey" is run to get the vw table populated correctly. However, if the system was being upgraded the statement would update an existing row in the vw table but it would not add any missing rows to the vw table during migration. To ensure that all rows are handled correctly, trigger logic has been completely refactored for 7.1.8.