SR-130695 · Issue 200024
Added handling for "(" and ")" in parameter value
Resolved in Pega Version 7.1.8
A backwards compatibility issue was found in the declare expression ruleform where if a parameter passed to a function alias contained ")" or "(", the data was not shown in the UI. This has been fixed by modifying the parsing logic to handle cases where parameters passed to the function alias might have an unexpected format such as "(" inside a parameter's value.
SR-130695 · Issue 200339
Added handling for "(" and ")" in parameter value
Resolved in Pega Version 7.1.8
A backwards compatibility issue was found in the declare expression ruleform where if a parameter passed to a function alias contained ")" or "(", the data was not shown in the UI. This has been fixed by modifying the parsing logic to handle cases where parameters passed to the function alias might have an unexpected format such as "(" inside a parameter's value.
SR-131162 · Issue 201045
Corrected inheritance for Data classes
Resolved in Pega Version 7.1.8
After migration, an API used to pull the list of concrete classes from RootClass Work- was pulling an additional class (Data-Portal-Padportal) when work- was supplied as an argument for rootclass. This additional class caused issues with reports due to it pointing to pr_history_data table and looking for non-existent columns. These inheritance issues have now been corrected.
SR-131162 · Issue 201046
Corrected inheritance for Data classes
Resolved in Pega Version 7.1.8
After migration, an API used to pull the list of concrete classes from RootClass Work- was pulling an additional class (Data-Portal-Padportal) when work- was supplied as an argument for rootclass. This additional class caused issues with reports due to it pointing to pr_history_data table and looking for non-existent columns. These inheritance issues have now been corrected.
SR-131567 · Issue 202155
Corrected grid overlap issue with Microsoft Internet Explorer 8
Resolved in Pega Version 7.1.8
When using the Microsoft Internet Explorer 8 browser, RTE was overlapping the content below when height was specified as 'Size to Content'. This was caused by browser reflow issues in Microsoft Internet Explorer 8 and has been corrected by triggering reflow on resize of the auto-grow RTE. However, please note that Microsoft Internet Explorer 8 will not be supported beyond this release.
SR-131567 · Issue 202062
Corrected grid overlap issue with Microsoft Internet Explorer 8
Resolved in Pega Version 7.1.8
When using the Microsoft Internet Explorer 8 browser, RTE was overlapping the content below when height was specified as 'Size to Content'. This was caused by browser reflow issues in Microsoft Internet Explorer 8 and has been corrected by triggering reflow on resize of the auto-grow RTE. However, please note that Microsoft Internet Explorer 8 will not be supported beyond this release.
SR-131723 · Issue 199975
Resolved RD header alignment
Resolved in Pega Version 7.1.8
When given a requirement to have a fixed size of 250 rows in a Report Definition (RD), selecting the "Do not scroll header" option caused the alignment of the header to be lost. This has been corrected.
SR-131723 · Issue 200028
Resolved RD header alignment
Resolved in Pega Version 7.1.8
When given a requirement to have a fixed size of 250 rows in a Report Definition (RD), selecting the "Do not scroll header" option caused the alignment of the header to be lost. This has been corrected.
SR-127827 · Issue 197318
Fixed RTE Japanese font size issue
Resolved in Pega Version 7.1.8
When Japanese text was copied from a Word doc and pasted into an RTE document, it resulted in irregular fonts appearing. This was caused by a logic bug in the paste function which removed the empty spans and made the html fragment incomplete. This has been corrected.
SR-127827 · Issue 196381
Fixed RTE Japanese font size issue
Resolved in Pega Version 7.1.8
When Japanese text was copied from a Word doc and pasted into an RTE document, it resulted in irregular fonts appearing. This was caused by a logic bug in the paste function which removed the empty spans and made the html fragment incomplete. This has been corrected.