INC-213625 · Issue 712296
Corrected null values being set to 0 in GenerateExcel
Resolved in Pega Version 8.7.2
The pxGenerateExcelFile activity was loading $0.00 in place of a null value for decimal columns. This has been resolved by updating the logic for GenerateExcel.java to skip double properties default value for non-existent clipboard props and extend the same fix to the integer class. Safety checks have been added before setting cell type to check if property exists, and handling has been added for a specific exception instead of generic exception for both decimal and integer use cases.
INC-213918 · Issue 714452
Discard button works consistently
Resolved in Pega Version 8.7.2
After check out, the discard button was not working consistently for decision tables or MapValue. Investigation showed this occurred when an exported file was being downloaded in the same window, as the thread would be busy with the file and not able to perform the discard action on the window. To resolve this, the configuration for the download on the same window has been removed, exportToDecisionTable has been modified to handle an iframe, and a runScript action has been added to register the exportToExcel activity and download in iframe.
INC-216935 · Issue 714047
Corrected decision table scroll bar display in resized section
Resolved in Pega Version 8.7.2
Resizing a decision table window was causing the horizontal scroll bar to move out of the section while scrolling. This has been resolved by updating the HTML and adding the needed CSS.
INC-217991 · Issue 714331
Display of 'check all' check box made configurable
Resolved in Pega Version 8.7.2
A new overridable 'when' rule pyShowSelectAllCBInSurvey has been added to allow customizing a survey to hide the 'Select all' checkbox in the ComplexQuestionCheckboxTemplate section.
INC-191371 · Issue 684481
Security update for GetAssignmentDetailsInternal errors
Resolved in Pega Version 8.8
Error handling for pzGetAssignmentDetailsInternal has been updated to return a 403 (forbidden) HTTP status code in place of potentially sensitive information when access is denied.
INC-193700 · Issue 685077
Support added for calling Strategy rule from When Rule
Resolved in Pega Version 8.8
An enhancement has been added to support manually referencing Strategy rules in the When rules using Dev studio.
INC-194330 · Issue 708712
Added special character handling for DecisionTable column-label
Resolved in Pega Version 8.8
The label of a decision-table column was being appended to the original decision-table return-value. The column label and comparator were handled differently for columns containing special characters (+, -, *,...), causing the data after the special character to be trimmed and appended to the row output value. This has been resolved by adding handling for special characters so the output and the label are rendered properly.
INC-195793 · Issue 697920
Enhanced ruleset validation for portal creation
Resolved in Pega Version 8.8
Attempting to create a new portal (web channel) from the app studio using the Creation Wizard with "Branch development preferences" enabled resulted in the error message "No valid rulesets in application preferences". Investigation showed this occurred due to CPM-Portal being specified in the application as the UI class: when attempting to create the portal, the system was evaluating the class against ruleset candidates. The class was not visible to the rulesets in the stack and thus the portal could not be created. This has been resolved by adding validation on UI pages, Int and Data classes in the application to ensure that they exist in user rulesets, and by adding an allowance for classes to exist only in branched rulesets and not the base ruleset during check if the ruleset is present in application stack.
INC-202249 · Issue 693323
Corrected doubled ampersand passed to message rule
Resolved in Pega Version 8.8
In drop down the ampersand "&" symbol was displayed correctly, but passing that value as a parameter to a message rule used in the page-set-messages method doubled the "&" symbol. This has been resolved.
INC-205666 · Issue 702935
Database table correctly prevents deletion if there are descendant classes
Resolved in Pega Version 8.8
When deleting a concrete class with descendant classes via an activity (Rule-.Delete), the Rule-Obj-Class.ValidateDeleteInternal activity was throwing an error message indicating the class could not be deleted due to descendant classes. However, the corresponding database table rule was deleted anyway. Investigation showed this was caused by ValidateDeleteInternal not reaching the Obj-Save-Cancel step. This can be fixed by modifying step 11, the post when conditions, to jump to END and set the END label at the Obj-Save-Cancel step instead Exit-Activity, but this issues has been resolved by updating all failure states to run end step. In addition, security has been updated to disallow "Allow invocation from browser".