[General] Subtemplate Opening and Return Logic in Mobile Preview

When a mobile template includes hyperlinks, the hyperlink opening and return logic differs from that on the PC.

The following table describes the logic.

When you preview a template configured with a Web Report hyperlink on a mobile device, the title of the linked subtemplate is determined by the hyperlink name.

Note: 

For details about how to customize the title of a subtemplate opened through a JavaScript hyperlink, see [General] Custom Subtemplate Title for JavaScript Hyperlink.

For example, you can name the Web Report hyperlink Subtemplate Name in the designer, as shown in the following figure.

When you open the subtemplate from the main template on a mobile device, the displayed title is also Subtemplate Name, as shown in the following figure.

Notes:

For FineReport earlier than V11.0.76, the subtemplate title displayed in HTML5 clients is not aligned with the hyperlink name. You need to manually configure the title in the template.

For general reports, open the subtemplate, choose Template > Web Attribute > Basic > Title, and set a custom title, as shown in the following figure.

For FRM reports, open the subtemplate, choose Component Setting > form > Title, and set a custom title, as shown in the following figure.

For mobile previews, when you navigate back from the subtemplate to the main template, the return logic is as follows:

• If both the main template and the subtemplate are CPT templates, the main template retains its original state without a page refresh.

• If either template is an FVS dashboard, the main template is refreshed when you navigate back, causing its page state to be lost. Starting from the FineVis Data Visualization plugin V4.9.0 and HTML5 Mobile Display plugin V11.5.10, you can append the parameter fvs_route=true to preview URLs to retain the original page state without a refresh in some scenarios when you navigate back from a linked subtemplate. The supported scenarios and rules are as follows:

1. For templates mounted to the platform and previewed from directory entries, if FVS and CPT templates navigate to each other through hyperlinks, appending this parameter prevents the main template page from refreshing when you navigate back.

Note: 

The function is supported only for directory template entries. Common page entries and homepage entries are not supported.

For example, http://localhost:8075/webroot/decision/url/mobile?fvs_route=true#/directory

2. When a CPT template is configured with a hyperlink to an FVS dashboard, appending this parameter prevents the main template page from refreshing when you navigate back.

For example, http:/localhost:8075/webroot/decision/view/report?fvs_route=true&op=h5 write&viewlet=WorkBook1.cpt#/report

3. When an FVS dashboard is configured with a hyperlink to a CPT template, appending this parameter does not prevent the FVS dashboard from refreshing the first time you navigate back to it.

Note: 

After the parameter is appended to prevent page refresh on back navigation, all subsequent hyperlink navigation follows the same return logic. For example, if you navigate from FVS1 to a CPT template and then navigate back directly, FVS1 is refreshed. However, if you navigate from FVS1 to a CPT template, and then from the CPT template to FVS2 through a hyperlink with fvs_route=true appended, navigating back from FVS2 to the CPT template does not refresh the CPT template. Subsequent back navigation also does not refresh pages.

You can append fvs_route=true directly to the preview URL, or append it to the CPT template path configured in the FVS dashboard, as shown in the following figure.

4. When hyperlinks in an Iframe component or widget open a subtemplate in a new window, the main template does not refresh when you navigate back if it is a CPT template, but refreshes if it is an FVS dashboard.