INC-177470 · Issue 657142
Optimization prconfig check added for TableInformationMap
Resolved in Pega Version 8.7
A prconfig setting check has been added to the TableInformationMap use of OPTIMIZE_SMA_QUERY during its foreign key lookup.
INC-170551 · Issue 656558
Rule Assembly update for pxTextInput and pxDisplayText
Resolved in Pega Version 8.5.5
After the application restart, multiple rule assembly alerts were seen for pxTextInput and pxDisplayText . During first access, Assembly is done and container is cached in VTable; investigation showed that in this case, the Load class without the package name had a class not found issue, and then subsequent access tried to use the container from cache and assembly was not done. To prevent this, an update has been made to perform the class lookup using the package name and class name.
INC-170551 · Issue 656559
Rule Assembly update for pxTextInput and pxDisplayText
Resolved in Pega Version 8.7
After the application restart, multiple rule assembly alerts were seen for pxTextInput and pxDisplayText . During first access, Assembly is done and container is cached in VTable; investigation showed that in this case, the Load class without the package name had a class not found issue, and then subsequent access tried to use the container from cache and assembly was not done. To prevent this, an update has been made to perform the class lookup using the package name and class name.
INC-182986 · Issue 668829
Property Rule Form refreshes after discarding changes
Resolved in Pega Version 8.7
After updating from Pega 8.2 to Pega 8.6 and migrating the properties, modifying any property rule and then discarding the change did not refresh the Property Rule Form. Investigation showed that the LOG-SYSTEM-PROPERTYOPTIMIZATION instance created during property optimization was not getting deleted when a property was deleted. As this was not getting deleted, the property was shown as optimized when adding the property back, causing confusion. This has been resolved by cleaning up the LOG-SYSTEM-PROPERTYOPTIMIZATION instance when the property is deleted and there is an optimization entry.
SR-A22794 · Issue 245278
parseXML able to map multiple values
Resolved in Pega Version 7.2.1
In order to present more information for custom use, parseXML as been updated with a new pagelist property that can map multiple attribute values.
SR-A19986 · Issue 242898
getAppHashForApplication API updated
Resolved in Pega Version 7.2.1
When logged in from an end user portal, editing a decision table and clicking on the gear icon to add a function would show the Function's headers (Example, Activity, string, etc.), but the functions list would not be loaded. This was traced to a timeout resulting from having numerous functions running on the portal combined with a configuration that returned an unowned AppHash when calling a ruleset from the production layer rather than the application layer, and has been resolved by adding logic to write out the AppHash when the appInfo is created from opening the application.
SR-A13590 · Issue 239611
Updated handling for Cyrillic usernames
Resolved in Pega Version 7.2.1
On systems where Windows user name was created in Cyrillic (ex C:\Users\?????? ????), generated word documents would be empty due to the characters in the directory name not being properly handled. The system now contains modified Silverlight code that will read the registry keys using RegOpenKeyEx, RegQueryValueEx and RegCloseKey functions of advapi32.dll as opposed to previously used RegRead function of Wscript.shell. These new registry functions are Unicode-aware. The Silverlight Prerequisites installer has also been modified to include the latest certificate.
SR-A22458 · Issue 243317
Plus '+' sign encoding corrected in connect-HTTP
Resolved in Pega Version 7.2.1
Using connect-http get to send an encrypted string to the external endpoint was not working due to missing encoding for the plus '+' string. The encoding has now been fixed.
SR-A17649 · Issue 233752
SQL generation modified for "Optimize for Reporting"
Resolved in Pega Version 7.2.1
After using the wizard to update Properties via "Optimize for Reporting", Report Definition will create SQL that is unique if the optimized property name is too long. This can result in the unique property name exceeding the 30 character field length, which then triggers the generation of a unique id with P +timestamp as the column alias name. Unfortunately, this means even if the same report is executed multiple times, the query would be different each time because of the column aliases and therefore the DB engine won't take the benefit of prepared statement caching and performance could be effected. To create the most effective performance, the column alias generation has been modified as below to make the column alias the same across multiple runs of RD: - using 25characters in propertyname and suffix it with index of the field location in RD select, L for list report - using 25characters in propertyname and suffix it with index of the field location in RD select, G for group fields in summary report
INC-173505 · Issue 657024
Error message updated for data page with REDUX
Resolved in Pega Version 8.7
A WrongModeException was generated when a runtime activity was trying to access a missing property in a data page with REDUX enabled. To clarify the issue, the error has been modified to be a MissingPropertyException. In addition, property information for a page group property was inferred on the top level page when it should have been inferred on the embedded page. This has been changed to infer the correct property information for mode-based processing to work as expected.