SR-
116448 · Issue 166844
SOAP settings updated to work with IBM JDK 1.7
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
When calling Service SOAP hosted on Websphere 8.5+ and JDK 1.7, the SOAP client was failing with a java.lang.VerifyError. This was traced to a change in the settings necessary for use with IBM JBK 1.7, and the needed properties have been updated.
INC-144311 · Issue 601108
Updates for nested "Append And Map To"
Resolved in Pega Version 8.5.2
Nested actions "Append And Map To" in Data Transforms were producing incorrect results when offline. This was traced to all operations being performed on the Page List which was on first level of nesting, which was caused by changing the Data Transform into JavaScript form for offline use. The JavaScript form of DataTransform uses variable the "targetListObj" to represent the Page List, and this same name was reused regardless of the "Append And Map To" nesting. An additional problem was seen with the "Update Page" Data Transform action when used with conjunction with a nested "Append And Map To" action: the action assumes that top level Pages exists, but "Update Page" did not create them. This caused the "Append And Map To" action to fail. To resolve this, the "Append And Map To" action will use suffixed variable names to reference nested PageLists, and "Update Page" will create the Page if it doesn't exist.
SR-117752 · Issue 171493
Changed decimal values to comma values for NL/SE localization
Resolved in Pega Version 7.1.7
The Dutch and Swedish convention for decimals is to use a comma as the separator instead of a dot. This use was not included in the localization so clicking on submit caused the comma values to be converted with a decimal point that multiplied the value by 100. (1200,00 is twelve hundred euros; the value became 120,000.00 - one hundred and twenty thousand euros) This has been fixed so the values are correctly handled with commas when localized to NL or SE.
SR-119243 · Issue 175219
Changed decimal values to comma values for NL/SE localization
Resolved in Pega Version 7.1.7
The Dutch and Swedish convention for decimals is to use a comma as the separator instead of a dot. This use was not included in the localization so clicking on submit caused the comma values to be converted with a decimal point that multiplied the value by 100. (1200,00 is twelve hundred euros; the value became 120,000.00 - one hundred and twenty thousand euros) This has been fixed so the values are correctly handled with commas when localized to NL or SE.
INC-132569 · Issue 595174
Resolved case detail overwrite
Resolved in Pega Version 8.5.2
In the interaction portal, when the same property (dropdown) was used to populate the details of sections in two cases, the first section (email case) details were replaced by the second section (outbound call case) details. Investigation showed that the refresh API was getting the reloadElement in the entire DOM based on the event target name property. To resolve this, updates have been made to use context DOM APIs to get the correct section.
INC-153805 · Issue 627969
Mobile app language remains consistent after data sync
Resolved in Pega Version 8.5.3
When using a Field Service Mobile App where the locale of all workers was set to nl_NL, the UI was intermittently flipping from NL to EN and and back again. This was traced to the locale of the requestor (field worker) being lost during synchronization of the mobile app data to the server, causing the UI to fall back to the default value of EN. This has been resolved by ensuring the requestor always uses the chosen locale for the operator.
INC-157699 · Issue 624596
Customer 360 Tabs load in Firefox browser
Resolved in Pega Version 8.5.3
After upgrade from v8.1 to v8.4, the layout group's tab content was not loading as expected in the customer 360 view when using the Firefox browser. Investigation showed this was due to the �role� attribute being removed from the header div by the on-hover showSmart tip action configured on the dynamic layout tabs. This has been resolved by updating the system to use data-role along with the role tab.
INC-139086 · Issue 597146
"Show next error" correctly displayed on user portal
Resolved in Pega Version 8.5.3
In the Case Worker user portal, the Show Next Error link was not shown when the layout group had a validate rule in the flow action. The same configuration worked as expected in Case Manager. This was a missed use case, and has been resolved.
INC-144778 · Issue 619615
Performance improvements for Ajax tab switching
Resolved in Pega Version 8.5.3
When using a 360-view of members in a portal implemented with an Ajax container that showed information in multiple tabs, tab switching was taking a lot of time even though the data was already in the memory. Updates have been made to improve performance.
INC-157041 · Issue 626312
Performance improvements for email listener processing
Resolved in Pega Version 8.5.3
Email processing was taking an excessive amount of time when a very large number of email listeners were running. Performance has been improved by updating the implementation of pzGetChannelByName to use obj-browse instead instead of looping through channels.