SR-116397 · Issue 166042
Ensured cleanup utility does not unexpectedly remove rulesets
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
When the rule cleanup utility ran the statement "DELETE FROM pr4_rule_ruleset WHERE PYRULESETVERSIONID
SR-116397 · Issue 166235
Ensured cleanup utility does not unexpectedly remove rulesets
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
When the rule cleanup utility ran the statement "DELETE FROM pr4_rule_ruleset WHERE PYRULESETVERSIONID
SR-117788 · Issue 160084
Support added for Alternate Domain URLs
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
Open URL' in a window action configured in a navigation rule was not passing on configured parameters in the alternate domain URLs. Support has been added to pass on the parameters if an alternate domain is used with openUrlInWindow action in an old menu.
SR-117788 · Issue 172850
Support added for Alternate Domain URLs
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
Open URL' in a window action configured in a navigation rule was not passing on configured parameters in the alternate domain URLs. Support has been added to pass on the parameters if an alternate domain is used with openUrlInWindow action in an old menu.
SR-118369 · Issue 169422
Resolved missing Datatype issue for report definition resolution
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
After migration, the error "No enum const class com.pega.pegarules.data.external.rd.constants.ColumnType.FLOAT" occurred during the resolution of the report definition. This was caused by a missing Datatype, and support for Datatype Float has been added for external db column types.
SR-118369 · Issue 170799
Resolved missing Datatype issue for report definition resolution
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
After migration, the error "No enum const class com.pega.pegarules.data.external.rd.constants.ColumnType.FLOAT" occurred during the resolution of the report definition. This was caused by a missing Datatype, and support for Datatype Float has been added for external db column types.
SR-119803 · Issue 171111
Corrected copying pages containing autopopulated properties
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
When the clipboard viewer copied a page from a given thread to its own thread to show it in the clipboard, an exception was generated if the page being copied contained an autopopulate property. To remedy this, autopopulate and reference property functionality have been changed to allow copying when declarative processing is disabled in a thread.
SR-119803 · Issue 174193
Corrected copying pages containing autopopulated properties
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
When the clipboard viewer copied a page from a given thread to its own thread to show it in the clipboard, an exception was generated if the page being copied contained an autopopulate property. To remedy this, autopopulate and reference property functionality have been changed to allow copying when declarative processing is disabled in a thread.
SR-119803 · Issue 175017
Corrected copying pages containing autopopulated properties
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
When the clipboard viewer copied a page from a given thread to its own thread to show it in the clipboard, an exception was generated if the page being copied contained an autopopulate property. To remedy this, autopopulate and reference property functionality have been changed to allow copying when declarative processing is disabled in a thread.
SR-109470 · Issue 166330
Listview joins corrected for multiple classes with the same name
Resolved in Pega Version 7.1.7
Running a listview with join which contains same name column in the "Get these fields" from Applies-to class and joined class was not working correctly; the property from the joined class was exposed whereas the one from Applies-To class was pulled from the blob column. To correct this, the SQL generation logic has been modified to maintain correct order (unexposed properties followed by exposed).