The RenderMode property specifies how will StiWebViewer render and display a report. The categories of modes for the component StiWebViewer use caching of a rendered report and do not use caching of a rendered report.

Consider the first category - modes without caching:

1. Standard
In this mode, the report must be re-rendered every time you refresh the page. This mode does not use Ajax to display the controls of StiWebViewer. Updating a report using the controls of the component StiWebViewer causes reloading of that page, on which the report is displayed.

2. RenderOnlyCurrentPage
In this mode, the report is rendered only up to a page that is currently displayed in the component StiWebViewer. In this mode the server memory will be saved considerably.

3. Ajax
This mode uses Ajax technology to display the report and update operations for the component StiWebViewer. This allows changing the page size and other parameters without reloading the page in the browser window.

The second category that uses caching modes of the rendered report is UseCache and AjaxWithCache.

Each time when updates are applied in the component StiWebViewer, a page from the server is reloaded, but the report is not re-rendered as in the Standard mode, but each time the report is loaded from cache. This allows displaying the next page of the report much faster.

This mode, as well as the Ajax mode, uses this technology to display a report and update operations for the component StiWebViewer. However, unlike the Ajax mode, the AjaxWithCache mode does not re-render a report when every request on the server. The report saved in the cache server after the first rendering is used.

The CacheMode property indicates to the report generator which type of caching to use for storing reports, pictures and service information. There are two options:

1. Page
Use the page cache.

2. Session
Use the session cache.

The ServerTimeOut property indicates the amount of time needed to store reports, images or service information in cache. You should not use too much time or too little time. If time is too long, then cache will quickly overflow and be automatically cleared with the server. As a result, the report (or report images) will not appear in cache and wrong information will be displayed in StiWebViewer. If time is too short, then to the moment of the request, the cache may not contain the necessary data.

The component StiWebViewer can display reports with dialogs. For this you should do the following:

1. Use a mode of viewing reports with caching - set the modes AjaxWithCache or UseCache in the RenderMode property;
2. If the data are not from the server, you need to provide a connection to the data in the ReportConnect event of the component StiWebViewer. It is also necessary to disconnect from data in the ReportDisconnect event;
3. In addition, you cannot run a report for rendering in the Page_Load event. In this case, the information in cache and needed to display the dialog, can be cleared;
4. You can only use a single dialog form in the report.

Well, in so simple and unpretentious way we reviewed the component StiWebViewer. Everything is more than understandable and accessible. Of course, there is a situation - you read the article, tried StiWebViewer in action and realized that you want more features, feel lack of scope for your business nature. Stimulsoft Company can only say one thing: “Ladies and gentlemen, we present you StiWebViewer.Fx. Convenient, efficient, easy to use ...” but that is another story, which will be revealed in the next article.
When working with StiWebViewer, remember the principle of the component works. To display a report, StiWebViewer exports it to the HTML format, where the resulting HTML text is displayed in the StiWebViewer, specially designed to display the report. Since Stimulsoft Reports stores all the objects separately, then, when converting the report into the HTML format, the margins of some objects may overlap, resulting in incorrect displaying of the report in the browser. Therefore, it is not desirable to overlap one object to another. Examples of overlapping:


To avoid such a situation it is necessary to use the grid to generate reports that helps you position objects of the report and get the correct displaying a report in the browser.

Let's talk about the graphic objects in the report, but to be more exact to use them. Stimulsoft Reports has a huge set of graphical objects for displaying information and its appearance in the report. On your choice, there are various graphical objects such as images, diagrams, primitives (the Shape component), bar-codes, RTF texts, and the CheckBox component.

Also, be aware that:
Vertical Line, Horizontal Line, Rectangle components do not belong to graphic objects. All vector images (WMF, EMF, EMF +) are not supported in HTML, so they will be converted to raster images (in the pixel format).

All these components are displayed as images. Since the HTML format does not allow transferring images in its body, then the report generator uses the page cache or session cache to store the images and, when lots of graphic objects in the report, server memory is taken. With the ServerTimeOut property one can set the cache time for objects in the page cache of the session cache.

If the image you want to display is static and can be saved on the server, then it is recommended to use the ImagerUrl property of the Image component to display an image. When using this property, the report generator does not produce saving image in cache or session cache and inserts a link to the image. Thus in the page cache or session cache nothing is saved that keeps server memory.

The StiWebViewer component is able to output reports in two modes: with caching and without it. If caching is not used, it is necessary to refresh the page each time when obtaining data for the report and the report re-build. When using caching, the rendered report is stored in cache on the server. Updating the page, the previously rendered report is loaded from cache and its rebuilding it is not required. It should be taken into consideration that each report is stored in the memory cache on the server and when having a large number of requests for reports this may bring to difficulties in work. Therefore, it is necessary to choose between two options - either minor memory requirements, but major in performance, or minor requirements in performance, but major in memory. Caching also should not be used if it is necessary to have a report with actual data after each update. Controlling the caching can be done using the following properties: RenderMode, CacheMode and ServerTimeOut.

