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-128179 · Issue 197764
Pagination added for ruleset versions ruleform
Resolved in Pega Version 7.1.8
Opening the Developer ruleform to view a ruleset in an environment containing multiple rulesets with thousands of versions presented performance issues where rendering took multiple minutes and scrolling was impossible due to the very large file size. To improve performance, pagination has been enabled for the ruleset versions section.
SR-128192 · Issue 193639
Libraries updated to reflect ruleset versions
Resolved in Pega Version 7.1.8
New ruleset versions were not showing in the Library. This was caused by improper version population: when a version-resolved rule (such as property/section) was created, a a data page would hold the default ruleset version. When a library (which is non version-resolved) was created, the default ruleset version was not reset and it became associated to the library rule. A fix has been added to reset the value of pyRuleSetVersion.
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-128220 · Issue 195539
Screen layout options now visible before saving a new harness
Resolved in Pega Version 7.1.8
When using a screenlayout in a harness, the options for defining the properties were not displayed. This was due to changes made to replace panel sets with screen layouts in this area, and was only an issue if the harness had not been saved yet. In order to facilitate development, these options will now also be present before saving.
SR-128228 · Issue 193947
Smoothed locking for cloud team logins
Resolved in Pega Version 7.1.8
In a large cloud team, a high number of simultaneous logins caused a requestor lock exception that required a system restart to resolve. This was caused by threads deadlocking while attempting to acquire a common resource during compilation. To resolve this, the locking has been modified to sync requests in order to ease congestion.
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-128296 · Issue 197865
Modified SOAP envelope activity to handle Axiom bug
Resolved in Pega Version 7.1.8
The version of InvokeAxis2 provided in updates was encountering a bug with Axiom's implementation for adding OMNodes and not all header elements were being mapped to their SOAP request. To resolve this, the pzAddCustomeHeaderstoSOAPEnvelope activity has been updated to add a line of code to remove a node from its child iterator once it is added.