Improves report rendering engine of all REST reports services.
Features
- The report rendering engine of all REST reports services now uses dedicated rendering thread queue with configurable count.
Fixes
- Fixed:
- Designers - Cannot grab the resize handle of container item when child item is adjacent
- Standalone Report Designer - Broken table layout when cut/copy cell, paste to another cell and trigger undo
- Standalone Report Designer - Report is not marked as dirty (save is not enabled) when TOC report is set to a report book
- Standalone Report Designer - ReportBook designer do not refresh on undo and redo operations
- Standalone Report Designer - Typed text in input field in CSV datasource wizard is displayed backwards
- Visual Studio Designer - VS item template cannot discover existing type reports in VS2015
- Visual Studio Designer - VS item templates fail to add nuget packages
- Processing - Expand all action does not expand nested groups
- Processing - Rendering reports in parallel using the ReportProcessor throws an error
- Rendering - Graph is scaled down when exported to MSOffice formats on a machine with high DPI from a dpi-aware application
- Rendering - Graph is scaled down when exported to MSOffice formats on a machine with high DPI from a dpi-unaware application
- PDF Rendering - The actions, associated with elements, aligned at the left or top side of the page, are not respected
- WebAPI - Reports stay partially rendered forever when IIS hits thread allocation limit
- MVC Report Viewer - Cannot handle direct print correctly, since it has three states - undefined, true and false
- Changed:
- System.Web.HttpContext.Current is not available in the report rendering thread anymore. Instead, to access the current user context please use the Telerik.Reporting.Processing.UserIdentity.Current static property. The UserIdentity object is also accessible in the expression context as a global object: =UserIdentity