INC-226000 · Issue 728651
Table column sizing working as expected for end users
Resolved in Pega Version 8.8
In optimized grid columns where a section was embedded in the cell with a button, the column size was not set as expected with default/short table density. These columns were truncated for end users even though the truncation did not happen for operators/users in the dev access group. This was due to the DOM structure that is loaded for the end user being different from the DOM structure loaded for the dev user, which resulted in a few styles not being applied to the end user. To resolve this, a new property has been added to apply the CSS properly for a column with section, button or icon.
INC-226272 · Issue 740937
Close button dirtypopup corrected
Resolved in Pega Version 8.8
After update, the Close button dirtypopup was not working in the case worker portal. This has been resolved by modifying the dirtyhandling and actionrouter files.
INC-226386 · Issue 741133
Ensure field level server side validation messages cleared
Resolved in Pega Version 8.8
A validation message was retained when not required. This was traced to a scenario where there were two server side validation messages on the decimal field in addition to a required client side validation condition; on text change of the decimal field, the server side validation persisted and client side validation replaced only the first message. This has been resolved with an update which will remove field level server side validation messages after client side validation on an event trigger.
INC-226588 · Issue 720903
EncryptURLActionString changed from Thread to Requestor scope
Resolved in Pega Version 8.8
The static content cache was growing rapidly. This was traced to pzClientApplicationData creating a new set of applicationdata.js files for every tab thread opened. To resolve this, and update has been made which changes pzEncryptURLActionString to use Requestor scope instead of Thread in pzclientapplicationdata.
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.