In the web application the user can work only with ready reports. In the mobile application based on Foresight Mobile Platform the user can only view reports. Depending on the application in use there are the following differences in regular report functionality:
| Functionality | Desktop application | Web application | Mobile application |
| Building report |
|
|
|
| Working with ready report: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
NOTE. The table displays only the functionalities that differ depending on the application. The identical functionalities are not displayed.
Conventions:
- functionality is fully available.
- functionality is unavailable.
- functionality is available with features of use.
On creating a regular report in the desktop application to further open this report in the web application, follow the recommendations below.
Take into account the following features if you create a report in the desktop application to further open it in the web application:
| Constraint/feature | Recommendation |
| Cell text is wrapped in the report | Set cell width and height to fit to the whole text |
| Conditional formatting defined with histograms, does not show | Use conditional formatting based on color scales or icons |
| Diagonal cell borders cannot be seen | Set borders only using horizontal and vertical borders |
| Hatching cannot be seen | Use image fill or some fill without using hatching |
| Cell images cannot be aligned | Select the images that fit the cell size |
| Merged cells, that are only partially located in fixed area, while the other part is in a non-fixed area, can be displayed incorrectly | When creating a report, avoid merging cells that are only partially located in fixed area, while the other part is a non-fixed area |
| If rows height is auto adjusted, on export to XLS the text in the row can be partially hidden because fonts in Foresight Analytics Platform and Excel do not match | After selecting the height automatically, manually increase the row height, or do not use autofit at all |
| Multiline headers and footers are trimmed on export to RTF | Use fewer words or make the header/footer font smaller |
| Headers and footers are not exported to HTML | Warn the user that headers and footers cannot be exported before exporting the report to HTML |
| Charts and images can export to PDF incorrectly, if no background is defined for these objects | Define background color for maps and charts, for example, white color |
| Constraint/feature | Recommendation |
| Tooltips are not shown for 3D charts | Select 2D chart types if it is required to show tooltips |
| The Masked String Editor control is not supported | Use the String Editor control and check the entered data |
| Element groups and selection schemas are not available when working with dimension elements | Use hierarchical dictionaries elements of which are already grouped to different levels as data sources for dimensions |
| Information messages called from units used for report event handling, are not supported | Replace information messages with another method of informing the user. For example, show information on a separate report sheet |
| Page break cannot be inserted into a report sheet | Create a report without using page breaks |
| Formulas using OR statement are not exported to XLS. Such as: =(C2=0) or (D2=0) | It is recommended to export into XLS format the values calculated by formulas instead of formulas |
To correctly display reports on tablets, set up report formatting in the desktop application taking into account guidelines for building reports.
NOTE. The report appearance with configured formatting for the mobile application may differ when the report is viewed in the web application.
For details see the Dashboards and Reports Building Guidelines section.
See also:
Getting Started with the Reports Tool
Features of functionality use