Engine-X Usage

This article describes how to use Engine-X. The engine-X function setting page is shown as follow：

Note: The features introduction of Engine-X, please refer to：Engine-X Introduction

1.Template Prepare

1）Open a cpt template，such as：%FR_HOME%\webroot\WEB-INF\reportlets\doc-EN\DataEntry\DataEntryApplication\Pagination.cpt

Click Template > Report Engine Attributes，As shown below：

2）ClickEnable background pagination，select Engine-X，then save settings，as show below：

2.Effect Preview

Click Pagination Preview，as show below：

1. Feature Introduction

• After select Pagination by Fixed Row，you can set Number of records per page

• Only support single dataset list report. If this function is not enabled in the single dataset list report, an error will be reported in the background：

• Error code: 11100052 Non-single data set schedule template cannot support calculating the total number of rows or page numbers, please adjust the template structure

• Number of records per page Include only the number of rows of vertically-expanding datasets, excluding headers and datasets that do not expand, the template will no longer be paged horizontally and no longer supports adaptive settings.

• If the number of lines set by Show Fixed Number of Row Per Page is different from the "Number of Records per Page", the "Number of Records per Page" shall prevail.

• When the extension cell used to calculate the number of rows in the template is set with filter settings that cannot be converted to sql or conditional formatting row height change, it will affect the amount of data finally displayed. When previewing, it shows that the page number/line number acquisition failed, and the background prompts an error：

• Error code: 11100050 There is a filter setting that does not support the calculation of the total number of rows, and the total number of rows or page numbers cannot be accurately calculated

• Error code: 11100051 There is a condition property setting that does not support the calculation of the total number of rows, and the total number of rows or page numbers cannot be accurately calculated

• Regardless of whether or not to set pagination by row, the export is uniformly exported by row  engine.

• If the total page number acquisition takes more than 1 minute, the acquisition will be automatically terminated, and it will not be acquired when it is suspended by intelligent O&M. At this point, the following figure is displayed：

2. Template Prepare

1）Create a new cpt template，SQL is ：SELECT * FROM 订单明细

2）The report style settings as show below：

3）A2, B2, C2, D2, E2 cell setting list, the setting method is the same, take cell A2 as an example. As shown below：

3. Effect Preview

1) Click Template > Report Engine Attributes > Enable Background Pagination > Pagination by Fixed Row, and set Number of Records per Page to 30. As shown below：

2）Click Pagination Preview，as show below：

1. Feature Introduction

• Only support single dataset list report. If this function is not enabled in the single dataset list report, an error will be reported in the background：

Error code: 11100052 Non-single data set schedule template cannot support calculating the total number of rows or page numbers, please adjust the template structure

• If the acquisition of the total data volume takes more than 1 minute, the acquisition will be automatically terminated, and it will not be acquired when it is terminated by intelligent O&M. As show below：

2. Template Prepare

Refer to Part III Template Preparation Contents.

3. Effect Preview

1) Click Template > Report Engine Attributes > Enable Background Pagination > Row Count Summary. As shown below：

2）ClickPagination Preview，as show below：

Using the cpt template of the new engine, if there are unsupported functions, an error message will be reported in the background：

Unsupported functions. The template has been saved but the paging engine cannot take effect normally, please confirm and modify the unsupported functions: XXXXXXXXX. 

At the same time, the template title shows Paging engine is not in effect, as show below：