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-113557 · Issue 167227
Dynamic Select correctly expands drop downs with IE
Resolved in Pega Version 7.1.7
While using the WorkBasketGadget with dynamic select, drop downs were not expanding to the full width of the field value and parts of the values were hidden. This was caused by an IE bug. The WorkBasketGadget rule has been modified to overcome the issue.
SR-114545 · Issue 164887
Increased limits for Bulk Processing
Resolved in Pega Version 7.1.7
When attempting to filter cases for Bulk Processing, the Property-List LookupList activity only requested a maximum of 2500 records. This caused an issue with class inheritance chains that contained more than 2500 property records, as those excess properties were not being used to filter within Bulk Processing area. To remedy this, the activity now allows a maximum of 10,000 records for Bulk Processing.
SR-114723 · Issue 166462
Portal calendar display corrected
Resolved in Pega Version 7.1.7
No data was visible for the daily or weekly view when displaying the Calendar on the Portal. This was caused by the height of the time frame for Daily/Weekly being set to a fixed value, causing events which fall under 11PM-12AM to not be displayed properly. In addition, the cell width for monthly view was also set to a fixed value, causing it to show only 4 events and hiding the 'show more' option. To correct this, the Day/Weekly view now includes double height to show all events, and the Monthly view displays 3 events and correctly includes the 'show more' option.
SR-114728 · Issue 166514
Resolved locking problems with doubled flow submissions
Resolved in Pega Version 7.1.7
If a Page validation message was present and an additional flow action was submitted through a second action menu, a "Lock Lost" message was generated. This was traced to the "Release on Commit" checkbox defaulting to 'on', and it has been set to a default condition of 'off'.
SR-114807 · Issue 162848
"Transfer to an Operator" dynamic list was not sorted
Resolved in Pega Version 7.1.7
The "Transfer to an Operator" dynamic list was not sorted, while the "Transfer work from" dynamic list was. This was caused by different function calls in the system, and has been corrected so the lists sort properly by property name.
SR-115000 · Issue 165234
Operator substitutions restored to the availability settings
Resolved in Pega Version 7.1.7
The operator availability setting links for Case Manager portal and Case User portal were missing substitute assignee details. These have been restored.
SR-115268 · Issue 166797
Cleanup improved for resolved work-items
Resolved in Pega Version 7.1.7
An error in the logic for Stage Flows caused improper cleanup of resolved work items, leading to outsized assignment tables. This has been corrected.
SR-115511 · Issue 168772
Application Express Wizard updated to correctly bind rulesets
Resolved in Pega Version 7.1.7
New Rule-Access-Role-Obj (RARO) rules created using Application Express wizard were being bound to specific ruleset versions vs. ruleset names. This caused failure to any modification to those RAROs, since modifying a RARO with a ruleset version would mean the save-as would fail if the validation found a RARO already present for that ruleset. In order to ensure proper binding and aid migration, a RARO with ties to a ruleset version will have that the version information removed automatically upon saving of the RARO.
SR-115711 · Issue 165363
Flow Action class correctly retrieved for subprocesses
Resolved in Pega Version 7.1.7
When running a Process Flow in a Data- class that is called from a Work- process flow via a SubProcess, the error "Failed to find a 'RULE-OBJ-WHEN' with the name 'CANMAINTAINCASEREPORT'" was being generated. This was caused by incorrect handling for the class: the flow action and WHEN rule are in a WORK class, but when the sub-flow is executed it looks in the DATA class of the embedded page instead of the WORK class relevant to the overall case. There was a workaround of saving the WHEN rules into the Data- classes, but the system now uses workPage instead of interestPage for localcase to ensure the correct class is retrieved.