Inserting library component references
Inserting report data components
Inserting analysis templates as components
Inserting a label/dashboard title
You can insert library components and report data components as well as labels, images, special fields, filtering tools, third-party objects, and HTML components into dashboards via the Resources panel. To access the panel, click the Show Resources button on the toolbar.
When inserting a library component from the component library into a dashboard, you are not copying it from the component library, but instead referencing it. In this sense, when a library component is edited in JReport Designer and republished to the component library, the changes will be reflected in all the dashboards that reference the library component, and any changes made to a library component in a dashboard will be saved into the dashboard only without affecting the source library component. However, if the same change in a library component is made both at design time in JReport Designer and at runtime in a dashboard, the runtime change has higher priority.
To reference a library component into the dashboard body:
Data components such as tables, crosstabs, charts, KPI components, and geographic maps in reports can be directly inserted into dashboards after being converted into library components automatically.
For reports that use business views as data sources, all data components can be converted to library components successfully.
However, page reports may use queries as data sources other than business views, therefore, only when the queries have corresponding business views, can the components be converted to library components and used in dashboards. So if you would like your page report components to be added in dashboards, you need to make sure the components are created on business views or if on queries a business view is created using each of the queries.
Currently library components do not support some features of page report components, after the latter are inserted into dashboards, those features will be removed. This may result in that the data components in dashboards look different from when they are in page reports. For features that are not supported in JDashboard, they will either be ignored, removed, or applied with the default values.
The following table lists how JDashboard deals with the unsupported page report features:
In Page Report Components | In Library Components |
---|---|
Display types like Barcode, Check box, and so on | Ignored |
Special fields | Removed |
Dynamic resources | Changed to constant resources |
Master/Detail reports | Ignored |
Subreports | Removed |
Nested data components that is one contains another | The ownership is removed and the involved data components are regarded as individual components. |
Definition properties | Ignored |
Formula-controlled properties | Default values are applied. |
Other components | Removed |
To insert a report data component into the dashboard body:
The inserted report data component runs with the report's catalog so it will not be able to run if the catalog is removed or updated. The report data component is not controlled by the runtime filters.
Analysis templates after being saved into the server resource tree can be inserted into dashboards as components. This feature requires a license for Visual Analysis.
To insert an analysis template as component into the dashboard body:
The inserted analysis template will be wrapped into a runtime library component and its data presentation area and legend area without legend icons will be displayed, just for viewing. However if no field binds with any legend, the legend area will not be shown. The default title is the server resource name of the parent analysis template without the suffix .va.
The inserted analysis templates cannot be exported or printed, therefore when exporting or printing a dashboard, they will not be listed and the cells containing them will be left blank.
Labels can be inserted in the dashboard header. A dashboard title is a special label.
Images can be inserted in the dashboard header.
Special fields can be inserted in the dashboard header.
You can insert these types of special fields in the dashboard header:
Filter controls can be inserted in the dashboard body. They are used to filter component data. For details, see Filtering Component Data.
A web page can be inserted in the dashboard body. All you need to do is give its URL. Note that some websites such as http://www.google.com
do not allow Gadgets to load them.
You should provide a complete URL address. A URL without "http://", for example www.jinfonet.com, will not be automatically added "http://" since it is regarded a relative path, which may lead to that the URL cannot be opened in some browsers.
An HTML component allows for typing text, comments, and messages using a simple-featured text editor. It can be inserted in the dashboard body.