Common Parameter Combination for Templates

Version

Application Scenarios

If there are multiple parameters, it is cumbersome to re-select each parameter before query every time you open templates. In most cases, parameter combinations used are relatively fixed. Therefore, FineReport V11.0 allows you to save historical parameter combinations, intelligently judging and recommending parameter combinations for you.

Notes

1. Common parameter combinations are stored based on template ID. New templates do not inherit the former settings on common parameter combinations after you replace or resave templates, unless you copy templates directly. (In the latter case, common parameter combination modifications take effect on both new and former templates.)

2. Common parameter combinations can only be used in the login status. If templates do not display common parameter combinations, you can use the fine_username parameter to confirm if the system is in the login status.

3. Common parameter combinations are not supported on mobile terminals or Engine-X/Row-based Engine plugins.

Open the template Visit Statistics Dashboard under the path %FR_HOME%\webroot\WEB-INF\reportlets.

Go to the parameter panel editing page and tick Use Parameter Combination under Attributes > Advanced.

Log in to the decision-making system as the admin/common user and set common parameter combinations in the template preview page, as shown in the following figure.

Note:

The system displays the parameter combination function and saves parameter combinations set by users only in the login status.

When you assign values to widgets through common parameters, the Edit End events of widgets will not be triggered. In FineReport V11.0.5 and later versions, you can trigger it by selecting Trigger Edit Exit Event on the parameter panel. /

To automatically query reports after switching parameter combinations, you need to add Edit End events that can automatically trigger queries for parameter widgets, and select Trigger Edit Exit Event. /

The JavaScript code for the widget Edit End event is as follows:

_g().parameterCommit();

Saving New Parameter Combinations

Set Region to New York, City to New York, and Customer to L Brands, click Save as Common Combination, name the combination as Combination 1, and click Save to create a parameter combination.

When you preview the template, select Combination 1 and the saved values can be automatically filled in the widget.

Note:

A user can save up to 9 parameter combinations (including intelligent recommendations) for one template. A warning message pops up with more than 9 combinations: Template parameter save up to 9.

Modifying Original Parameter Combinations

Select Combination 1, change Customer to Sysco, click Save as Common Combination, and click Save in the pop-up dialog box.

Sorting

Select Combination 1 and drag it to the middle of Combination 2 and Combination 3 to finish sorting.

Deleting

Select a combination, click the X icon, and click OK in the pop-up dialog box.

Renaming

Double-click the combination name to rename the parameter combination.

According to the used parameter combinations based on your historical operation records (saved in the fine_record_param table), the system recommends the two most commonly used parameter combinations used more than seven times within the past seven days by default.

From the server startup, it first recommends at 00:01 A.M. the next day and then recommends every 24 hours.

Note:

Saved combinations will no longer be recommended.

fine_param_template

The fine_param_template table in FineDB stores parameter combinations saved by different users, as shown in the following table.

The decrypted recommendation parameter combinations information (in .json format and stored in TPGROUP) is as follows:

• name: name of the recommended parameter combination

• id: widget ID

• value: data value

• encrypt: determine whether it is encrypted, with false referring to no encryption for non-password controls and True to encryption for password widgets.

• type: determine whether it is an intelligent recommendation.

Note:

The data order in the data field represents the data usage frequency. The more commonly used a data field is, the higher it is sorted.

{
    name: 'xxx',
    data: {
        id1 : 'value1',encrypt:'flase'
        id2 : 'value2',encrypt:'flase'
        ...
        id9 : 'value9',encrypt:'flase'
    }
    type:'flase'
}

fine_record_param

The fine_record_param table in LogDB stores detailed usage history records of different users, as shown in the following table.