SR-122839 · Issue 185954
Audit entries properly suppressed
Resolved in Pega Version 7.1.8
Audit entries were being added to the history even after suppressing the same in the DT "FilterHistory" of the respective interaction class. When the "RemoveAssignmentByTicket" function called the activity "AddWorkHistory", the parameter workPage was not being sent. Because the system skipped the call to the decision tree, it was returned as 'true' each time. To resolve this, the system now passes "WorkObjectPageName" to ensure proper evaluation.
SR-124004 · Issue 186135
Timing improved for delegated strategy rule editing
Resolved in Pega Version 7.1.8
After saving a strategy rule to an unlocked production ruleset and adding that version to My Favorites, it was not possible to checkout the rule. When the refresh/reload button (only button displayed on the rule toolbar) was clicked, a StringIndexOutOfBoundsException message was generated. The root cause was a timing issue due to system slowness that prevented the display of the toolbar icons, and code has been implemented to increase the timeout for 'openRuleINprogress'.
SR-125148 · Issue 178077
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-125148 · Issue 178317
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-125148 · Issue 192416
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-125148 · Issue 193504
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-127838 · Issue 194007
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-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-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-126980 · Issue 192477
Chart control validation updated to handle aggregate functions
Resolved in Pega Version 7.1.8
When a chart control contained a Report definition with COUNTDISTINCT in the summarize field, the chart was not displayed at runtime. Manually executing the Report Definition displayed the data and the pie chart as expected. This was found to be an issue with chart control not rendering the chart at run time if the underlying RD source contained an aggregate function. To correct this, the pzIsChartReportColumnValid validate rule has been updated.