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).
SR-112935 · Issue 166182
Repeating grids enhanced to allow the '&' character as text
Resolved in Pega Version 7.1.7
When values in a repeating grid contained the character "&", the ReloadSection activity failed with an illegal argument tracer and no values were passed to a second Repeating Grid Page List. This was traced to '&' being used by the system to perform a split of value string. In order to allow use of the '&' character in the list values field, it will now be encoded so it is passed without evaluation.
SR-113396 · Issue 162534
Smoothed background Bulk Processing processing
Resolved in Pega Version 7.1.7
If the setting for BPUnitsToProcessForeground is given as 0 in all cases, attempting to run Bulk Processing in the background failed and logged an "Index out of bound" exception in the system logs. To cover this condition, a check has been added to handle zero items in the foreground processing when running background Bulk Processing.
SR-113919 · Issue 170809
Made page displays consistent between Java versions
Resolved in Pega Version 7.1.7
"pxflow" pagegroup values in pywork page were being placed differently depending on the version of Java used in the environment. This was caused by a handling error in situations where there is no classname, and has been fixed.