SR-128829 · Issue 180467
Added multi-class localization for DisplayRFHarnessErrors
Resolved in Pega Version 7.1.8
When Rule DisplayRFHarnessErrors was in two different classes, @baseclass and Rule-Obj-Flow, the localization check box was previously only available under @baseclass and not for Rule-Obj-Flow. This has been updated so the marked rule in rule-obj-flow is also localized when checked under @baseclass.
SR-128829 · Issue 193680
Added multi-class localization for DisplayRFHarnessErrors
Resolved in Pega Version 7.1.8
When Rule DisplayRFHarnessErrors was in two different classes, @baseclass and Rule-Obj-Flow, the localization check box was previously only available under @baseclass and not for Rule-Obj-Flow. This has been updated so the marked rule in rule-obj-flow is also localized when checked under @baseclass.
SR-128834 · Issue 192690
Corrected dynamic select refresh behavior
Resolved in Pega Version 7.1.8
When a Dynamic select with "OnChange + refresh" was configured, the values in dynamic selects were not retained after a refresh in the Google Chrome and Firefox browsers. This occurred most often when selecting a value for a second dynamic select box caused a refresh and forced the previously selected value to be lost from the first box. The values were reset to "Select.." and the drop values were also not populated. The root cause of this problem was trailing white spaces in the values returned by the service that populated the dynamic select. While Microsoft Internet Explorer automatically trimmed these spaces, Google Chrome and Firefox did not. This has been corrected by trimming results when getting data from xml in the DynamicSelect JavaScript file.
SR-128834 · Issue 193912
Corrected dynamic select refresh behavior
Resolved in Pega Version 7.1.8
When a Dynamic select with "OnChange + refresh" was configured, the values in dynamic selects were not retained after a refresh in the Google Chrome and Firefox browsers. This occurred most often when selecting a value for a second dynamic select box caused a refresh and forced the previously selected value to be lost from the first box. The values were reset to "Select.." and the drop values were also not populated. The root cause of this problem was trailing white spaces in the values returned by the service that populated the dynamic select. While Microsoft Internet Explorer automatically trimmed these spaces, Google Chrome and Firefox did not. This has been corrected by trimming results when getting data from xml in the DynamicSelect JavaScript file.
SR-120412 · Issue 178850
Flow actions 'ResumeProblemFlow' and 'RetryProblemFlowFromstart' have been correctly marked as being unavailable for bulk processing
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.8
The Flow Problems flow actions 'ResumeProblemFlow' and 'RetryProblemFlowFromstart' are marked as being available for bulk processing which gives the impression they could be used to perform a bulk process operation when actually it is not possible. Each of these flow actions reference the same HTML Work- ActionDisplayError instance which is configured on the expectation that a specific value for pyFlowInError will be present on the newAssignPage, and this is the case when using the bulk processing approach via the portal. Therefore, this configuration has been marked as unavailable for bulk processing to avoid any future confusion. There is an alternative and recommended means by which bulk operations can be performed on assignments in the FlowProblems flow by using the "Flow Errors" list under the "Process and Rules category ? Processes" landing page. Please review the PRPC Help topic "Help: Working with the Flows with Problems report" for additional details.
SR-126107 · Issue 189620
"Previous" button now navigates to correct index
Resolved in Pega Version 7.1.8
After correcting a validation error while enabling buttons in a repeating grid, the "Previous" button was navigating to the wrong index, skipping rows in between instead of displaying details for the immediately previous item. The "Next" button worked correctly. This was caused by an error in success callback where "grid.activeRow" was updated to the wrong index when the rows above were expanded, and has been fixed.
SR-130181 · Issue 201836
Modified Dropdown to return JSON content type for use with ISAM
Resolved in Pega Version 7.1.8
ISAM, a third-party tracking layer, embeds JavaScript code in text/html responses. The Dropdown control was returning JSON but in HTML content type, so sites that use ISAM found that the ISAM JS code was embedded and the Pega JS that parses the JSON response failed to execute. Changes have been made to the wrapper to ensure the desired behavior of Pega returning application/json content type for JSON responses instead of text/html.
SR-130181 · Issue 197628
Modified Dropdown to return JSON content type for use with ISAM
Resolved in Pega Version 7.1.8
ISAM, a third-party tracking layer, embeds JavaScript code in text/html responses. The Dropdown control was returning JSON but in HTML content type, so sites that use ISAM found that the ISAM JS code was embedded and the Pega JS that parses the JSON response failed to execute. Changes have been made to the wrapper to ensure the desired behavior of Pega returning application/json content type for JSON responses instead of text/html.
SR-130302 · Issue 197285
Focus switch corrected for multiple actions on a button
Resolved in Pega Version 7.1.8
When multiple actions like CreateNewWork and Cancel were configured on a button, clicking on the button opened a new tab but focus was not moved to the new tab. This unexpected behavior was caused by the dynamic container's MRU object not getting updated correctly when multiple actions were performed. This has been resolved by updating the logic for the updateItemMRUCache API in dynamicContainer.Js.
SR-130302 · Issue 198340
Focus switch corrected for multiple actions on a button
Resolved in Pega Version 7.1.8
When multiple actions like CreateNewWork and Cancel were configured on a button, clicking on the button opened a new tab but focus was not moved to the new tab. This unexpected behavior was caused by the dynamic container's MRU object not getting updated correctly when multiple actions were performed. This has been resolved by updating the logic for the updateItemMRUCache API in dynamicContainer.Js.