SR-C18886 · Issue 358530
Enhancement to support international currencies in SmartDispute
Resolved in Pega Version 8.1
An enhancement has been added to the Smart Dispute application to support using international currencies. The currency control 'pxCurrencyInternational' is available in the base Pega Platform, similar to the existing control 'pxCurrency' but with format type as 'Text'. The control also has a script that removes any text other than non- numeric, comma, decimal, or negative sign values and supports both comma and dot as decimal separators.
SR-C18932 · Issue 360087
Fixed product file list view filter error
Resolved in Pega Version 8.1
When creating a product file, the error "An Exception occurred while processing contents of Rule-Admin-Product" appeared when using a list view filter in Product rule. This was caused by the instances not having the ruleset name present when it was expected, and code has been added to make sure those are included when needed.
SR-C18936 · Issue 358807
API added to customize properties used in checksum calculation
Resolved in Pega Version 8.1
In order to provide a way to customize certain system properties from a checksum calculation, an API has been added to set a list of properties to be excluded.
SR-C18978 · Issue 358377
Fixed exception for empty offline property value
Resolved in Pega Version 8.1
Using a localized value with property reference caused a script error in the _resolveParams function of pzpega_offline_localization file when there were no property values in offline. This has been corrected.
SR-C18980 · Issue 358386
Expression evaluation performance improvements
Resolved in Pega Version 8.1
The code has been modified to improve the performance of Expression evaluation by avoiding the rendering of invisible elements in layout container children.
SR-C19122 · Issue 359549
Behavior change for error handling when using "Call superclass data transform"
Resolved in Pega Version 8.1
Previously, when "Call superclass data transform" was enabled for data transfers, the initial data transform would continue working even if the subsequent transforms it called failed. As an example, given data transform A, which called another data transform B, which called another data transform C, and data transform A performed some actions after calling data transform B; If an error occurred while processing data transform C, data transform C ended processing, data transform B also ended processing, but data transform A continued working. This was confusing behavior. To create a more consistent environment, whether or not “call superclass data transform” is used, when any of the chained data transforms fail the entire process will exit. The documentation has also been updated to indicate this new behavior.
SR-C19190 · Issue 360723
Cluster Management shows all servers with pagination
Resolved in Pega Version 8.1
When Pagination was used in a table layout with page size as 20, the option to navigate between pages was not displayed and only the first 20 nodes were displayed in the cluster management landing page. This was traced to a missed checkbox in table layout properties Display Header Grid used to display the header section, and has been fixed.
SR-C19202 · Issue 358750
Handling added for password beginning with special character
Resolved in Pega Version 8.1
The upgrade process was failing when it tried to generate the the SQL for the RuleSet Cleanup Script. This was an issue with a password that began with a special character, and handling has been added for that use
SR-C19217 · Issue 363043
New Java regression issues fixed for Connector and Metadata Wizard
Resolved in Pega Version 8.1
Multiple features in Connector and Metadata Wizard (legacy) were not working after upgrade due to some methods being deprecated in the latest version of Java. These regression issues have been fixed.
SR-C19248 · Issue 359946
Behavior modification for bypass OperatorID update
Resolved in Pega Version 8.1
An update of an OperatorID record could be bypassed during authentication by setting the "extAssignFlag" property with any non-blank value, however in the most recent versions of Authentication.java this flag is ignored during the Authentication.unauthenticate() method. The flag is still respected and the update skipped if the initializeUser() method) is used. In order to create behavior that matches, if the "extAssignFlag" is enabled then the system will not save the operator record in unauthenticate() method.