SR-D12297 · Issue 483685
Added support for anonymous objects in a nested JSON Data Transfer
Resolved in Pega Version 8.1.6
Calling a inner Data Transfer from an outer Data Transfer (both of type JSON) was generating an exception. This exposed an edge case in JSON mapping related to a condition where an object's field value was an array that included anonymous objects. The code maintains its "place" in the JSON structure partly by means of a "jsonContext" structure that names every object (but not any array or anonymous object) it is inside of, which is key to the serializer's ability to flatten nested clipboard structures in the JSON or conversely expand flat clipboard structures into nested JSON structures. In addition, there is a "structureStack" that shows how deep the function is in terms of OBJECT and ARRAY elements. The code uses the indices into these two structures to determine whether to pop out of one or the other, and in this scenario, when a field's value was an array containing an anonymous object, closing the array was causing the outermost object to be closed, thus leading to the exception when the system tried to continue to serialize. To resolve this, when closing an array, the system will check whether the parent of the array had the same name as the last position in the jsonContext, and if so, pop the jsonContext.
SR-D25278 · Issue 499448
Enhanced logging for Clipboard JSON Deserializer
Resolved in Pega Version 8.1.6
An enhancement has been made to introduce a number of logger events to the Clipboard JSON Deserializer in order to have sufficient data to diagnose any issues encountered.
SR-D24497 · Issue 496468
Removed duplicated Cross-site scripting filtering
Resolved in Pega Version 8.1.6
Some specific special characters ( "(" , ")", "%" , "&" ) in Delegated View of Data Type rules are not displayed properly in Edit view. Investigation showed the parameter value was subject to multiple passes of cross-site filtering, and the unneeded Cross-site scripting filters have been removed.
SR-D12337 · Issue 482881
Removed duplicated Cross-site scripting filtering
Resolved in Pega Version 8.1.6
Some specific special characters ( "(" , ")", "%" , "&" ) in Delegated View of Data Type rules are not displayed properly in Edit view. Investigation showed the parameter value was subject to multiple passes of cross-site filtering, and the unneeded Cross-site scripting filters have been removed.
SR-D5126 · Issue 487187
Corrected active state selector for IOS devices
Resolved in Pega Version 8.1.6
When scrolling RDL, gray artifacts were observed which did not always disappear from the UI. This was traced to the background color being applied wrongly due to an incorrect selector for active state in the layout that resulted in the gray region being visible. To resolve this, the selector has been updated to target only non-IOS devices for active state.
SR-D24318 · Issue 494059
Dom API updated to resolve Microsoft Internet Explorer 11 not loading async data with refresh when
Resolved in Pega Version 8.1.6
The browser was continuously showing "loading" if Microsoft Internet Explorer 11 was used for a section which was sourced from a data page and configured to load the data asynchronously from a external service while calling an activity and using a 'refresh when' rule to refresh the section if a property changed. Investigation showed that the initial data load was successful and the section with the data was visible, but if the property changed and the section loaded once again due to the 'refresh when' condition, the browser was unable to render the defer loaded section case because the dom returned had the wrong value. To resolve this, the API used to check for the dom element has been updated.
SR-D16074 · Issue 485882
Additional language options added to Language Wizard dropdown
Resolved in Pega Version 8.1.6
An enhancement has been added to the “select a language” dropdown in the Language Wizard that extends the available options to include Latin American Spanish (es_XL), Brazilian Portuguese (pt_BR), and Korean (ko_KR).
SR-D17418 · Issue 498722
Attached note header displays properly in Hebrew locale
Resolved in Pega Version 8.1.6
With the locale set to Hebrew, the whole portal is presented correctly from right to left, but when opening a case note (attached email) the header was not displayed as right to left. This has been resolved by updating the 'DisplayNote' HTML of class 'Data-WorkAttach-Note' and 'Show' HTML of class 'Data-Corr-Email' to use locale information from the operator.
SR-C96680 · Issue 483764
Reject changes in approvalRuleChanges flow will clear cache and reassemble rules
Resolved in Pega Version 8.1.6
When a paragraph rule with "need approval" checked in the ruleset version was delegated, previewing the data in the paragraph rule via a button and making changes worked as expected. However, after the changes were made and sent to the approver to accept or reject the changes and the private copy was deleted, it was observed that rejected changes still showed in the paragraph rule and the cache was not cleared. The Rule Approval process allows checkouts to be approved or rejected: when not using rule approval process, a Checkin from the personal ruleset results in a Delete operation (from WBCheckIn & RuleCheckIn) that will remove the rule from the personal ruleset. However, with Rule Approval process setup, the rule in the personal ruleset is not deleted. Instead it is simply moved to the CheckInCandidates ruleset. The pyRuleset on the rule page changes, but the Inskey remains the same. Because there was no delete operation, there was no noteChange event and the cache was not cleared. To resolve this, the system has been updated to now enable NoteChangeInternal to invalidate rules that are part of the personal ruleset only if they have the correct setting in their prconfig.xml. This fix also forces re-assembly of rules after check-in and approve/reject so that pressing preview will ensure the correct rule gets displayed.
SR-D22210 · Issue 496435
Submenu is correctly hidden
Resolved in Pega Version 8.1.6
While creating any new case item from the navigation menu, the menu was not displaying the actual list of options after selection. Instead, it remained in the expanded menu form. This was traced to an incorrect menu status due to an error in checking the value and has been corrected.