SR-C93344 · Issue 431348
Bcrypt password hash increased to 2^12
Resolved in Pega Version 8.2.2
Bcrypt password hashes have been increased to 2^12 iterations for new passwords.
SR-C89156 · Issue 429484
Blank paramter passed as inshandle invokes NoWorkID harness instead of exception
Resolved in Pega Version 8.2.2
In releases prior to 8.1, the Obj-Open-By-Handle method was used to set an ActivityStepStatus error if a blank parameter was passed as inshandle. The activity step 8 would show as failed and invoke the NoWorkID harness. As of Pega 8.1, the code was refactored and modified to throw an InvalidArgumentException and quit the activity. In order to ensure better backwards compatibility, the error handling has been reset to show the NoWorkID harness when instanceHandle is empty.
SR-C93555 · Issue 431599
BulkMover updated to not treat Numerics as strings
Resolved in Pega Version 8.2.2
When attempting to update Pega platform 8.1.1 to 8.1.3 with Oracle on a Windows machine with German locale using the out-of-place upgrade of the rules schema, the migration failed at the migration step with the error message "ORA-01722: Ungültige Zahl". This was traced to BulkMover failing when trying to convert a string to a Numeric due to the locale using commas as the decimal separator, and has been resolved by updating BulkMover to not treat Numerics as strings.
SR-C89541 · Issue 430729
Case Manager email correspondence opens when encryption and obfuscation are used
Resolved in Pega Version 8.2.2
If the urlEncryption (true) and submitURLObfuscation(required) settings were enabled, it was not possible to open correspondence emails sent in Case Manager portal. No issue was seen when submitURLObfuscation was set to "optional" (which allows the server to accept URLS with either clear-text or obfuscated strings). Investigation showed the obfuscated values for pyActivity were not part of the HTTP request generated when the Data-Corr-Email attachment is clicked, leading to the system blocking the pop-up window request. Because bEncryptURLs, which is being set in the fragment DesktopWrapper_Variables, is not available in the harness context, the SafeURL method toURL therefore was not encrypting the URL. This has been resolved by setting both bEncryptURLs and pega.ctx.bEncryptURLs to true in the HTML fragment.
SR-C88948 · Issue 426225
Command-line BIX extract properly exits with failure status if the rule is not found
Resolved in Pega Version 8.2.2
Running a BIX extract from the command line was returning 0 for both success and failure. This was caused by the error message in this scenario not properly setting the flag if an extract rule did not exist, and has been corrected to ensure the command exits with status code 1 if it is not able to get the list of extract rules.
SR-C87757 · Issue 431644
Country Code for Austria saved correctly
Resolved in Pega Version 8.2.2
When trying to save an address with CountryCode=AT, the code was saved as "at" instead. This was caused by a temporary field value not being correctly cleared, and has been resolved.
SR-C89619 · Issue 429574
Custom section filters retained during refresh
Resolved in Pega Version 8.2.2
Filtered values were not retained on refresh when filtered using a custom section. This has been resolved.
SR-C91121 · Issue 430389
Data Page seatch results have expanded data available to view
Resolved in Pega Version 8.2.2
It was not possible to expand a search result and see Ruleset, Updated by, etc, for Data Pages. This was traced to the Layout Properties of section pzSearchDrilldown having a visibility condition of .pzCategoryActionKeys != 'Rule-Declare-Pages' after being reconfigured during prediction studio implementation for rule transition. To resolve this, the necessary related table for data pages has been added to the pzSearchDrilldown section.
SR-D3494 · Issue 439416
Enhanced REST acceleration wizard handling of existing properties during rule generation
Resolved in Pega Version 8.2.2
A resolution provided in an earlier release addressed the REST accelerator wizard failing when there was a property present in the @baseclass and that property was also present in the JSON input for data model generation. The error generated was "Cancelling rule generation. Definition required to conform to @baseclass.Name instance". This update further enhances that Rest wizard resolution to address case sensitivity issues in the naming, and adds additional support for scenarios where the property does not exist in the integration class or parent class by checking if the property exists in pyIntContextClass.
SR-C96297 · Issue 433776
Enhancements added in support of AES/PDC integration
Resolved in Pega Version 8.2.2
The following enhancements have been added in support of AES/PDC integration: - QueueStatistics for Oracle and multi-tenant environments -Postgres statistics are reset after every push (this can be disabled by changing the DSS ResetTableStats) -Enabled Debug statements before all connect-rest/connect-soap calls -Handling for Listener Information issues -Elastic search updates -The connect timeout has been enhanced from 30 sec to 60 sec for all REST connectors. -Data pages can be used for picking the End point URL -Elastic Search Count details can be pushed to PDC