It should be considered that if you need to obtain an exact copy of a report from a browser, it is necessary to use caching; otherwise the report that appears in the current moment will not be output, but the one that will be rendered using the latest data when you refresh the page.
The World Wide Web has fully embraced the life of a contemporary man, gave him a huge flow of information. And foolish a man is who tries to watch from the sidelines for the tireless proliferation of Internet web. This is particularly critical concerns of business area. Who owns the information - owns the world. Now, this statement can be rephrased as: Who uses the information - rules the world. Only using the power of the Internet business one can keep afloat in competitive fighting and also stay as a leader. Now we will talk about one facet of the World Wide Web and how to use it. Each case, word, event has its logical conclusion. If we are talking about business and any form of earnings, then reporting thoroughly takes this niche. Stimulsoft Company, a leading manufacturer of software for data processing and analysis, like no one else knows the structure and principles of reporting; understands the importance of displaying reports in the open waters of the interactive ocean. This article covers the possibility of locating reports in the Internet and work with them, but, to be more precise, a component of Stimulsoft Reports - StiWebViewer.


StiWebViewer is an ASP.NET component that is included into Stimulsoft Reports.Web. The full path to the component is Stimulsoft.Report.Web.StiWebViewer. A Web browser that supports Javascript and CSS2 is required for this component. AJAX technology is supported. StiWebViewer is included in the following products: Reports.Net, Reports.Web, Reports.Ultimate. StiWebViewer is used to display the report on a web page. The component consists of two elements: a toolbar and an area for displaying the report. The toolbar is located at the top of StiWebViewer. Let’s review it in detail.


The toolbar allows the user to control displaying reports print them as well, save reports as files.

The picture below shows the toolbar where all its elements are marked with numbers.


1) The Print button. The component StiWebViewer supports three printing modes: printing to the Adobe PDF format, printing with preview and without preview.


Printing to Adobe PDF format:

If this option is selected, the entire report is exported to the Adobe PDF format. The file is sent as a report to the client’s browser that automatically opens this file and runs the program Adobe Acrobat to display the report. After that, from this program one can print a PDF file.

Advantages: very accurate in compliance with all sizes and locations of components, correct watermarks printing and several other intersecting elements of the report, report preview before sending it for printing.

Disadvantages: a special plug-in Adobe Acrobar Reader is required to be installed on a local computer.

Printing with Preview:

In this mode, the report engine generates a report as an HTML page that is displayed in the client’s browser. Printing can be performed out of this browser.

Advantages: It is possible to see a report before sending it to the printer, and cancel printing if there is something wrong with the report.

Disadvantages: Difficulty in previewing large reports, because in preview the entire report without paging is displayed.

Printing without preview:

In this mode, the report engine generates an invisible field on the page of StiWebViewer, in which the report as an HTML page is placed. After that, the client’s browser, using CSS, runs printing of compiled HTML pages.


Fast printing, "in three clicks": select the menu item Print -> the printer -> click the Print button. Disadvantages: You must be sure that the report will be printed correctly.

2) Save the report in the specified file format. In a special menu Save, you can select the file format for the report be saved in.


3) Show the first report page.

4) Show the previous report page.

5) This field shows the number of a page being displayed.

6) Show the next report page.

7) Show the last report page.

8) Select report zoom.

9) Report display mode. The control sets the display mode of the report.

Show page only.

Show the entire report.
If your firm is forced to create many similar reports, but in different languages, this article will definitely help you. You have probably already used to that if it comes to the crunch Stimulsoft is always happy to help. This issue is no exception. Stimulsoft Reports for solving such problems offers the Globalization Editor. With this editor it becomes possible to localize the report in several languages. The editor is easy to find, just follow the picture shown below:

WinForms Reports Designer (Office 2010 interface)

First, you must set the Auto Localize Report on Run property to Yes (this property is shown in the picture and described below). This allows checking the culture of the operating system.

Culture? Yes, the culture. Culture is an identifier of the language settings of your operating system. For example: Ru or En.

Finding the culture, the report generator checks cultures used in a report and are presented in the list. If identical cultures found, then all expressions in the report will be substituted. As a result, the report will be localized in the culture of the installed operating system, according to the parameters set in the Globalization Editor.

If culture of the operating system is not in the list of cultures used in the report, then the report will not be localized.

When set the Auto Localize Report on Run property to No, automatic localization will not work.

Let’s review the Globalization Editor:


1) The Add Culture button. Used to add a new culture selecting from a list of proposed cultures.

2) The Remove Culture button. Used to remove the selected culture.

