SR-122176 · Issue 184992
Older button visibility conditions retained after upgrade
Resolved in Pega Version 7.1.8
After migration, older button controls set to visibility "ALWAYS" and when condition "canPerform" became visibility "WHEN" and when condition "canPerform". To resolve this, the logic for the activity Embed-Harness-Section!UpgradeOnOpen has been updated to check for "VISIBILITY" first before "visible when" to retain the proper settings.
SR-122215 · Issue 180037
Resolved installation errors for DB2 Z/OS with WebSphere
Resolved in Pega Version 7.1.8
A problem was encountered while installing split schema on a DB2 z/OS system with WebSphere. This was caused by an erroneous system setting where the ports to the DB2 database were not open in this environment. While the Admin could correct the environment to open the ports and allow the application server node to connect to the DB2 database, this has been changed in the software to default to the correct settings.
SR-122264 · Issue 182315
Preview Included Section corrected for Case Manager portal
Resolved in Pega Version 7.1.8
The Section Include preview feature was implemented with support in the Developer Studio, but was found to not be working as expected in the Case Manager Portal. This was due to a wrong 'if' condition for span identification, and the system has been updated.
SR-122292 · Issue 182878
Operators and Access Groups are now automatically force re-indexed during import
Resolved in Pega Version 7.1.8
If a number of new OperatorIDs were created and added to two workgroups and then the changes were exported, the new OperatorIDs were present when the file was imported to other environments but a query run against the table PR_INDEX_OPERATOR_WORKGROUP did not incorporate the new IDs. While there was a workaround of manually forcing a re-index during import to fully incorporate the new IDs, the Operators and Access Groups are now automatically force re-indexed during import to ensure data is up to date.
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-122314 · Issue 178491
Resolved installation errors for DB2 Z/OS with WebSphere
Resolved in Pega Version 7.1.8
A problem was encountered while installing split schema on a DB2 z/OS system with WebSphere. This was caused by an erroneous system setting where the ports to the DB2 database were not open in this environment. While the Admin could correct the environment to open the ports and allow the application server node to connect to the DB2 database, this has been changed in the software to default to the correct settings.
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.