INC-166820 · Issue 649968
Blank parameter handling added to assignments function
Resolved in Pega Version 8.5.4
When calling the Pega v1 API /assignments/{ID}/actions/{actionID} a 500 Internal Server Error status was returned if the configuration included an Autocomplete configured with two fields where the second had the "Use in Search" setting enabled. An error was also logged. Once the error occurred, editing the Autocomplete to disable the second "Use in Search" did not stop the error; the entire Autocomplete had to be deleted and recreated. This was traced to the system trying to set a blank parameter due to the autocomplete being configured with a data page with no parameters, and has been resolved by modifying the pzAPIDetermineOptionsFromPage Rule-Utility-Function to not set parameters when the parameter key is blank.
INC-169323 · Issue 646268
Deleting attachment with icon button works in Attachment section
Resolved in Pega Version 8.5.4
After upgrade, a delete icon in the attachment section was not working as expected. This was traced to BAC work done earlier, and has been resolved by updating the Delete Attachment function of the AttachmentListViewSelectorScript.
INC-170041 · Issue 649669
Check and error message added for filename containing "%00"
Resolved in Pega Version 8.5.4
At the time of file attachment or upload, if the file name contained % followed by two 0s (%00), the file upload mechanism distorted the UI and the Pega logo screen popped up. The file was saved properly in the ServiceExport directory, but while fetching the attachment info, the file was split in two because the engine considered %00 as a delimiter. This has been resolved by adding a file name check and a pyInvalidFileName field value to be used for an error message.
INC-173953 · Issue 650851
Updated Pega DX API special character handling
Resolved in Pega Version 8.5.4
When the using Pega API v1 and invoking api/v1/cases/{ID}/actions/{actionID} for a few fields in section, special characters were being converted into HTML entities. For example,"You'll usually find this information in your terms and conditions." was being converted as "You& #39;ll usually find this information in your terms and conditions" in the API response. This has been resolved by updating the system to ensure the pyDXAPIEncodeValues application setting is honored.
INC-174355 · Issue 652051
Corrected file download in Cosmos
Resolved in Pega Version 8.5.4
An unauthorized request error was seen in tracer while downloading files in the Cosmos application. This was traced to the pyAttachmentFeedDescription control in the Theme Cosmos Rule Set not being correctly updated, and has been resolved.
INC-176091 · Issue 652121
Busy indicator correctly resolves with Microsoft Internet Explorer upload
Resolved in Pega Version 8.5.4
When using Microsoft Internet Explorer to upload documents, the busy indicator was not resolving after the file was attached. This was due to a missed use case in work done around the timing of the busy indicator when attaching multiple files, and has been resolved by modifying PzMultiFilePath to ensure the busy Indicator is removed when the file count is zero.
INC-167606 · Issue 665868
Updated ConfirmHarness handling for case type creation
Resolved in Pega Version 8.5.5
If a new case type was created with the initialization stage and there were no assignments in the case type, the /cases API did not return a NextPageID in response. This has been resolved by setting the pyConfirmHarness parameter before calling addworkobject.
INC-168368 · Issue 651080
Correct flow actions loaded in multi-thread portal refresh
Resolved in Pega Version 8.5.5
The member authentication screen was displaying an incorrect flow action on doing browser refresh after creating a new interaction. Refresh is a special case where the parameter retention is different across single-threaded & multi-threaded portals alongside the execution order of activities. In this case, this inconsistency occurred in a multi-threaded portal when newAssignPage had the information to load the proper assignment but the parameter indicated an old index. This has been resolved by adding 'when' conditions to to populate and pass the correct references and labels and to honor the Param.TaskIndex set and sent by UI activities so it's retained in case of multi-thread portals.
INC-169636 · Issue 649730
WorkObjects security update
Resolved in Pega Version 8.5.5
Cross-site scripting protections have been updated for WorkObjects.
INC-170514 · Issue 653761
Lock conflict resolved for AssignmentCheck
Resolved in Pega Version 8.5.5
The error "Unable to unlock this work object" sporadically appeared in both the runtime log and Pega RULES log when the robot was trying to create a case in Pega using an API call. Investigation showed that as the case was created, it was pulled by another robot (another requestor) which was using the GetAssignments API. This caused the perform assignment check to fail. To resolve this, a 'when' rule has been added to the performAssignmentCheck Activity.