SR-D50161 · Issue 514875
Auto populate disabled during redux page conversion to prevent concurrent modification exception
Resolved in Pega Version 8.1.7
Running a standalone data page sourced from a look up of a class was failing sporadically with a concurrent modification exception. The Data page was backed by redux pages: this meant that when the page fetched from data source was converted to redux page, it was iterating through all properties in the mContent of the page and trying to convert those to redux properties. During this process, when any auto populate property was encountered it was getting triggered and modifying the mContent, resulting in a change in iterator. As a result, when the Iterator was trying to fetch the next element, the concurrent modification exception was thrown. To resolve this issue, auto populate has been disabled during redux page conversion to avoid unnecessary problem during data page load.
SR-D29034 · Issue 500682
Added support for JSON mapping of deep nested pagelist objects
Resolved in Pega Version 8.1.7
An exception occurred when using a JSON data transform in the service activity to map the clipboard data to JSON on the third level of a structure formed as Pagelist-->page-->pagelist. To resolve this, support has been added for nested pagelist mapping with deep nesting of objects (configured for one sided actions) and arrays.
SR-D38931 · Issue 507058
Support added for Multiple Set-Cookies in Connect REST
Resolved in Pega Version 8.1.7
When using a REST connector, the service returned multiple cookies as separate Set-Cookie response headers, but only the last header value received was stored when using pzResponseHeaderMap on the parameter page. In order to support this use, changes have been made to store multiple header values from Connect-REST responses.
SR-D18853 · Issue 503274
Visibility on client check removed to enable Pulse on click
Resolved in Pega Version 8.1.7
When Pulse was configured on click of a icon, the comment section was not visible. Investigation showed that at the time of DOM load, pyMessage property was not available in the DOM because 'Run visibility condition on client' was checked by default. Visibility on client checks have been removed to resolve this issue.