INC-155855 · Issue 620576
Safe check added to modal window pop-up cancel
Resolved in Pega Version 8.5.3
On click of a link to add items to the rows by selecting the page list from pop-up window, clicking on the cancel button generated a node name undefined error after which clicking the link would not open the pop-up window at all. This was traced to the pre-processing activity in the flow action used to copy page list from one page to other, and has been resolved with the addition of a safe check.
SR-116903 · Issue 167940
Recent Explorer item handling corrected
Resolved in Pega Version 7.1.7
When opening a Scheduled item from Recent Explorer, an incorrect flow was being called and the Review Harness buttons (which are based on flow parameters) were incorrect. This was traced to a missing TaskWrapper activity, and has been corrected. In addition, a process was added to check property as well as parameter in the Review Harness.
SR-117583 · Issue 170260
Draft Mode now includes referenced rules for shape sub-processes
Resolved in Pega Version 7.1.7
If a a flow was created in Draft Mode and shapes were added, adding subprocess shapes and implementing one of the subprocesses created a list of Referenced Rules that did not include the sub-flow rules. This was caused by dangling connectors, and has been corrected by a call that will generate the Java for the flow even when this condition is present.
INC-139627 · Issue 604760
Legacy and new ID generation logging enhanced
Resolved in Pega Version 8.5.2
A DuplicateKeyException was generated when attempting to create a case. The root issue was related to the local modification of the reserved ID field in the database through a custom activity and was able to to be fixed with a local change. In order to improve diagnosing events such as this in the future, enhanced logging has been added to to the legacy and new ID generation.
INC-144601 · Issue 602422
Empty addresses removed from email
Resolved in Pega Version 8.5.2
After upgrade, an issue was seen when sending email to multiple 'To' addresses generated an exception if any 'To' address had an empty value. To resolve this, a check has been added that will remove any empty address from the recipientTo address list.
INC-135195 · Issue 598071
PD4ML library updated
Resolved in Pega Version 8.5.2
When generating a PDF from a report definition with more than 1000 records, the system would hang abruptly and stop responding. There was also a noticeable size difference in the generated file. This was an issue with the included version of PD4ML, and has been resolved by updating the version from 4.0.6 to 4.0.9fx1.
INC-154564 · Issue 617348
JAWS reads the table header and filter options separately
Resolved in Pega Version 8.5.3
When table headers for a non-optimized table with filter options received focus in Google Chrome, JAWS read the header, sort and filter options all run together. This was due to a difference in the way JAWS reads headers in Chrome from the way it reads them in IE, and has been resolved.
INC-146564 · Issue 607856
DX API returns application specific validation messages
Resolved in Pega Version 8.5.2
When trying to validate the input swagger details with application specific conditions, the create case DX API did not return the validation messages from application but instead returned a "500 Internal Server Error". Investigation showed that the error parameter was not set on validation fail, and this has been corrected.
INC-152442 · Issue 616666
Check added for Create Access to attachment
Resolved in Pega Version 8.5.3
After restricting access for the attachments category in a CS application, the attachment was added without category and could not be opened. This was due to the Create Attachment access not being automatically created for all categories when privileges were added, and has been resolved by adding a step to check Create Access for attachments of the respective category.
SR-114596 · Issue 164687
Check added for property with blank value
Resolved in Pega Version 7.1.7
If a property is left blank in the SelectTierOverride section, updating that section showed the message "'pega' is undefined" and a JavaScript error was generated. This was traced to the filePath control included in the section, which along with refreshing the section submitted filepath data to the server: if messages are set on page using Page-Set-Messages/Property-Set-Messages, then it will try to include pega_ui_textarea js file and fail. To correct this, a check has been added for blank properties.