SR-127838 · Issue 194658
Parse XML validation default set to "Never"
Resolved in Pega Version 7.1.8
In some cases, the parse XML rules function was not correctly mapping all of the input types. The root cause for the different failure modes seen was found to be that validation was set to "Always" by default, and the rule data did not reflect this until after a manual Save or Save-As. The default has now been set to "Never", and can be manually adjusted to "Always" or "When" as desired.
SR-128063 · Issue 193580
Added schema qualification to BIX / DB2 extract rules
Resolved in Pega Version 7.1.8
When using a Business Intelligence Exchange (BIX) extract rule which included writing the manifest details to external database tables, running the extract rule generated errors for the insert into the pr_extract_summary and pr_extract_details tables. This issue existed both when running from the command line and from the User Interface (UI). This was traced to the extract code not schema qualifying the pr_extract_summary and pr_extract_details tables in the insert statements, so it is expecting those tables to be in the schema of the user who is defined in the Database rule. This has been corrected through code changes for DB2 external databases that includes currentSchema=YourSchemaName in the URL connection to the external database.
SR-128118 · Issue 191010
Workbasket name updated in Case Manager portal
Resolved in Pega Version 7.1.8
When CaseManager portal was launched and any particular WorkBasket selected, the text "WORK IN XXXXX WORKBASKET" was shown. XXXXX was the WorkBasket name, which was being picked from RuleName(Identifier) instead of ShortDescription. This was unexpected, and has been changed.
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.