SR-108805 · Issue 149539
Help updated to explain When Rule "ALL" Evaluation behavior
Resolved in Pega Version 7.1.7
A 'when' rule evaluating all pages in page list will only evaluate the properties on pages in the list that contain that property. This may cause a "true" result that does not match customer expectations. The hover help has been clarified to explicitly state that the evaluation results apply only for those pagelist entries where the property exists and not for all the page list entries.
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-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-113149 · Issue 168421
Ensured tabbed section refresh for new sessions
Resolved in Pega Version 7.1.7
When a new session had only 2 tab groups configured with dynamic container, the first tabbed section refresh was not working as expected. This was caused by a missing null check, and has been corrected.
SR-113431 · Issue 161621
Corrected use of Navigation URLs in Detailed view
Resolved in Pega Version 7.1.7
The detailed view drilldown from a summary view was not passing the correct set of filters down to the server when the breadcrumb trail link was clicked, causing any included Navigation URLs to fail. There was a workaround of using list view in place of detailed view, but the HTML has been updated to pass the proper parameters to the activity and show the correct information.
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-113714 · Issue 173122
Added tenantID checking for multi-tenant import of access groups
Resolved in Pega Version 7.1.7
When attempting to overwrite an existing access group by importing the Client Access groups in the tenant layer, an error was generated and the access groups were not overwritten. This occurred when the SQLs were not Tenant-qualifying for operator records but were being imported into a tenant; as a result, operator record updates were marked as inserts. To correct this, the behavior has been updated to query for current tenantId and always tenant-qualify the query if it's an overridable instance and not in a shared context.
SR-114353 · Issue 166997
System scanner performance enhanced
Resolved in Pega Version 7.1.7
When working with a large number of hotfixes, the system scanner can become very slow. Performance enhancements have been incorporated to increase speed by changing how ID and key comparisons are performed.
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.