SR-125143 · Issue 187274
Length limits for form URLs
Resolved in Pega Version 7.1.8
When using the out-of-the-box Other Actions button, selecting 'Refresh' caused a blank page to display and resulted in an 'ERR_CONNECTION_RESET' script error. This happened when a form submit URL including all input parameters exceeded the max length expected. The submit function has been modified to send only the required params as part of the URL, and not all hidden inputs.
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-125192 · Issue 189446
Thread Name displayed in RemoveInactiveThread API
Resolved in Pega Version 7.1.8
An enhancement has been added to display the thread name when throwing an exception during thread deletion: "You may not remove the "+aThreadName+" thread currently processing".
SR-125196 · Issue 191599
Variable added for non-English fonts in RTE
Resolved in Pega Version 7.1.8
Previously, the dropdown for font styles in pxRichTextEditor control contained only English-language fonts and did not include fonts for other languages such as Japanese. To enhance the localization, the global variable 'window.customCKEditorFonts' has been added to override 'CKEDITOR.config.font_names' when desired.
SR-125210 · Issue 189127
Customization corrected for RRHeader section of RD
Resolved in Pega Version 7.1.8
If the RRHeader section item was customized and renamed, opening Report Definition and clicking "Edit Report Title" did not produce the expected results even with the "Edit Report Title" command enabled. This was due to the RRHeader section being hard-coded; this is now loaded dynamically to allow for customization.
SR-125245 · Issue 187386
Search ability corrected for rule names containing spaces
Resolved in Pega Version 7.1.8
While a space was allowed in the rule name of a report category rule, searching for a rule name with a space generated the error "Unable to open instance Error: Can't find record". This was due to a missing JavaIdentifier validator for the "pyCategoryName" property in "Rule-Category" class, and this has been added.
SR-125254 · Issue 188703
Added Finish Assignment check for old harnesses
Resolved in Pega Version 7.1.8
After upgrade, a failing post flow action validation created the inability to correct the errors and resubmit using a pxButton which performed an out of the box "Finish Assignment." When trying to do so, a busy indicator was displayed and the application froze. This was caused by an incorrect legacy harness pointer for the Action section. A check for old harnesses has been added, and the submit API now sets the target of form submit for finish assignment to the parent window.