SR-109470 · Issue 166330
Listview joins corrected for multiple classes with the same name
Resolved in Pega Version 7.1.7
Running a listview with join which contains same name column in the "Get these fields" from Applies-to class and joined class was not working correctly; the property from the joined class was exposed whereas the one from Applies-To class was pulled from the blob column. To correct this, the SQL generation logic has been modified to maintain correct order (unexposed properties followed by exposed).
SR-112935 · Issue 166182
Repeating grids enhanced to allow the '&' character as text
Resolved in Pega Version 7.1.7
When values in a repeating grid contained the character "&", the ReloadSection activity failed with an illegal argument tracer and no values were passed to a second Repeating Grid Page List. This was traced to '&' being used by the system to perform a split of value string. In order to allow use of the '&' character in the list values field, it will now be encoded so it is passed without evaluation.
SR-113396 · Issue 162534
Smoothed background Bulk Processing processing
Resolved in Pega Version 7.1.7
If the setting for BPUnitsToProcessForeground is given as 0 in all cases, attempting to run Bulk Processing in the background failed and logged an "Index out of bound" exception in the system logs. To cover this condition, a check has been added to handle zero items in the foreground processing when running background Bulk Processing.
SR-113919 · Issue 170809
Made page displays consistent between Java versions
Resolved in Pega Version 7.1.7
"pxflow" pagegroup values in pywork page were being placed differently depending on the version of Java used in the environment. This was caused by a handling error in situations where there is no classname, and has been fixed.
SR-
118589 · Issue 171900
Corrected locking for custom Access Roles
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
After adding a custom Access Role to an Object in the WO class with an Access When rule defined to allow opening a instance, Obj-Open-By-Handle failed to lock the work item correctly and two operators could have it open simultaneously. This was caused by the custom stack inheriting parent state for all members, and has been changed.
SR-114882 · Issue 164513
Validation error display corrected for screen flow harness
Resolved in Pega Version 7.1.7
Inconsistencies were appearing in the error display on the harness of the screen flow. The issue was due to the "Allow errors" value being set to true even when "Save on last step" was unchecked. While there was a workaround of unchecking both "Allow errors" and "Save on last step" options, this has been fixed.
SR-115166 · Issue 169266
Embedded list views enabled in IAC
Resolved in Pega Version 7.1.7
While using IAC to render a PRPC harness via a gadget, the embedded list view was not being displayed and autocomplete was not functioning. This was traced to a rule defect that failed to carry over the "Web Enabled" checkbox for the content tab shortcut listview.
SR-115387 · Issue 164437
Flow Action support tuned for MenuBar keyboard navigation
Resolved in Pega Version 7.1.7
Using the' MenuBar' setting to display the flow actions for pyActionArea was not working as expected with keyboard navigation within the "other actions" menu: the Up/Down keys moved the cursor, but pressing the Enter key did not fire any actions because a mouse click was expected. An enhancement has been added to the logic to support an enter key event for menu items. In addition, the "other actions" menu was not accessible with keyboard navigation from the Resolve Flow action. This has been corrected.
SR-
114971 · Issue 164164
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.
SR-
114971 · Issue 165871
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.