SR-D8650 · Issue 475298
Handling added for null sort order in file import metadata
Resolved in Pega Version 8.3
A NullPointerException was seen while fetching the sort order of indexes during a file import. This was caused by a null being returned for an index that did not have the sort order in the metadata, and has been resolved by adding a null check; if the metadata of the index returns "null" as sort order, then the order will be set to "A".
SR-D10969 · Issue 475335
Logic for the Materialized/Not Materialized feature updated
Resolved in Pega Version 8.3
The Materialized/Not Materialized feature was not working properly. When there was an aggregate dataset entry in the Advance page set to use "No" for materialized, doing "Materialized" in IH Summaries LP on that dataset materialized the dataset and created a duplicate entry in the aggregation config page where one was "No" and one was "Yes'. This has been corrected. It was also observed that after an application changed its name while the access groups remained the same, changing a dataset from "Not Materialized" to "Materialized" worked, but changing from "Materialized" to "Not Materialized" did not. Instead, a warning message was posted at the top of the page indicating the problem. Investigation showed that the pzChangeStatus activity failed because the current application name did not match the application name of the access group set for the aggregation configuration record. To resolve this issue, the logic has been updated to remove the reliance on the application name.
SR-D10970 · Issue 475336
Datasets created from the IH summary component correctly listed as aggregate
Resolved in Pega Version 8.3
Attempting to create an aggregate data set from the IH Summary shape did not properly list it as aggregate due to a source dataset error. This has been corrected.
SR-D10966 · Issue 476280
IH summary behavior change reverted
Resolved in Pega Version 8.3
Changes introduced to Interaction History aggregations in 8.1 intended to better align them with the existing behavior of the Interaction History shape in Strategy produced the unexpected side effect of lots of empty records. Based on feedback, the decision has been made to revert the IH aggregation behavior change.
SR-D6265 · Issue 477258
Cursor action corrected for pyRecents section refresh condition
Resolved in Pega Version 8.3
If a “Layout Group” was used to add content in the left panel of the User Portals, the inclusion of the out-of-the-box pyRecents section with the standard refresh condition resulted in incorrect cursor behavior when selecting landing page options, displaying the content in a tab while the cursor in the left hand panel jumped up or down one position. Investigation showed that the index in the bar menu was wrongly set in sessionstorage when separators were present, and the issue has been resolved by updating the setstate and maintainstate methods to not consider the menu-separator in calculating the index.
SR-D211 · Issue 481391
Case Assignment issue lock corrected
Resolved in Pega Version 8.3
After upgrade, an intermittent error was seen when browsing the screen flows of a child case type application, indicating "Users have lost the ability to make this change because a change elsewhere has taken precedence over the change you made here. Please click on the assignment again to continue". This was traced to a change made to address an issue with the Opener not properly honoring the aUnlockOnCommit flag that was passed in via the openIfStale() API: in a very specific use case following that change, the system would unlock work objects during openIfStale when it should not. This has been corrected.
SR-D9922 · Issue 481416
Case Notes view has proper line wrapping in Google Chrome
Resolved in Pega Version 8.3
When case notes were opened in the Google Chrome browser, the view did not wrap. This was traced to a style attribute for white space which caused the line breaks to be collapsed in Google Chrome, and has been resolved by modifying the DisplayNote HTML to handle the wrap use case.
SR-D8279 · Issue 481598
Error enhancements added to Cases API
Resolved in Pega Version 8.3
Enhancements have been made to error handling for the Pega cases API:1) Any error added to an activity called in case creation, for example "ValidateNew", was generating a 500 error and not being returned. This has been modified to return and display a 4XX error along with the error message. 2) 'Put' now has an extension point for validating input and adding errors, and the errors added will be returned. 3) Post for assignments now also has extension points that will fire the validation errors while calling from Rest. If set, the error will be returned by the REST service.
SR-D9119 · Issue 481695
Handlng improved for rollback of Hfix with dependent HFixes
Resolved in Pega Version 8.3
Attempting to rollback an HFix with dependent HFixes resulted in a Hazelcast jar exception. Investigation showed the DL included the same jar multiple times in the dependent hotfixes, which was a result of how the DL was created via the hotfix process. In order to better handle this scenario, when there are multiples of the same entries to delete the message will be logged and the process will continue if the entry is not found in the database.
SR-C91274 · Issue 481706
Corrected Base64Decode calculations
Resolved in Pega Version 8.3
Testing indicated that a file encoded using Base64Encode generated the error "The Operation completed successfully, but returned no content" when decoding with Base64Decode. Validating the content of the text file via a JSON validator using text formatted as JSON worked as expected. Investigation showed that extra padding characters were being appended due to calculations around CRLF characters, and this has been corrected.