SR-128883 · Issue 195834
Fixed button contrast when using accessibility
Resolved in Pega Version 7.1.8
The "Select Values" button in the dialog to edit report filter had a low contrast ratio when accessibility was enabled. This was caused by the unintentional application of the repeat layout CSS to the button, and has been fixed.
SR-130224 · Issue 200002
Fixed class pickup when Ticket Urgency is used as reference
Resolved in Pega Version 7.1.8
It was not possible to convert a summary report to a list report if the report had Ticket.Urgency as a reference and Ticket was a single page pointing to data class type property in the work class. This was traced to the drill down picking up the Urgency property from the work class, and has been resolved.
INC-195511 · Issue 693219
Check added for child join class when using ABAC
Resolved in Pega Version 8.7.1
When a join was applied on a report definition and the same join class had a child class to which ABAC was applied (for some property eg., isABC), an "invalidreference" exception (isABC) was generated. This was traced to the system taking into account the child class of the join class while running the report, and has been resolved by adding a check to handle this scenario.
SR-127517 · Issue 199062
Fixed Listview filtering using manual entry
Resolved in Pega Version 7.1.8
List View filtering was not working when the filter string was explicitly typed in the filter section. Handling has been added to the Embedded list filtering to correct this issue.
SR-127237 · Issue 190840
Time-related RUFs now use operator's time zone
Resolved in Pega Version 7.1.8
Date properties and Time properties were taking their reference from the server's default time zone, which created unexpected behaviors for operators in other time zones using start and end date functions. This has been resolved by updating the time-related RUFs to use the operator's defined time zone
SR-129592 · Issue 196979
Scheduled report now checks default max records value
Resolved in Pega Version 7.1.8
When scheduling a report definition, the default value for max records to export was ignored when run by a scheduled task agent but used if the report was run manually. This value is normally set to 10,000 in the system settings and should be the default unless an override value has been entered for "Maximum Number Of Rows For Export" on the Data Access tab. To correct this issue, the pzRunScheduledShortcut activity has been updated to use the default if no value has been entered.
SR-122689 · Issue 183471
Corrected display issue for tabbed Summary View charts
Resolved in Pega Version 7.1.8
When using Summary View charts in a Tabbed Section, the chart loaded correctly on the first viewing. However, on moving to a different tab and coming back to the same tab again, the Summary View was getting distorted (elongated). There was a local workaround on using RefreshWhenActive, but this has been resolved.
SR-122689 · Issue 183713
Corrected display issue for tabbed Summary View charts
Resolved in Pega Version 7.1.8
When using Summary View charts in a Tabbed Section, the chart loaded correctly on the first viewing. However, on moving to a different tab and coming back to the same tab again, the Summary View was getting distorted (elongated). There was a local workaround on using RefreshWhenActive, but this has been resolved.
SR-117877 · Issue 178627
Report on implementation classes corrected for descendant class
Resolved in Pega Version 7.1.8
Report definition was not using implementation class even when 'report on descendant class' was checked. This was caused by an access group changed in RAQ not being reflected into DAQ. When a Data-Admin-Requestor has a Access group which isn't the default, the default authentication doesn't occur and as such the application data page isn't created for the requestor. The lack of an application page causes the code to not determine the associated implementation class for the report definition. This has been changed to use the access group from DAQ only if it is newer than RAQ.
SR-117877 · Issue 175972
Report on implementation classes corrected for descendant class
Resolved in Pega Version 7.1.8
Report definition was not using implementation class even when 'report on descendant class' was checked. This was caused by an access group changed in RAQ not being reflected into DAQ. When a Data-Admin-Requestor has a Access group which isn't the default, the default authentication doesn't occur and as such the application data page isn't created for the requestor. The lack of an application page causes the code to not determine the associated implementation class for the report definition. This has been changed to use the access group from DAQ only if it is newer than RAQ.