SR-108838 · Issue 154989
Increased limit for Rule_Obj_CaseType
Resolved in Pega Version 7.1.7
Previously, Rule_Obj_CaseType was encountering a byte limit of 65535 in the JVM that impeded the ability to create a desired large number of coverable work types (54+). The system code has been modified to store the rule types differently to avoid generating extra lines of java code for each coverable case type.
SR-109455 · Issue 172370
CSS generation fixed for attaching files after validation failure
Resolved in Pega Version 7.1.7
After a validation had failed, uploading a file (through the filePath Control) and submitting the flow action resulted in the page loading with no CSS applied. This has been corrected by changing how the uploading wrapper is applied in cases of validation failure.
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-111606 · Issue 163137
Improved consistency with multiple class inheritance rules
Resolved in Pega Version 7.1.7
A gap in the handing of multiple class inheritance was causing an issue with the consistency in picking the correct rule from a cache. If the entry was placed in a class where the applies-to class of the rule could not see it, that entry was missed from invalidation later on during the save. This could be temporarily remedied by clearing the cache, but the rule handling has been updated to consistently choose the correct rule from the cache under multiple inheritance.
SR-111889 · Issue 157259
Some SOAP calls with WSTRUST generated exceptions in customized environments
Resolved in Pega Version 7.1.7
In some heavily customized environments, a SOAP connect call using the WSTRUST element generated an exception. This was due to uneven handling of the local custom elements in the SOAP STS request, and has been resolved by adding a method to pick up all custom code based on the tag in policy document.
SR-111945 · Issue 157966
Closing Lucene search popup in Firefox corrected
Resolved in Pega Version 7.1.7
When using Firefox, it was not possible to close the popup box generated by a Lucene search unless a work object was selected first. This was caused by an error the the method used to access the document id, and has been corrected.
SR-112147 · Issue 162872
Missing buttons from modal dialogues after manual resize
Resolved in Pega Version 7.1.7
After a launching a modal dialog from a local action and manually resizing it to make it smaller, selecting another layout from the dropdown menu was causing the re-size icon and OK/Cancel buttons to disappear. To eliminate this problem, the system has been modified to properly reset the height and width of the modal container before displaying the second layout was displayed.
SR-112203 · Issue 156906
Corrected 'Top Performers' report
Resolved in Pega Version 7.1.7
The "Top Performers" report in the Case Manager portal was returning incorrect values in the 'Avg. Velocity' column due to an incorrect calculation based on the number of days in the selected period. This has been corrected.
SR-114573 · Issue 162421
Corrected 'Top Performers' report
Resolved in Pega Version 7.1.7
The "Top Performers" report in the Case Manager portal was returning incorrect values in the 'Avg. Velocity' column due to an incorrect calculation based on the number of days in the selected period. This has been corrected.
SR-112357 · Issue 163326
Dynamic Select while editing Data Table instances
Resolved in Pega Version 7.1.7
When using DynamicSelect in a few properties under DataTable instances, editing or adding new rows in the DataTable failed to show a list of values from ReportDefinition and generated the error "Select element SwitchboardCategory is missing DSCaption". This was traced to HTMLPropertyParams not being properly passed on to DynamicSelect control, and has been fixed.