Progress® Telerik® Reporting R3 2017

Requirements

Requirements for adding and displaying the HTML5 Report Viewer.

  1. Required Service:

  2. Required JavaScript libraries:

  3. Required HTML5 compliant browser. For more information see: Browser Support

Important Settings

Note Note

Kendo UI Professional license is not required if you are only going to use the demanded pro widgets for the needs of HTML5 Report Viewer. Telerik Reporting provides a JS file containing a subset of the used by default Kendo UI widgets - telerikReportViewer.kendo-x.x.x.x.min.js. For more information refer to Telerik Reporting License Agreement (point 4.2).

  • The required CSS and Js files must be loaded before creating the HTML5 Viewer on the page.

  • jQuery must be loaded only once by the page with the HTML5 Viewer;

  • If you are using Telerik Kendo UI of version greater than 2015.3.930, you need to replace the provided subset of Kendo UI widgets (telerikReportViewer.kendo-x.x.x.x.min.js) with a link to the original Kendo Ui JavaScript libraries like kendo.all.min.js;

  • If you use a CDN to load the required CSS and JS files, verify the links are run over HTTP or HTTPS depending on the hosting of the application.

  • The HTML5 Viewer is designed to request its HTML template from the resources of the Reporting REST Service. If you will not add changes in the default template, you do not have to specify the HTML template. The HTML template includes links to the HTML5 Viewer's CSS template file and icon fonts, also available through the resources of the HTML5 Viewer.

    For more details, check Styling and Appearance

  • The viewer depends on the Promise object and will not load successfully if not available. See Promises/A+. Most modern browsers have native implementation and support for this object (see Browser Compatibility at Promise - JavaScript | MDN). If Promise object is not detected, the viewer will use JS to try and load a Promise polyfill from Polyfill.io with the query https://cdn.polyfill.io/v2/polyfill.min.js?features=Promise. The loading might not succeed if the browser security does not allow dynamic script loading or the client computer has no internet access. If this applies to your application deployment scenario you should load a Promises/A+ JS implementation of choice into your application. For example you can load the same polyfill:

    <script src="https://cdn.polyfill.io/v2/polyfill.min.js?features=Promise"></script>

    In that case the viewer will check that a Promise object is available and will not try to load another one.

See Also