SR-122305 · Issue 181630
Resolved addition of extra lines added upon RTE save
Resolved in Pega Version 7.1.8
After pasting some text (paragraph) content into the out-of-the-box RTE control and saving, new lines were inserted between paragraphs and again every time the save button was clicked, adding more lines. This was caused by a missing redundancy check within the RTE control code that is used to replace '/n' (new lines) with
in order to incorporate proper indentation when the text area is upgraded to RTE. Changes have been made to handle the carriage return case properly.
SR-122305 · Issue 183086
Resolved addition of extra lines added upon RTE save
Resolved in Pega Version 7.1.8
After pasting some text (paragraph) content into the out-of-the-box RTE control and saving, new lines were inserted between paragraphs and again every time the save button was clicked, adding more lines. This was caused by a missing redundancy check within the RTE control code that is used to replace '/n' (new lines) with
in order to incorporate proper indentation when the text area is upgraded to RTE. Changes have been made to handle the carriage return case properly.
SR-122393 · Issue 183981
Fixed error with importing a complex column layout
Resolved in Pega Version 7.1.8
After upgrading, a layout with a large number of columns was causing an error due to a conditional piece of Java code not being properly initialized. This has been corrected.
SR-122393 · Issue 182288
Fixed error with importing a complex column layout
Resolved in Pega Version 7.1.8
After upgrading, a layout with a large number of columns was causing an error due to a conditional piece of Java code not being properly initialized. This has been corrected.
SR-122393 · Issue 183524
Fixed error with importing a complex column layout
Resolved in Pega Version 7.1.8
After upgrading, a layout with a large number of columns was causing an error due to a conditional piece of Java code not being properly initialized. This has been corrected.
SR-122399 · Issue 183836
Missing 'defer load' option replaced
Resolved in Pega Version 7.1.8
Due to an error, the 'Defer load contents' option was missing from sections created with an embedded Tab Group. This has been fixed.
SR-122409 · Issue 182081
Refresh when active' tabs no longer affecting other tabs
Resolved in Pega Version 7.1.8
A tab using the 'Refresh when active' setting, could cause the content of other non auto refreshing tabs to re-execute. E.g. Report Definitions that are sourcing repeat grids in other tabs. This occurred when using the 'Refresh when active' setting on a tab whose content is a Dynamic Layout (the out-of-the-box default when adding a tab) with an embedded section. There was a local workaround of updating tabs to use the required section as the top level content rather than using a dynamic layout with an embedded section, and this has now been incorporated into the software. The refresh when active setting is still available in this configuration.
SR-122413 · Issue 182457
Corrected button disable failure for values starting with '0'
Resolved in Pega Version 7.1.8
The button disable condition was failing for string values proceeded with zeros. To resolve this, the evaluate function of pega_ui_doc now has a check to not execute the parsefloat in cases of string and zero values.
SR-122451 · Issue 184656
Smoothed multi-access group switching
Resolved in Pega Version 7.1.8
In the user portal, there is an option to change the access group to switch between the applications. There was no problem changing the access group the first time, but after creating a work object it was not possible to change the access group again. This was caused by the NavigationHeading - Changes table-layout CSS property value being set to "auto" , and the handleWidgets method has been changed to use the getAttribute method instead.
SR-122481 · Issue 189776
Issue with layout visibility condition expression formatting corrected
Resolved in Pega Version 7.1.8
After migration, the layout visibility condition expression was not working when given a value starting with zero in quotes (e.g. .tansactionstatuscd=='014'), although removing the single quotes or the zero caused the rule to evaluate to true. Previously, expressions were evaluated on the server side only but recent architecture changes moved this to the client side where such expressions were not supported. In order to ensure correct behavior, single quotes will be removed rom the given visible 'when' condition so the evaluation returns the expected result.