Overview
Application scenarios: If you have installed the FVS plugin, you can view this article to learn about functions related to FVS templates.
Note: Mobile devices are not supported.
Version
Report Server Version | Plugin Version | Function Changes |
11.0.6 | 1.8.0 | For all widgets, Visible on preview option was deleted in Content > Permission, but you can hide widgets in the Widget Layer. For details, see “Hiding or Displaying Widgets”. |
11.0.6 | 1.5.0 | Widget was added in this version and there are six types of widgets. |
Application Scenarios
Widget is widely applied in the report or dashboard.
In the FVS large screen template, widgets are used as components directly added to the pages. Therefore, widgets also support component attributes: FVS Component Animation, FVS Component Basic Attributes.
This article will mainly introduce other common properties of Widget in FVS.
Widget Types
Widget Types | Introduction |
When previewing the template, you can manually input values in the text box and other components will be linked through parameters. | |
When previewing the template, you can select the date and time, and other components will be linked through parameters. | |
When previewing the template, you can drop the options down, and other components will be linked through parameters. | |
When previewing the template, you can drop the options down and multiple selections are supported. Other components will be linked through parameters. | |
When previewing the template, you can select button options and other components will be linked through parameters. | |
When previewing the template, multiple button options can be selected and other components will be linked through parameters. |
Functions
Widget Name
1. The name of the widget is used to bind parameters. When you need to link parameters with other components, set the widget name to be the same as the parameter.
For example, if the parameter area is used to represent the region, the widget name also needs to be area.
2. The widget name is not set in Component configuration panel, but in Content configuration panel. As is shown below:
3. Widgets with the same name are not supported in the same page. In different pages, widgets with the same names are supported to represent the same parameter.
Hiding or Displaying Widgets
In the 1.8.0 version, Visible on preview setting for all widgets have been cancelled. Instead, you can hide components in the Widget Layer list.
As is shown below:
Widget Query Logic
1. In FVS, the widget will automatically trigger a query after the value is modified. Components related to the widget parameter will be refreshed, which will take effect on all pages of the entire template.
For example, if both page 1 and page 2 have charts that reference the area parameter, altering the value of the drop-down widget parameter on page 1 will cause both charts on page 1 and page 2 to change accordingly.
As is shown below:
2. In different pages, widgets with the same name are considered as the same parameter.
When previewing the template, if the value of a widget on any page is altered, widgets with the same name on other pages will change accordingly.
In the template editing interface, the default values of widgets with the same name in different pages will be overlapped with each other, and the default value of the last operated widget will prevail.
For example:
Both page 1 and page 2 have a text box widget named area. If you set the default value of the text box widget on page 1 as East China, the default value of the text box widget on page 2 will also display East China. If you alter the default value of the widget as North China on page 2, and the default value of the widget on page 1 will also be changed to North China.
The same goes for previewing.
Widget Events
The events currently supported by the FVS widgets include: After Initialization Event, After-load Event and Click Event.
Click Event | After Initialization Event | Edit Finish Event | Component |
supported | supported | unsupported | ButtonGroup, CheckboxGroup |
unsupported | supported | supported | Textbox, DateTime, Drop-downBox, Drop-downCheckbox |
FVS supports the following widget interfaces. For details, see Widget Object.
To use the widgets, you can refer to the usage of widgets in the body of dashboard. Remember to replace the interface_g() used to obtain the object with duchamp.
Interfaces | Introduction | Examples |
getValue | get the actual value of the widget | duchamp.getWidgetByName(“widget name”).getValue(); |
get Text | get the display value of the widget | duchamp.getWidgetByName(“widget name”).getText(); |
setValue | set the value of the widget | duchamp.getWidgetByName(“widget name”).setValue(‘text’); |
setVisible | set the widget visible/invisible | duchamp.getWidgetByName(“widget name”).setVisible(false); |
isVisible | whether the widget is visible or not return true indicates visible return false indicates invisible | duchamp.getWidgetByName(“widget name”).setVisible(false); |
setEnable | enable/disable the widget | duchamp.getWidgetByName(“widget name”).setEnable(false); |
isEnabled | whether the widget is enabled or not return true indicates available return false indicates unavailable | duchamp.getWidgetByName(“widget name”).isEnabled(); |
reset | reset the widget and clear the content of the widget | duchamp.getWidgetByName(“widget name”).getText(); |
setWaterMark | add watermark text (only supports widgets with input boxes) | duchamp.getWidgetByName(“widget name”).setWaterMark(‘I am watermark’); |
For more information, see JS interface scenarios supported by FVS large screen.
Widget Styles
In the FVS template, if you click Template > Template Theme in the top menu bar to set the style of the widget components, it will take effect on all widgets in the current template.
For details, see FVS Template Theme.
Previous：FVS Tab Component
