INC-139328 · Issue 588584
Corrected Excel table picture being included with the rich-text editor paste
Resolved in Pega Version 8.5.2
Corrected Excel table picture being included with the rich-text editor pasteAs an unintended consequence of code added to allow pasting or dragging and dropping an image for upload using the rich-text editor and the CK Editor, any copied content from Excel also added a table picture to the last cell as part of the pasted data. This has been resolved by updating the system to recognize content copied from Excel and prevent uploading of the image.
SR-110773 · Issue 160105
WorkPage now properly deleted after rule checkin
Resolved in Pega Version 7.1.7
There was an issue with rule check-in where it created the WorkPage with the obj-class Work-ProjectManagement-CheckIn, but it did not delete WorkPage when the check-in was complete. To address this, protective code has been added that checks the class of WorkPage for the existence of expected properties in order to properly handle the related clipboard pages.
SR-119610 · Issue 177443
Corrected resizing issue with screen layout skin
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
An issue was found when mixing re-sizable and non-re-sizable widths in the Header 'Left Right Screen' layout for EndUser71 skin. On screen load, the panels appeared with the correct size, but once the right panel was closed and reopened, it reopened to the size given for the 'Left Panel Width'. This has been corrected.
INC-155559 · Issue 617502
GoToStage property marked as non-transient
Resolved in Pega Version 8.5.3
When refreshing or reopening the flow, the pzRuleParamsHolder did not display the gotostage property in in the change to stage shape even though the property was present in the clipboard and the flow switched correctly. This was traced to pyGoToStage being marked as transient, which caused the value to not be saved to the database. To resolve this, the pyGoToStage property is now marked as non-transient.
INC-157974 · Issue 621965
Summary Report collapsible sections made accessible
Resolved in Pega Version 8.5.3
In order to improve accessibility, the rules 'RRDataSummaryGeneration' and 'pzDisplayGroupNodeVertical' have been updated so the clickable expand icons in summary reports will append the value of the current group when setting the text "Click to expand or collapse". This will allow JAWS to uniquely identify exactly what will be expanded or collapsed.
INC-159332 · Issue 629619
Logic updated for finding 'Last' in Interaction History
Resolved in Pega Version 8.5.3
The 'LastReponseDate' and 'LastInteractionId' in the Interaction History summary data set were null. Investigation showed that reusing the ESM component in the aggregation dataset caused any assumptions made during the optimization of ESM to not be true anymore. To resolve this, the logic of the Last aggregation has been modified to not rely on a Last event which might not be stored in-state (such as optimization), but rather to use the list of events which is always stored.
SR-114479 · Issue 165273
Corrected locking for custom Access Roles
Resolved in Pega Version 7.1.7
After adding a custom Access Role to an Object in the WO class with an Access When rule defined to allow opening a instance, Obj-Open-By-Handle failed to lock the work item correctly and two operators could have it open simultaneously. This was caused by the custom stack inheriting parent state for all members, and has been changed.
SR-
118589 · Issue 171900
Corrected locking for custom Access Roles
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
After adding a custom Access Role to an Object in the WO class with an Access When rule defined to allow opening a instance, Obj-Open-By-Handle failed to lock the work item correctly and two operators could have it open simultaneously. This was caused by the custom stack inheriting parent state for all members, and has been changed.
SR-116157 · Issue 165994
Improved crash recovery in a complex system
Resolved in Pega Version 7.1.7
During crash recovery in a clustered, load balanced system, attempting to recover a user's progress displayed a message that the session was recovered but the page did not then properly load the recovered data. To ensure proper crash recovery failover on complex systems, the user is now authenticated on the STANDARD thread instead of a work thread when restoring work in progress.
SR-118174 · Issue 173341
Sorted Report Definition drill downs corrected
Resolved in Pega Version 7.1.7
For some configurations, the Report Definition drill down did not work when it has been sorted. This manifested as either no results returned by the drill down report or an error message related to invalid filter values. This was caused by an error in calling the page sort in cases where 'do not display group headers' was checked, and has been corrected.