3) The Close button. Used closes the Globalization Editor.

4) The Auto Localize Report on Run property, depending on the state, enables or disables report localization. If this property is set to Yes - localization is enabled, if to No - localization is disabled.

5) A list of cultures used in this report.

6) A list of components for localization.

What is globalization? This item is a list of all the major elements. By selecting one of the elements we associate with it the value of the crop.

7) Localization of the contents of the selected component.

8) A list of system variables, functions, formats of the report designer.

And now the most difficult, but interesting, especially for those who know and understand what is the project code. Dear programmers, the next part of this article is for you!

Report Globalization in Stimulsoft Reports:

For report globalization in Reports.Net it is necessary to call a special method before report rendering and displaying:
StiReport report = new StiReport();
string cultureName = "en";
cultureName - determines what language will be used in the globalization of the report. This culture should be defined in a report in the collection of globalization; otherwise globalization will not be performed.

For report globalization in Reports.Fx for Flex it is necessary to call a special method before report rendering and displaying:

var report: StiReport = new StiReport();
var cultureName: String = "en";
cultureName - determines what language will be used in the globalization of the report. This culture should be defined in a report in the collection of globalization; otherwise globalization will not be performed.

For report globalization in Reports.Fx for PHP it is necessary to set the value of globalization to GET or POST request when viewing the report:


globalization - determines what language will be used in the globalization of the report. This culture should be defined in a report in the collection of globalization; or globalization will not be performed.

For report globalization in Reports.Fx for Java you must set the globalization parameter when viewing the report:
<stiviewerfx:button value="Show Report" report="Report.mrt" variableStr="globalization=en" />
globalization - determines what language will be used in the globalization of the report. This culture should be defined in a report in the collection of globalization, or globalization will not be realized.

Finally we want to give one advice. Would you like to have the best reports at the right time with minimum effort to create them? Use software from Stimulsoft Company. Would you like to be informed of all new products in the world of reporting? Visit our blog more often.
The fifth and the final article from the series "Conditions - Understandable for Everyone" will unveil all the questions you may have about the Icon Set Condition. In previous articles we reviewed Conditions in general and their types Highlight Condition, Data Bar and Color Scale Condition.

The Icon Set Condition is one of the easiest Conditions type. It may seem that the Icon Set simply marks components in the report, but it is not correct. Besides the basic functions of "visual selection", this Condition sorts components by specified condition, assigning an icon to each data category. And the variety of icons is vast. Sorting itself can be performed from two to five values that can embrace the most sophisticated report. How it works? Minimum and maximum values for all the values in the selected data column are specified. All the calculated values fall in the range from 0 to 100 percent. Then the condition and range values for each icon are set. If, for example, you select a group of three icons, each of the selected icon has its own sub-range. This provides an opportunity to identify every component with a value, depending on the sub-range. The picture below shows the Icon Set dialog.


1. Field Column. Indicates data column from which values will be taken to fulfill the necessary condition.

2. A menu to select a group of icons, the most appropriate for the report style:


3. Button Reverse. Used to set icons in the reverse order.

4. Field Alignment. Used to specify the icons location in a component.


5. Field Icon. Shows order of selected icons, but also allows selecting an individual icon for each value in the report.


6. Filed Sub-Condition. It includes the fields: Operation, Type, Value. Each field line indicates a condition in which each value of the selected component is assigned to a particular icon.

Field Operation. Used to change the operation type of the Sub-Condition. The picture below shows the Operation menu:


Field Type. Used to change the value type of the sub conditions. There are two values: Percentage and Value.


Field Value indicates the value of the sub-condition by which to sort.

Let's review an example for better understanding how the Icon Set Condition works. In the example, we need to visually highlight the values by the ProductName column depending on the values located in column UnitsInStock. Before applying the Icon Set the report looks as shown in the picture:


Let's describe all the actions we need to do to apply the Icon Set Condition.

Select the component {Products.ProductName} in the DataBand to which the condition will be applied.


Clicking the button Conditions, invoke the conditions editor from the drop down list by selecting the Icon Set Condition.


Define the data column in the field Column.


Select an icons set from the list.


Set the position of icons in the component.


Select the type of operation, condition and set the values by which to sort.


After clicking Ok, go to the Preview. The result of applying the Icon Set Condition can be found in the picture below.


As a result of the articles series "Conditions - Understandable for Everyone" we can conclude that Conditions is not only convenient, useful, and absolutely easy to use tool in the reporting tool Stimulsoft Reports. Thanks to it, we can modify reports adding simplicity and clarity of its perception and rationalization, because now all the important elements will not remain without attention. If, before reading these articles, the Conditions tool caused difficulties or even stood aside, after reading this article series, this tool should become more than understandable. So, design reports, call the conditions editor and create!