INC-226674 · Issue 730362
Corrected LiveDesignViewDisplay error handling
Resolved in Pega Version 8.8
When all rulesets were locked and a section was opened from Live UI in a portal, a "rule deleted" message appeared and it was confirmed the rule was deleted even though the rule was in locked ruleset. Investigation traced this to a pzLiveDesignViewDisplay call to pxChooseBestRuleSet which jumped to failure logic when "allow check out" was disabled, and this has been resolved by correcting the error handling in pzLiveDesignViewDisplay.
INC-228060 · Issue 741140
Added control for displaying Ajax popup alert for optimized iOS table
Resolved in Pega Version 8.8
When using an application on iOS with a section that contained at least 3 tables with 'optimize code allow' set to true, refreshing caused the error "AJAX request failed. Reason: communication failure" to be displayed. When a refresh is triggered, ongoing AJAX requests are cancelled, and the WebKit (OS provided) behavior is to display the "AJAX request failed" alert. To control this behavior, a check has been added for the flag pega.u.d.showAjaxFailureMessageMobile when displaying the alert popup. The default behavior is set to false and will not show the alert. To display the alert, set pega.u.d.showAjaxFailureMessageMobile = true in userworkform. The additional fieldValue "AJAX request failed" of type pyMessageLabel is created to allow configuring a custom message.
INC-228309 · Issue 732111
Mashup can be loaded from Salesforce LWC
Resolved in Pega Version 8.8
Pega Mashup was not able to be loaded from Salesforce Lightning Web Components (LWC) due to the request not being triggered to the Pega server. This has been resolved by modifying the Pega references to be compatible with Salesforce LWC.
INC-228341 · Issue 744464
Security updated for user profiles
Resolved in Pega Version 8.8
Cross-site scripting protections have been added for user profiles.
INC-228900 · Issue 738197
Archived case history is viewable
Resolved in Pega Version 8.8
Case history was not displayed for archived cases. This has been resolved by adding a section and when condition to display archived case history.
INC-228988 · Issue 742196
Handling added for custom attribute that holds a JSON string
Resolved in Pega Version 8.8
When the DX Assignments API was expected to render a view with a custom attribute that holds a JSON string, it cut the string off at a random point. This caused an error on the front-end screen and the correct view was not displayed. Investigation showed part of the json was incorrectly localized which caused it to treat some values as variables. This has been corrected by testing whether a custom attribute is JSON, and if it is it will be escaped so it is not localized or modified.
INC-229167 · Issue 734199
PD4ML upgraded
Resolved in Pega Version 8.8
Issues with PDF generation have been resolved by upgrading PD4ML to version 4.0.13.
INC-229308 · Issue 739562
ValidateInteger function added to preserve decimal properties
Resolved in Pega Version 8.8
Decimal properties were being automatically changed to integer. This occurred because the edit validate rule on any type of property did not allow decimal entry if the edit validate rule name contained "IsInteger" even if the rule contained no code. To resolve this, the validateInteger function has been added to check whether the validation type is integer.
INC-229714 · Issue 733083
ParentKey handling updated for for CS portal
Resolved in Pega Version 8.8
After creating an interaction in the CPM portal and refreshing the CPMPerformIncludes section (top-level section in the Perform harness) on button click, the focus was set to the first property and a large number of "Uncaught harness context does not exist" error appeared on the console and the screen became frozen. Analysis showed that after the refresh the parentKey property was empty, causing the flow to be executed in the wrong context. This has been resolved by adding a condition to set the parentKey for CS portal 'Add document' scenarios.
INC-229967 · Issue 735962
Number control decimal formatting triggered on tabout
Resolved in Pega Version 8.8
When using the pxNumber control in a section, decimal formatting for input of fewer than 4 digits was not executing unless a post call to the server was triggered. This has been resolved by adding a condition check to format value when there is input of length greater than 0.