FineDB table structure-FineReport Help Document

Last update：March 12, 2026

Overview

This document briefly introduces the table field descriptions contained in the FineDB database.

Note: 1. This document uses the built-in project database as an example. Note that field data types may differ if you are using an external database.

2. The FineDB configuration database stores project configuration information. Tables are interrelated. Arbitrary modifications may lead to serious consequences, such as project startup failure.

Do not manually add, Delete, or Modify Any data in the FineDB database! Such operation may cause irreparable bugs, and you will bear the consequences.

1.1 Table List

Classification	Subcategory	Table name	Description
Permission control	User-Department Position-Role	FINE_USER	User Table
		FINE_EXTRA_PROPERTY	User Additional Information Table
		FINE_DEPARTMENT	Department Table
		FINE_POST	Position Table
		FINE_DEP_ROLE	Intermediate table for department positions, through which users associate departments with positions
		FINE_CUSTOM_ROLE	Custom Role Table
		FINE_USER_ROLE_MIDDLE	Intermediate table for user roles, through which users associate with custom roles and department position roles
		FINE_SOFT_DATA	Synchronized user soft-delete data table, storing data from synchronized user soft-deletes
		FINE_TENANT	Tenant Table
	Permission-Directory	FINE_AUTHORITY	Permission table, which only records the permissions granted to the current directory; permissions for templates and subdirectories under this directory will not be recorded
		FINE_AUTHORITY_OBJECT	Permission entity table, recording permission objects, directory names, and report names for the current directory (excluding templates and subdirectories within it)
		FINE_AUTH_PREFERENCE	Permission panel user preference settings
		FINE_HOMEPAGE_EXPAND	Homepage expansion table Records expansion attributes of homepage-type permission entities
		FINE_FAVORITE_ENTRY	Favorite nodes table
Platform operations	Login	FINE_LAST_LOGIN	Last Login Prompt table
		FINE_LOGIN_LOCK	Login Lock table Lock due to excessive incorrect password attempts For details, see Login Lockout.
		FINE_BLOCK_IP	Log in to lock IP table Lock due to excessive access frequency from the same IP For details, see Access Control.
	Backup & Restoration	FINE_BACKUP_NODE	Backup nodes table
	Backup & Restoration	FINE_BACKUP_EXCLUDE_ENTITY	Backup exclusion information table
	Task schedule	FINE_SCHEDULE_TASK	Scheduled Task Table
		FINE_SCHEDULE_TASK_PARAM	Scheduled task parameter values
		FINE_SCHEDULE_TASK_EXTEND	Scheduled task extended attributes
		FINE_SCHEDULE_TASK_LOG	Scheduled task tree monitoring log
		FINE_SCHEDULE_RECORD	Log table recording task schedule execution
		FINE_SCHEDULE_OUTPUT	Scheduled Task Export
		FINE_BASE_OUTPUT	Task attachment processing master table
		FINE_OUTPUT_CLASS	Custom Class Processing
		FINE_OUTPUT_CLIENT_NOTICE	Client Notification
		FINE_OUTPUT_EMAIL	Push email
		FINE_OUTPUT_FTP	FTP upload
		FINE_OUTPUT_MOUNT	Scheduled task mount directory
		FINE_OUTPUT_PLATFORM_MSG	Platform system message
		FINE_OUTPUT_PRINT	Print processing
		FINE_OUTPUT_SFTP	SFTP upload
		FINE_OUTPUT_SMS	Send a text message.
		FINE_USAGE_DATA	Scheduled task reach count record table
	Message	FINE_BASE_MESSAGE	Platform message master table
		FINE_PROCESS_MESSAGE	Reporting Message
		FINE_SYSTEM_MESSAGE	Platform system message
	Report	FINE_WORKFLOW	Process in the reporting workflow
		FINE_WORKFLOW_TASK	Tasks in the reporting workflow
		FINE_WORKFLOW_TASK_IMPL	Specific tasks issued from tasks in the reporting workflow
		FINE_WORKFLOW_NODE	Nodes in the reporting workflow
		FINE_WORKFLOW_STASH_DATA	Temporary data storage in the reporting workflow
		FINE_WORKFLOW_LOG	Operation logs in the reporting workflow
System Management	Configuration	FINE_CONF_CLASSNAME	When a configuration class field is of interface type, record its type
		FINE_CONF_ENTITY	Store data from configuration classes
		FINE_CONF_XMLENTITY	Some fields have extremely complex structures; to store them in a database, they are saved in XML format
		FINE_INTERNATIONAL	Table for recording multilingual data
		FINE_LABEL	Label table
		FINE_LABEL_INDEX	Tag Relationship Table
		FINE_OPS_EXCEED_TEMPLATES	Exceed Limit Templates
		FINE_OPS_CRASH_DETAIL	Crash Record Table
		FINE_NET_CHECK_RECORD	Network Check Record Table
	SWIFT Module	FINE_SWIFT_COL_IDX_CONF	Column Index Configuration
		FINE_SWIFT_CONFIG_ENTITY	Swift Internal Configuration Table
		FINE_SWIFT_METADATA	Used to store table metadata
		FINE_SWIFT_SEG_LOCATION	Swift Segment Distribution Information
		FINE_SWIFT_SEGMENTS	Swift Segment Details
		FINE_SWIFT_SERVICE_INFO	Stores Swift service information
		FINE_SWIFT_TAB_IDX_CONF	Table Index Configuration
		FINE_SWIFT_TABLE_PATH	Cube Intermediate Directory Configuration Management
		FINE_SWIFT_CLUSTER_SIZE	Deprecated
		FINE_SWIFT_DAYS_RECORD	Daily access statistics cache table
		FINE_SWIFT_FILEKEY	Time index table for Swift data blocks (seg)
		FINE_SWIFT_RESTORE_RESULT	Log restoration temporary records
	Quartz Module	QRTZ_BLOB_TRIGGERS	Triggers stored as Blob type
		QRTZ_CALENDARS	Calendar information storage table
		QRTZ_CRON_TRIGGERS	Storage for Cron-type triggers
		QRTZ_FIRED_TRIGGERS	Storage for fired triggers
		QRTZ_JOB_DETAILS	Storage for JobDetail information
		QRTZ_LOCKS	Storage for pessimistic lock information of programs
		QRTZ_PAUSED_TRIGGER_GRPS	Storage for paused Trigger group information
		QRTZ_SCHEDULER_STATE	Storage for cluster node instance information
		QRTZ_SIMPLE_TRIGGERS	Simple trigger information
		QRTZ_SIMPROP_TRIGGERS	Stores CalendarIntervalTrigger and DailyTimeIntervalTrigger
		QRTZ_TRIGGERS	Basic information of triggers
Other modules	Mobile Terminal	FINE_MOBILE_DEVICE	Mobile Device Table
		FINE_MOBILE_PUSH_MESSAGE	Mobile message push table
		FINE_WEIXIN_USER_RELATION	Platform and WeChat user mapping table under manual matching
		FINE_WEIXIN_OUTPUT	Scheduled task information for WeChat push
		FINE_WEIXIN_AGENT	Application information table in WeChat management
		FINE_WEIXIN_GROUP	WeChat group information table in WeChat management
		FINE_DINGTALK_USER_RELATION	Platform and DingTalk user mapping table under manual matching
		FINE_DINGTALK_OUTPUT	Scheduled task information for DingTalk push
		FINE_DINGTALK_AGENT	Application information table in DingTalk management
		FINE_DINGTALK_GROUP	DingTalk group information table in DingTalk management
		FINE_FEISHU_USER_RELATION	Platform and Feishu user mapping table under manual matching
		FINE_FEISHU_OUTPUT	Scheduled task information for Feishu push notifications
		FINE_FEISHU_AGENT	Application information table in Feishu management
		FINE_FEISHU_GROUP	Feishu group information table in Feishu management
	Report	FINE_PARAM_TEMPLATE	Parameter Combinations for Templates
		FINE_PRINT_OFFSET	/
		FINE_PRINT_OFFSET_IP_RELATE	Print offset IP association table
		FINE_REMOTE_DESIGN_AUTH	Remote design user table
		FINE_WRITE_STASH	Data Entry Temporary Storage Table
		FINE_PROCESS_EXPAND	Expansion attribute table for reporting process type permission entities, i.e., related attributes configured in the decision-making platform directory for reporting processes, including name, path, description, type, display terminal, parameter settings, etc.
		FINE_REPORT_EXPAND	Expansion attribute table for report type permission entities, i.e., related attributes configured in the decision-making platform directory for reports, including name, path, description, type, display terminal, parameter settings, etc.
		FINE_EXCEL_SUBMIT_TASK	Excel batch import permission entity expansion table
		FINE_VCS	Template Version Management Table
		FINE_COMPONENT_HEALTH	Component health record table
	Open platform related	FR_OPEN_API	API Information
		FR_OPEN_APP	Customer Information
		FR_OPEN_AUTH	Permission Information
		FR_OPEN_GROUP	API Group Name
		FR_OPEN_PRIVILEGE	Open Platform Permission Table
		FR_OPEN_RELATION	Group and API Association Table
		FR_OPEN_API_PERFORMANCE	API Query Rate
	Multi-Product Connection Plugin	FINE_COORDINATOR_ENTRY	Template from Server
	Multi-Product Connection Plugin	FINE_COORDINATOR_SERVER	Server Information

1.2 Table Relationships

1.2.1 Permissions

1.2.2 Reporting

1.2.3 Scheduled Tasks

1.2.4 Messages

1.2.5 Printing

Note: Based on the above table structure, and since the tables are not directly related, manual deletion of data in intermediate tables is required for direct database operations.

For example: Deleting a department = Delete department + Delete dep_role + Delete user_role_middle;

Deleting a user = Delete user + Delete user_role_middle + Delete extra_property.

2. User-Department Position-Role

2.1 FINE_USER User Table

Field Name	Description	Data Type	Length
ID	Primary key Associated table fields fine_extra_property>relatedId fine_user_role_middle>userId fine_base_message>userId fine_auth_preference>userId fine_favorite_entry>userId fine_last_login>userId fine_login_lock>userId fine_workflow_task>creatorId fine_authority>roleId	VARCHAR	255
BIRTHDAY	Birthday	TIMESTAMP	26
CREATIONTYPE	Creation type: Manual creation Synchronous creation	INTEGER	32
DESCRIPTION	Description	VARCHAR	1000
EMAIL	Mailbox	VARCHAR	255
ENABLE	Enabled true: enabled false: disabled	BOOLEAN	0
LANGUAGE	Internationalization language	VARCHAR	255
LASTOPERATIONTYPE	Last modification type 1: Manual modification 2: Synchronized modification	INTEGER	32
MALE	Gender true: male False: female	Boolean	0
MOBILE	Telephone number	VARCHAR	255
PASSWORD	Password This field contains the encrypted ciphertext of the platform user password and does not affect the platform user's ability to log in to the decision-making platform. The built-in encryption method is SHA256 Ciphertext after custom encryption	VARCHAR	255
REALNAME	Name	VARCHAR	255
USERNAME	Username Associated table fields fine_base_message>userName fine_workflow_task>creatorName fine_schedule_record>creator fine_schedule_task>creator	VARCHAR	255
WORKPHONE	Mobile Number	VARCHAR	255
REALALIAS	Sorting index for realName For example, if the name is Anna, REALALIAS would be an FR: New field added for JAR versions from 2019-12-05 onwards BI: JAR files released on or after 2020-01-15, newly added fields.	VARCHAR	255
USERALIAS	Sorting index for userName For example, if the username is Alice, USERALIAS would be alice FR: New field added for JAR versions from 2019-12-05 onwards BI: JAR files released on or after 2020-01-15, newly added fields.	VARCHAR	255
TENANTID	Tenant_ID Currently unused, reserved field	VARCHAR	255
SALT	Salt parameter When user password is updated, the salt value is also updated to enhance security FR: New field added for versions 10.0.18 and later BI: New field added for versions 5.1.15 and later	VARCHAR	255

2.2 FINE_EXTRA_PROPERTY User Additional Information Table

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
NAME	Attribute name, distinguishing user types used by the platform user_product_type.platform.bi_datamining: Super admin user_product_type.platform: PC end user user_product_type.platform.bi_view: BI user - viewer user_product_type.platform.bi_design: BI user - designer user_product_type.mobile: Mobile end users user_product_type.platform.fdl: fdl data development users	VARCHAR	255
RELATEDID	User ID Associated table field fine_user>id	VARCHAR	255
TYPE	Type of associated data item	INTEGER	32
VALUE	Property Value	VARCHAR	65536

2.3 FINE_DEPARTMENT Department table

Field Name	Description	Data Type	Length
ID	Primary key Associated table field fine_dep_role>departmentId	VARCHAR	255
CREATIONTYPE	Creation type: Manual creation Synchronous creation	INTEGER	32
DESCRIPTION	Description	VARCHAR	1000
ENABLE	Enabled true: enabled false: disabled	BOOLEAN	/
LASTOPERATIONTYPE	Last modification type 1: Manual modification 2: Synchronized modification	INTEGER	32
NAME	Department name	VARCHAR	255
PARENTID	Parent department ID	VARCHAR	255
FULLPATH	Department full path Grandparent department ID Parent department ID ... FR: new field added for JAR packages generated at and after 2019-05-20) BI: new field added for JAR packages generated at and after 2019-06-13)	VARCHAR	65536
ALIAS	NAME sort index For example, if the department is the leadership department, ALIAS is ldb FR: JAR from 2019-12-05 onwards, new field added BI: JAR from 2010-01-15 onwards, new field added	VARCHAR	255
TENANTID	Tenant_ID No current use, reserved field	VARCHAR	255

2.4 FINE_POST Position table

Field Name	Description	Data Type	Length
ID	Primary key Related table field fine_dep_role>postId	VARCHAR	255
CREATIONTYPE	Creation type: Manual creation Synchronous creation	INTEGER	32
DESCRIPTION	Description	VARCHAR	1000
ENABLE	Enabled or not 1: Enabled 0: Disabled	BOOLEAN	0
LASTOPERATIONTYPE	Last modification type 1: Manual modification 2: Synchronized modification	INTEGER	32
NAME	Position Name	VARCHAR	255
ALIAS	NAME sorting index For example, if the position is Development Engineer, the ALIAS would be kfgcs FR: New field added for JARs from 2019-12-05 onwards BI: new field added for JAR packages generated at and after 2020-01-15)	VARCHAR	255
TENANTID	Tenant_ID No current use, reserved field	VARCHAR	255

2.5 FINE_DEP_ROLE Intermediate table for department positions

Field Name	Description	Data Type	Length	Remark
ID	Primary key	VARCHAR	255	Related table field fine_user_role_middle>roleId
CREATIONTYPE	Creation type: Manual creation Synchronous creation	INTEGER	32	/
DEPARTMENTID	Associated department and position ID departmentId is empty and postId is empty: indicates the root department departmentId is empty and postId is not empty: indicates a position under the root department (default does not exist) departmentId is not empty and postId is empty: indicates a department without positions departmentId is not empty and postId is also not empty: indicates a normal department position	VARCHAR	255	Associated table field fine_department>id
POSTID		VARCHAR	255	Associated table field fine_post>id
LASTOPERATIONTYPE	Last modification type 1 - Manual modification 2 - Synchronized modification	INTEGER	32	/
FULLPATH	Complete path of intermediate data	VARCHAR	65536	/
TENANTID	Tenant_ID	VARCHAR	255	Currently unused, reserved field

2.6 FINE_CUSTOM_ROLE Custom role table

Field Name	Description	Data Type	Length
ID	Primary key Associated table field fine_user_role_middle>roleId	VARCHAR	255
CREATIONTYPE	Creation type: 1: Manually created by administrator 2: Synchronized dataset creation	INTEGER	32
DESCRIPTION	Description	VARCHAR	255
ENABLE	Enabled true: enabled false: disabled	BOOLEAN	/
LASTOPERATIONTYPE	Last modification type 1: Manual modification 2: Synchronized modification	INTEGER	32
NAME	Role Name	VARCHAR	255
ALIAS	NAME sorting field index For example, if the role is project operations, ALIAS would be xmyw FR: New field added in JAR from 2019-12-05 onwards BI: (new field added for JAR packages generated at and after 2020-01-15)	VARCHAR	255
TENANTID	Tenant_ID No current use, reserved field	VARCHAR	255

2.7 FINE_USER_ROLE_MIDDLE Intermediate table for user roles

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
ROLEID	Associated generalized role ID depRoleId or customRoleId Associated table field fine_dep_role>id fine_custom_role>id fine_authority>roleId Note: Different departments and roles of a user will be stored as multiple records.	VARCHAR	255
ROLETYPE	Associated generalized role type 1: Department position 2: Custom role	INTEGER	32
USERID	Associated user ID Associated table field fine_user>id	VARCHAR	255
TENANTID	Tenant_ID No current use, reserved field	VARCHAR	255

2.8 FINE_SOFT_DATA Synchronized user soft-delete data table

Data deleted from the synchronization source is physically deleted from FineDB, while different types of data are saved in the soft-delete table.

Data restored from the synchronization source is recovered from the soft-delete table. The IDs of fields with the same name remain unchanged, ensuring no impact on permissions.

Field Name	Description	Data Type	Length	Remark
ID	Primary key	VARCHAR	255	/
DELETEDID	ID to be deleted	VARCHAR	255	1) Fields DELETEDID + TYPE form a unique key Meaning no two records can have identical DELETEDID and TYPE values 2) Fields DELETEDNAME + TYPE form a unique key Meaning no two records can have identical DELETEDNAME and TYPE values
DELETEDNAME	Name to be deleted User: username Department: Computed full department name Position: Position name Role: Role name Department Position: Department ID + Position ID	VARCHAR	255
TYPE	Deleted Data Types 1: Department 2: Role 3: User 4: Position 5: Department-Position intermediate table 6: Synchronize user and manually customized role relationship data 7: Synchronize user and department position relationship data	INTEGER	32

2.9 FINE_TENANT Tenant table

No current use

Field Name	Description	Data Type	Length
ID	User ID	VARCHAR	255
NAME	Username	VARCHAR	255

3. Permissions-Directory

3.1 FINE_AUTHORITY Permissions table

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
AUTHORITY	Permission value 1: Deny 2: Allow	INTEGER	32
AUTHORITYENTITYID	Associated permission entity ID Associated table field FINE_AUTHORITY_OBJECT>id	VARCHAR	255
AUTHORITYENTITYTYPE	Associated authority entity type Platform type 0: Directory permissions, management system permissions, entities are all in the authority_object table 1: Personnel management - department permissions, personnel management - role permissions 2: Permissions on Data Connection 7: Scheduled task permissions 8: Server Dataset Report Type 101: FineReport template permissions (template authentication) BI type 201: BI business package permissions 202: BI business package row filter permissions (not externally perceivable) 203: BI dashboard permissions (mainly used for sharing) 204 - BI template permissions (template authentication) 205 - BI dashboard sharing control (role to role) 206 - BI self-service dataset sharing 207 - BI self-service dataset sharing (role to role) FDL:* 320: Module directory 321: Scheduled 322: Pipeline 323: Service	INTEGER	32
AUTHORITYTYPE	Permission Type Platform type 1: View permission 2: Grant permissions 3: Edit permissions 4: Data connection management permissions 7: Scheduled task management permissions 9: Management Permission on Personnel Management 10: Server dataset management permissions Report Type 101: FineReport template authentication permissions 102: FineReport template view permission 103: FineReport template data entry permissions 104: Batch import task permissions 105: FineReport Reporting Process Permission BI type 201: Business Package Usage Permission 202: Business Package Management Permission 203: BI Report Export Permission 204: BI Dashboard Sharing Permission 205: BI Template Certification Permission 206: BI Template View Permission 207: BI Template Export Permission 208: BI Dashboard Sharing Role Control Permission 209: BI Dashboard Sharing Function Permission 210: BI Dashboard Public Link Function Permission FDL Module: (All are management permissions; authorization permissions refer to the corresponding "Platform Type" field) 320: Data Catalog Permission 321: Scheduled Task Permission 322: Pipeline Task Permission 323: Data Service API Permission 324: Data Service Application Permission	INTEGER	32
ROLEID	Associated Generalized Role ID Related table field fine_dep_role>id fine_custom_role>id fine_user_role_middle>roleid fine_user>id	VARCHAR	255
ROLETYPE	Associated Generalized Role Type 1: Department, Position under Department 2: Custom Role 3: User 4: Position	INTEGER	32
TENANTID	Tenant_ID No current use, reserved field	VARCHAR	255

3.2 FINE_AUTHORITY_OBJECT Permission Entity Table

Contains directory information, management system

Field Name	Description	Data Type	Length
ID	Primary key Related table field FINE_AUTHORITY>AUTHORITYENTITYID	VARCHAR	255
EXPANDID	Associated expansion attribute record ID	VARCHAR	255
EXPANDTYPE	Associated expansion attribute type Platform type 1: Platform management system node 2: Homepage 3: Directory 5: Link 6: File Report Type 101: Reporting workflow 102: FineReport Report BI type 201: BI report	INTEGER	32
PARENTID	Associated parent node ID	VARCHAR	255
COVERID	Cover ID System Management>Appearance Configuration>Directory cover in directory style	VARCHAR	255
DESCRIPTION	Description	VARCHAR	65536
DEVICETYPE	Display Type 0: PC, tablet, and mobile not selected 1: PC 2: Tablet 3: PC and tablet 4: Mobile 5: PC and mobile selected 6: Tablet and mobile selected 7: PC, tablet, and mobile selected	INTEGER	32
DISPLAYNAME	Display report name and directory name	VARCHAR	255
ICON	Icon ID Directory icons in System Management > Appearance Configuration > Directory Style	VARCHAR	255
PATH	Path, meaning varies by entry type	VARCHAR	255
SORTINDEX	Sort order	BIGINT	64
MOBILEICON	Mobile icon ID	VARCHAR	255
FULLPATH	Entity full path FR: new field added for JAR packages generated at and after 2019-05-20 BI: new field added for JAR packages generated at and after 2019-06-13	VARCHAR	65536
TENANTID	Tenant_ID No current use, reserved field	VARCHAR	255

3.3 FINE_AUTH_PREFERENCE Permission panel user preference settings

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
AUTHTYPE	Permission panel type	INTEGER	32
AUTHVISIBLECFG	Permission visibility configuration	BIGINT	64
USERID	User ID Associated table field fine_user>id	VARCHAR	255

3.4 FINE_HOMEPAGE_EXPAND Homepage Expansion Table

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
ANDROIDPADHOMEPAGE	Homepage link for Android tablets	VARCHAR	1000
ANDROIDPHONEHOMEPAGE	Homepage link for Android phones	VARCHAR	1000
IPADHOMEPAGE	Homepage link for iPad	VARCHAR	1000
IPHONEHOMEPAGE	Homepage link for iPhone	VARCHAR	1000
PCHOMEPAGE	Homepage link for PC	VARCHAR	1000
TYPE	Homepage type 0: FineReport Template 1: Decision Directory 2: Hyperlink 3: FineBI template	INTEGER	32

3.5 FINE_FAVORITE_ENTRY Favorite Node Table

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
ENTRYID	Favorite report ID	VARCHAR	255
TIME	Favorite time	TIMESTAMP	26
USERID	Collection user ID Associated table field fine_user>id	VARCHAR	255

4. Log in to

4.1 FINE_LAST_LOGIN Last Log in to Information Table

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
CITY	Log in to city	VARCHAR	255
instance	IP used to log in to	VARCHAR	255
TIME	Login time	TIMESTAMP	26
USERID	Login user ID Associated table field fine_user>id	VARCHAR	255

4.2 FINE_LOGIN_LOCK Log in to Lock Table

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
ERRORTIME	Number of password errors	INTEGER	32
LOCKOBJECT	Locked IP or username	VARCHAR	255
LOCKOBJECTVALUE	Value of IP or username	VARCHAR	255
LOCKTIME	When it was locked	TIMESTAMP	26
LOCKED	Usually empty	BOOLEAN	/
UNLOCKTIME	When it will be unlocked	TIMESTAMP	26
USERID	User ID Associated table field fine_user>id	VARCHAR	255

4.3 FINE_BLOCK_IP Log in to locked IP table

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
CREATETIME	Lock time	TIMESTAMP	26
instance	Locked IP	VARCHAR	255
REJECTEDVISITS	Number of rejections	INTEGER	32

5. Backup and restore

5.1 FINE_BACKUP_NODE Backup node table

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
BACKUPMODULE	Backup module jar: JAR package jar-cluster: JAR package under cluster (special case. Under cluster, JAR backup will automatically switch to proxy implementation, hence this separate module) Plugins dashboards: BI templates reportlets: Report Templates config: Platform Configuration dpworks: Scheduled Tasks	VARCHAR	255
BACKUPNAME	Backup Name	VARCHAR	255
BACKUPTIME	Backup Time	TIMESTAMP	26
SAVEPATH	Backup Path	VARCHAR	1000
BACKUPSIZE	Backup File Size	DOUBLE	64
TYPE	Type Auto: automatic backup MANUAL: manual backup FR: New field added for JARs from 2019-12-05 onwards BI: new field added for JAR packages generated at and after 2020-01-15	VARCHAR	255
BACKUPENDTIME	Backup End Time FR: Version 10.0.11 and later, new field added BI: Version 5.1.8 and later, new field added	TIMESTAMP	26
STATUS	Backup Status 0: None 1: Success 2: Failure FR: Version 10.0.11 and later, new field added BI: Version 5.1.8 and later, new field added	INTEGER	32
DETAIL	Details (Error Log) FR: Version 10.0.11 and later, new field added BI: Version 5.1.8 and later, new field added	VARCHAR	65536

5.2 FINE_BACKUP_EXCLUDE_ENTITY Backup Exclusion Table

Field Name

Description

Data Type

Length

Some functional configuration items are not included in backup and restore, hence this table is skipped during backup execution.

The id and value have no specific meaning; the stored information depends on the functionality.

VARCHAR

255

VALUE

VARCHAR

255

6) Task Schedule

6.1 FINE_SCHEDULE_TASK Scheduled Task Table

Field Name	Description	Data Type	Length
ID	Primary key Associated table field fine_schedule_task_param>taskId fine_schedule_record>taskId	VARCHAR	255
BACKUPFILEPATH	Backup file path Reserved field, unused	VARCHAR	1000
CREATOR	Task Creator Associated table field fine_user>userName fine_schedule_record>creator	VARCHAR	255
EDITABLE	Whether the task is editable true: editable false: not editable Reserved field, unused	BOOLEAN	0
FILECLEARCOUNT	Attachment cleanup count -1: Do not clean 0: Clean immediately after task ends 1: Keep once Other positive integers: Retain times	INTEGER	32
NEXTFIRETIME	Next execution time yyyy-MM-dd HH:mm:ss	TIMESTAMP	26
OUTPUTSTR	Combined string of task attachment processing types, used for conditional query filtering File processing methods, separated by commas: 1: Email notification 2: FTP upload attachment 3: Platform notification 5: SMS notification 6: Mount platform 7: Custom attachment processing 8: Print file 9: Customer notification 10: SFTP upload	VARCHAR	1000
PREFIRETIME	Last execution time yyyy-MM-dd HH:mm:ss	TIMESTAMP	26
REPEATTIME	Time interval for restarting after task execution fails	INTEGER	32
REPEATTIMES	Number of retries after task execution fails	INTEGER	32
SENDBACKUPFILE	Whether to send backup files true: send false: not send Reserved field, unused	BOOLEAN	0
SHOWTYPE	Display type 0: Pagination preview 1: Data entry preview 2: Data analysis preview 3: preview on PC 4: New data entry	INTEGER	32
TASKCONDITION	Task Status JSON format, including type and description. type： 0: Always execute 1: Formula judgment 2: Custom Class Judgment description: Specific content (specific formula or class name)	VARCHAR	255
TASKDESCRIPTION	Task description Reserved field, unused	VARCHAR	1000
TASKNAME	Task Name	VARCHAR	255
TASKPARAMETER	Task Parameter In JSON format, includes inputStyle parameter input method, name parameter name, type parameter type, value parameter value inputStyle input method (optional) 0: Default 1: Dataset type parameter type String: String Integer Double: Double Date: Date Boolean: Boolean TableColumn: Dataset Column value parameter value If the parameter input method is default, then value is a string If the parameter input method is dataset, it includes value dataset name and colname dataset field value	VARCHAR	65536
TASKSTATE	Task Status 0: Start 1: Pause 2: Completed May not correspond to the frontend display status; requires calculation before displaying on the frontend	INTEGER	32
TASKTYPE	Task Type 0. No Schedule Object 1: Report Template 2: BI Template 3: Multiselected Report Template	INTEGER	32
TEMPLATEPATH	Template Path	VARCHAR	1000
TRIGGERGROUP	Trigger Group In JSON format, contains multiple triggers, including trigger type, time, etc. triggerType trigger type: 1: Only Execute Once 2: Fixed Interval 3: Detailed Frequency Setting 4: Expression Setting start time yyyy-MM-dd HH:mm:ss startType start type: 1: Execute immediately 2: Select start time endType end type: 1: End immediately after execution 2: No end date 3: Select end time 4: Additional executions recurrenceInterval Simple recurrence execution interval (optional) recurrenceIntervalUnit Time unit for simple recurrence execution interval (optional) 1: Minute 2: Hour 3: Day 4: Week repeatCount Additional execution count (optional): Integer hours Detailed frequency execution hours (optional): Integer minutes Detailed frequency execution minutes (optional): Integer dayType Detailed frequency execution day (optional): 1: Daily 2: Weekly 3: Monthly monthDays When execution day is monthly, select specific days of the month (optional): Integer Array weekDays When execution day is weekly, select specific days of the week (optional): Integer Array months Which months to execute for detailed frequency (optional): Integer Array	VARCHAR	65536
USERGROUP	User group JSON format: customRole Role list: Array of role IDs customRoleStr Role list string: For frontend display departmentAndPost Department list: Array of department IDs departmentStr Department list string: For frontend display platformUser User list (optional): Array, formatted as "Name(Username)" platformUserStr User list string (optional): For frontend display userType User type: 1 - Platform user, 2 - Custom user columnIndex Custom user - dataset column index (optional) columnIndexStr Custom user - dataset column name (optional) tableDataName Custom user - dataset name (optional)	VARCHAR	65536
SCHEDULEOUTPUT	Task push Associated table field fine_schedule_output>id	VARCHAR	255
CONDITIONPARAMETER	Custom class parameters for execution conditions JSON format: name Parameter name value Parameter value FR: new field added for JAR packages generated at and after 2020-06-08 BI: new field added for JAR packages generated at and after 2020-08-04	VARCHAR	1000

6.2 FINE_SCHEDULE_TASK_PARAM Scheduled task parameter values

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
PARAM	Parameter List JSON format: parameter name: parameter value	VARCHAR	65536
TASKNAME	Task Name	VARCHAR	255
TASKID	Task ID Associated table field fine_schedule_task>id	VARCHAR	255

6.3 FINE_SCHEDULE_TASK_EXTEND Scheduled task extended attributes

Field Name	Description	Data Type	Length
ID	Record ID	VARCHAR	255
TASKID	Scheduled task ID	VARCHAR	255
TASKPARAMETERMAP	Parameters for scheduled task templates	VARCHAR	65536
TEMPLATEPATHS	Templates for scheduled tasks	VARCHAR	4000

6.4 FINE_SCHEDULE_TASK_LOG Scheduled task tree monitoring logs

Field Name	Description	Data Type	Length
ID	Record ID	VARCHAR	255
LOGTIME	Log time	BIGINT	64
LOGTYPE	Log type 0: Failed 1: Successful 2: skip	INTEGER	32
TASKID	Scheduled task ID	VARCHAR	255
TASKLOG	Scheduled task logs	VARCHAR	16777216
TASKNAME	Scheduled task name	VARCHAR	255

6.5 FINE_SCHEDULE_RECORD Scheduled task execution log

Note: For projects with JAR packages before 2019-05-20, the fine_schedule_record table is used to store scheduled task execution logs.

For projects with JAR packages on or after 2019-05-20, the fine_schedule_record table in the LogDB database is used to store scheduled task execution logs. Please refer to: Platform Logs LogDB Database.

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
CREATOR	Creator	VARCHAR	255
DETAILMESSAGE	Details	VARCHAR	65536
FILEPATH	Generate attachment path Reserved field, unused	VARCHAR	1000
LOGMESSAGE	Log information	VARCHAR	255
LOGTIME	Task execution time Log print time	TIMESTAMP	26
LOGTYPE	Log type 0: Failed 1: Successful 2: skip	INTEGER	32
NEXTFIRETIME	Next recording time Reserved field, unused	TIMESTAMP	26
RUNTYPE	Attachment processing type 0: generated by snapshot 1: sent by email 2: FTP Upload 3: Platform Message Push 4: file print 5: sent by SMS 6: Mount Platform 7: Custom Class Processing 8: regularly filled 9: notified by client 10: SFTP Upload -1: Attachment Send (Default)	INTEGER	32
TASKNAME	Task Name	VARCHAR	255
TASKID	Task ID Associated table field fine_schedule_task>id	VARCHAR	255

6.6 FINE_SCHEDULE_OUTPUT Exports in Scheduled Tasks

Field Name	Description	Data Type	Length
ID	Primary key Associated table field fine_schedule_task>scheduleOutput fine_base_output>outputId	VARCHAR	255
BASENAME	Generate attachment name	VARCHAR	65536
CREATEATTACHBYUSERNAME	Whether to generate different attachments for different users 1: Yes 0: No	BOOLEAN	0
FORMATS	Export attachment type JSON format: formatNum File processing method: 0: Output CPR 1: Output new version EXCEL 2: Output PDF 4: Output WORD 8: Output old version EXCEL 16: Output PNG 32: Output FRR	VARCHAR	255
BASEMAMEMAP	Attachment name for a single template in scheduled tasks	VARCHAR	65536
FORMATSMAP	Export format for attachments of a single template in scheduled tasks	VARCHAR	65536

6.7 FINE_BASE_OUTPUT Task attachment processing main table

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
ACTIONNAME	Attachment processing class type	VARCHAR	255
EXECUTEBYUSER	Whether to execute separately for different users 1: Yes 0: No	BOOLEAN	/
RESULTURL	Result URL	VARCHAR	1000
RUNTYPE	Attachment processing type 0: generated by snapshot 1: sent by email 2: FTP Upload 3: Platform Message Push 4: file print 5: sent by SMS 6: Mount Platform 7: Custom Class Processing 8: regularly filled 9: notified by client 10: SFTP Upload -1: Attachment Sending (Default)	INTEGER	32
OUTPUTID	Export ID Associated table field fine_schedule_output>id	VARCHAR	255

6.8 FINE_OUTPUT_CLASS Custom Class Processing

Field Name

Description

Data Type

Length

CLASSNAME

Custom Class Name

VARCHAR

255

Primary key

Associated table field

fine_base_output>id

VARCHAR

255

6.9 FINE_OUTPUT_CLIENT_NOTICE Customer Notification Table

Field Name	Description	Data Type	Length
ADDRESSEE	Receiver	VARCHAR	65536
CONTENT	Content	VARCHAR	65536
CUSTOMIZELINK	Custom Link	VARCHAR	65536
LINKOPENTYPE	Link Type 1: Times Result Link 2: Custom Link	INTEGER	32
MEDIAID	Image ID for Rich Text Messages	VARCHAR	255
SUBJECT	Subject	VARCHAR	65536
TERMINAL	Push Terminal Currently fixed as 1, representing app notification	INTEGER	32
TYPE	Message Type 1: Link message 2: Graphic message 3: File message	INTEGER	32
ID	Primary key Associated table field fine_base_output>id	VARCHAR	255

6.10 FINE_OUTPUT_EMAIL Email push table

Field Name	Description	Data Type	Length
ADDLINK	Result link	BOOLEAN	0
BCCADDRESS	BCC	VARCHAR	65536
BODYCONTENT	Content	VARCHAR	65536
CCADDRESS	CC	VARCHAR	65536
PREVIEWATTACH	Body preview	Boolean	0
SUBJECT	Subject	VARCHAR	65536
USEATTACH	Use Attachment	Boolean	0
ID	Primary key Associated table field fine_base_output>id	VARCHAR	255
CUSTOMADDRESS	Custom email recipient	VARCHAR	1000
CUSTOMBCCADDRESS	Custom email BCC	VARCHAR	1000
CUSTOMCCADDRESS	Custom email CC	VARCHAR	1000
PREVIEWWIDGET	Whether to check "Preview component content in body" FR: Added field for version 10.0.13 and later BI: Added field for version 5.1.10 and later	Boolean	0
ADDLINKLIST	Result link for a single template in scheduled tasks	VARCHAR	65536
EMAILACCOUNTCONFIGID	Sender ID	VARCHAR	255
REVIEWATTACHLIST	Preview content of a single template in scheduled tasks	VARCHAR	65536
USEATTACHLIST	Generated attachments for a single template in scheduled tasks	VARCHAR	65536

6.11 FINE_OUTPUT_FTP FTP upload table

Field Name	Description	Data Type	Length
PASSWORD	Password	VARCHAR	255
PORT	Port number	VARCHAR	255
SAVEPATH	Upload Path	VARCHAR	255
SERVERADDRESS	Server Address	VARCHAR	255
USERNAME	Username	VARCHAR	255
ID	Primary key Associated table field fine_base_output>id	VARCHAR	255
FTPMODE	FTP Mode passive: Passive mode active: Active mode	VARCHAR	255

6.12 FINE_OUTPUT_MOUNT Scheduled task mount directory

Field Name	Description	Data Type	Length
DESCRIPTION	Description	VARCHAR	65536
FOLDERENTRYID	Mounted Folder ID	VARCHAR	255
FOLDERENTRYNAME	Mounted Folder Name	VARCHAR	255
FOLDERENTRYSTR	Mounting Directories	VARCHAR	255
ID	Primary key Associated table field fine_base_output>id	VARCHAR	255

6.13 FINE_OUTPUT_PLATFORM_MSG Platform System Message

Field Name	Description	Data Type	Length
CONTENT	Content	VARCHAR	65536
LINKOPENTYPE	Link Type 1: Times Result Link 2: Custom Link	INTEGER	32
SUBJECT	Subject	VARCHAR	65536
ID	Primary key Associated table field fine_base_output>id	VARCHAR	255

6.14 FINE_OUTPUT_PRINT Print Processing

Field Name

Description

Data Type

Length

PRINTERNAME

Printer Name

VARCHAR

255

Primary key

Associated table field

fine_base_output>id

VARCHAR

255

6.15 FINE_OUTPUT_SFTP SFTP Upload Table

Field Name	Description	Data Type	Length
ID	Primary key Associated table field fine_base_output>id	VARCHAR	255
PASSWORD	Password	VARCHAR	255
PORT	Port number	VARCHAR	255
PRIVATEKEY	Private Key	VARCHAR	255
SAVEPATH	Upload Path	VARCHAR	255
SERVERADDRESS	Server Address	VARCHAR	255
USERNAME	Username	VARCHAR	255

6.16 FINE_OUTPUT_SMS SMS Sending

Field Name	Description	Data Type	Length
TEMPLATEID	Template ID	INTEGER	32
ID	Primary key Associated table field fine_base_output>id	VARCHAR	255
SMSPARAM	SMS parameters, in JSON format, including: id: parameter IDname: parameter name value: parameter value type: Type of the parameter Types include: String: String Integer Double: Double Date Boolean: Boolean Formula: formula FR: New field added for JARs from 2019-12-05 onwards BI: new field added for JAR packages generated at and after 2020-01-15	VARCHAR	255

6.17 FINE_USAGE_DATA Scheduled Task Reach Record Table

Field Name	Description	Data Type	Length
ID	Record ID	VARCHAR	255
DATA	Record data	VARCHAR	1000
DATATYPE	Record data type	INTEGER	32
SUBTYPE	Record data subtype	INTEGER	32
TAG	Record data name	VARCHAR	255

7. Messages

7.1 FINE_BASE_MESSAGE Basic Message Table

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
CREATETIME	Message creation time	TIMESTAMP	26
DATETIME	Message time	TIMESTAMP	26
MESSAGE	Message Content	VARCHAR	65536
READ	Read or not 1: Yes 0: No	Boolean	/
TOASTED	Whether a toast notification has been shown 1: Yes 0: No	Boolean	/
type	Message Type 0: System message 1: Report message 2: Template message 3: Mobile message -1: Unknown message	INTEGER	32
URL	URL	VARCHAR	1000
URLTYPE	URL type 0: None 1: Internal link type, e.g. /report/entry/{id} 2: External link type, e.g. www.fanruan.com 3: Platform module route, redirecting to a specific Tab page in system management 4: URL to open multiple templates within the platform	INTEGER	32
USERID	User ID Associated table field fine_user>id	VARCHAR	255
USERNAME	Username Associated table field fine_user>userName	VARCHAR	255

7.2 FINE_PROCESS_MESSAGE Push Message Table

Field Name	Description	Data Type	Length
ALLTASKID	All task IDs	VARCHAR	255
DEADLINE	End time	timestamp	26
PROCESSED	Is completed 1: Completed 0: Not completed	Boolean	0
taskId	Report task ID	VARCHAR	255
ID	Primary key Associated table field fine_base_message>id	VARCHAR	255

7.3 FINE_SYSTEM_MESSAGE System message table

Field Name	Description	Data Type	Length
TERMINAL	Push Terminal Currently fixed as 1, representing PC-side message notifications	BIGINT	64
TITLE	Subject	VARCHAR	255
ID	Primary key Associated table field fine_base_message>id	VARCHAR	255

8. Reporting

Note: JARs after 2018-12-27 added reporting-related tables.

8.1 FINE_WORKFLOW Reporting process table

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
createTime	Creation time of the dashboard	timestamp	26
CREATORID	Creator ID Associated table field fine_workflow_task>creatorId fine_workflow_stash_data>userId fine_workflow_log>operatorname	VARCHAR	255
DESCRIPTION	Description	VARCHAR	65536
name	Process Name	VARCHAR	255
NODESID	Node ID Associated table field fine_workflow_node>id	VARCHAR	65536

8.2 FINE_WORKFLOW_TASK Process Task Table in Reporting

Field Name	Description	Data Type	Length
ID	Primary key Associated table field fine_workflow_task_impl>taskId	VARCHAR	255
createTime	Creation time of the dashboard	timestamp	26
CREATORID	Creator ID Associated table field fine_user>id fine_workflow>creatorId	VARCHAR	255
CREATORNAME	Creator Name Associated table field fine_user>username	VARCHAR	255
DEADLINEDATE	End Time	INTEGER	32
DEADLINETYPE	Deadline Type	VARCHAR	255
ISSUECONTROL	Timed Issuance	VARCHAR	65536
ISSUEOVER	Whether Issuance is Completed 1: Yes 0: No	Boolean	0
LEAPFROGBACK	Over-level rollback	Boolean	0
name	Task Name	VARCHAR	255
parentID	Parent Task ID Associated table field fine_workflow_task_impl>parentId	VARCHAR	255
PROCESSID	Process ID Associated table field fine_workflow_task_impl>processId	VARCHAR	255
REMINDCONTROL	Reminding Method	VARCHAR	65536
TASKNAMECALCULATEONCE	Whether to check "Calculate only once when the task is initiated" when adding a task 1: Checked 2: Unchecked	Boolean	0

8.3 FINE_WORKFLOW_TASK_IMPL Task Details Table

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
ALERTED	Whether to alert 1: Yes 0: No	Boolean	0
COMPLETESTATE	Current task operator and completion status, 1: Completed 0: Not completed Example: {"demo/authority/Product Sales Query.cpt":{"sunlin":0}} Note: If the reporting user identity is a role, the operator does not display the username but shows the role type id_role id	VARCHAR	65536
createTime	Creation time (time of issuance)	timestamp	26
CURRENTNODEIDX	Current node ID	INTEGER	32
DEADLINE	End Time	timestamp	26
FRTASKID	Source Task ID	VARCHAR	255
name	Task name	VARCHAR	255
NEEDALLCOMPLETE	Whether all need to be completed 1: Yes 0: No	Boolean	0
NODEROUTE	Node traversal path JSON	VARCHAR	65536
NOTE	Remark	VARCHAR	16777216
OPERATORJSON	Which node on the Node is multi-user	VARCHAR	65536
OPERATOROFFSET	Which user in the multi-user node	VARCHAR	65536
OPERATOROFFSETNAME	Name of the user in the multi-user node	VARCHAR	65536
parentID	Parent task ID Associated table field fine_workflow_task>parentId	VARCHAR	255
PROCESSID	Process ID Associated table field fine_workflow_task>processId	VARCHAR	255
REPORTOFFSET	Which template	INTEGER	32
SENDTIME	Sending time	timestamp	26
SENDER	Sender	VARCHAR	255
SENDERID	Sender ID	VARCHAR	255
SONTASKID	Subtask ID [{nodeIdx:0, userId:1, taskId:1}]	VARCHAR	255
state	Task Status -1: Initial 0: Waiting to report 1: Waiting for review 2: Approved 3: Rejected 4: Closed 5: Timeout	INTEGER	32
taskId	Source Task ID Associated table field fine_workflow_task>Id	VARCHAR	255
TASKBACKTARGET	Rollback information	VARCHAR	255

8.4 FINE_WORKFLOW_NODE Workflow Node Reporting Table

Field Name	Description	Data Type	Length
ID	Primary key Associated table field fine_workflow>nodesId	VARCHAR	255
ALERTCONTROL	Alert Details	VARCHAR	1000
AUTHORITY	Permission	VARCHAR	255
DESCRIPTION	Description	VARCHAR	1000
name	Node name	VARCHAR	255
NEEDALLCOMPLETE	Whether to proceed only after all tasks are completed 1: Yes 0: No	Boolean	0
NEEDOFFLINEREPORT	Whether offline data entry is required 1: Yes 0: No	Boolean	0
PROCESSID	Process ID	VARCHAR	255
REPORTCONTROL	Reporting Details	VARCHAR	1000

8.5 FINE_WORKFLOW_STASH_DATA Reporting Process Data Staging Table

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
DATA	Data	VARCHAR	16777216
REPORTPATH	Report Path	VARCHAR	65536
USERID	User ID Associated table field fine_workflow>creatorId	VARCHAR	255
taskId	Task ID	VARCHAR	255

8.6 FINE_WORKFLOW_LOG Reporting Process Operation Log

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
datetime	Date	timestamp	26
message	Message	VARCHAR	65536
OPERATORNAME	Operator Name Associated table field fine_workflow>creatorId	VARCHAR	255
PROCESSNAME	Process Name	VARCHAR	255
taskName	Task Name	VARCHAR	255

9. System Configuration

9.1 FINE_CONF_CLASSNAME Interface Configuration Type Table

Field Name	Description	Data Type	Length
ID	Current field position in the configuration	VARCHAR	255
CLASSNAME	Field type of the corresponding configuration value in the configuration	VARCHAR	255

9.2 FINE_CONF_ENTITY Configuration Class Data Table

Field Name	Description	Data Type	Length
ID	Location of data in the configuration	VARCHAR	255
VALUE	Data value	VARCHAR	65536

Note: Most configuration content stored in the database is in this table. For example: id = BackupConfig.backupMemory, value = 1024 means assigning a value of 1024 to the backupMemory configuration in BackupConfig, indicating that automatic backups can occupy up to 1024MB.

Common platform configuration items and front-end configuration pages not provided are mostly stored in the fine_conf_entity table. For details, see: Configuration Information Storage Table.

9.3 FINE_CONF_XMLENTITY XML-Stored Configuration Mapping Table

Field Name	Description	Data Type	Length
ID	Location of data in the configuration	VARCHAR	255
VALUE	XML text value of this field	BLOB	67108864

9.4 FINE_INTERNATIONAL Multilingual Support Internationalization Data Table

Note: This table appears in JAR packages from versions dated 2020-02-28 onwards.

Field Name	Description	Data Type	Length	Remark
ID	Primary key	VARCHAR	255	/
DESCRIPTION	Description	VARCHAR	1000	/
I18NKEY	Internationalization key	VARCHAR	255	/
LANGUAGE	Internationalization language zh_CN: Simplified Chinese zh_TW: Traditional Chinese en_US: English ja_JP: Japanese ko_KR: Korean	VARCHAR	255	/
I18NVALUE	Internationalization value	VARCHAR	1000	Chinese characters need to be converted to Unicode encoding using an online conversion tool before being written.

9.5 FINE_LABEL Label Table

Field Name	Description	Data Type	Length
ID	Record ID	VARCHAR	255
LABELNAME	Label Name	VARCHAR	255
RELATEDTYPE	Label Association Type	INTEGER	32

9.6 FINE_LABEL_INDEX Label Relationship Table

Field Name	Description	Data Type	Length
ID	Record ID	VARCHAR	255
LABELID	Label ID	VARCHAR	255
RELATEDID	Label Association ID	VARCHAR	255

9.7 FINE_OPS_EXCEED_TEMPLATES Exceed Limit Templates

Note: This table is added in FineReport version 11.0.5 and later / FineBI version 5.1.23 and later.

This table records templates that exceed normal time limits, used for operation and maintenance platform analysis.

Field Name	Description	Data Type	Length
ID	id	VARCHAR	255
TEMPLATENAME	Template Name	VARCHAR	255
TEMPLATETYPE	Exceed Limit Type	VARCHAR	255

9.8 FINE_OPS_CRASH_DETAIL Crash Record Table

Note: This table is added in FineReport version 11.0.5 and later / FineBI version 5.1.23 and later.

Field Name	Description	Data Type	Length
ID	id	VARCHAR	255
DOWNTIME	Crash Time	BIGINT	64
Node	instance	VARCHAR	255
REASONDETAIL	Detailed Reason	VARCHAR	255
SOLUTION	Solution	VARCHAR	255

9.9 FINE_NET_CHECK_RECORD Network Check Record Table

Note: This table is added in FineReport version 11.0.7 and later / FineBI version 5.1.25 and later.

Field Name	Description	Data Type	Length
ID	id	VARCHAR	255
config		VARCHAR	1000
HANDLERNODE		VARCHAR	255
ITEM		VARCHAR	255
RESULT		VARCHAR	16777216
TARGET		VARCHAR	255
TIME		BIGINT	64
type		VARCHAR	255

10. Swift module (not allowed to modify)

10.1 FINE_SWIFT_COL_IDX_CONF Column index configuration table

Field Name	Description	Data Type	Length
COLUMNNAME	Field Name	VARCHAR	255
TABLEKEY	Data table SourceKey	VARCHAR	255
REQUIREGLOBALDICT	Whether to generate global index 1: Yes 0: No	Boolean	0
REQUIREINDEX	Whether to generate index 1: Yes 0: No	Boolean	0

10.2 FINE_SWIFT_CONFIG_ENTITY Swift internal configuration table

Field Name	Description	Data Type	Length
CONFIGKEY	Location of the configuration	VARCHAR	255
CONFIGVALUE	Configuration Value	VARCHAR	65536

10.3 FINE_SWIFT_METADATA Data table metadata storage table

Field Name	Description	Data Type	Length
ID	SourceKey calculated from the data table	VARCHAR	255
FIELDS	Field	VARCHAR	65536
REMARK	Translated name	VARCHAR	255
SCHEMANAME	Schema of the database table	VARCHAR	255
SWIFTSCHEMA	Data file storage location CUBE / LOG	VARCHAR	255
tableName	Table name	VARCHAR	255

10.4 FINE_SWIFT_SEG_LOCATION Swift Segment distribution information

Field Name	Description	Data Type	Length
CLUSTERID	Cluster ID	VARCHAR	255
SEGMENTID	Generated Segment ID	VARCHAR	255
SOURCEKEY	Data table SourceKey, indicating which table the Segment belongs to	VARCHAR	255

10.5 FINE_SWIFT_SEGMENTS Swift Segment details

Field Name	Description	Data Type	Length
ID	Generated Segment ID	VARCHAR	255
SEGMENTORDER	Segment sequence number	INTEGER	32
SEGMENTOWNER	Data table SourceKey, indicating which table the Segment belongs to	VARCHAR	255
SEGMENTURI	Relative URL of the data file	VARCHAR	65536
STORETYPE	Data storage type MEMORY: Memory storage, exists only in memory and is lost upon shutdown NIO: Writes memory content to files to solve the problem of data loss upon shutdown FINE_IO: An IO framework implemented by fr itself. When NIO files are full, data is written to FINE_IO	VARCHAR	255
SWIFTSCHEMA	Data file storage directory CUBE / LOG	VARCHAR	255

10.6 FINE_SWIFT_SERVICE_INFO Save Swift service information

Field Name	Description	Data Type	Length
ID	Service ID	VARCHAR	255
CLUSTER_ID	Cluster ID	VARCHAR	255
IS_SINGLETON	Whether to start only one instance 1: Yes 0: No	Boolean	0
SERVICE	Service Type cluster_master_service: Records the master node ID for synchronization across all nodes. Others: Services started on each node (such as query, import, history, real-time services, etc.)	VARCHAR	255
SERVICE_INFO	Additional service information	VARCHAR	255

10.7 FINE_SWIFT_TAB_IDX_CONF Table index configuration

Field Name	Description	Data Type	Length
TABLEKEY	Table SourceKey	VARCHAR	255
ALLOTRULE	Partitioning logic	VARCHAR	255

10.8 FINE_SWIFT_TABLE_PATH Cube intermediate directory configuration management

Field Name	Description	Data Type	Length
CLUSTERID	Cluster ID Standalone mode is LOCAL	VARCHAR	255
TABLEKEY	Table SourceKey	VARCHAR	255
LASTPATH	Temporary directory used last time	INTEGER	32
TABLEPATH	Currently used intermediate directory	INTEGER	32
TMPDIR	Intermediate directory used when generating Cube	INTEGER	32

10.9 FINE_SWIFT_CLUSTER_SIZE

This table has been deprecated.

Field Name	Data Type	Length
ID	VARCHAR	255
PRIMARY_CLUSTER_SIZE	INTEGER	32
DESCRIPTION	VARCHAR	255

10.10 FINE_SWIFT_DAYS_RECORD Daily access statistics cache table

Note: This table was deprecated in July 2022, and its content is now stored in the fine_pretreat_job_result table of logdb.

Every day at midnight, Swift has a scheduled task to query the "daily visits, daily active templates, and daily active users" from the previous day's access statistics and record them in this table as a cache.

The "TASK" in the field names of this table refers to this scheduled task.

Field Name	Description	Data Type	Length
TASK_ID	Task ID	VARCHAR	255
TASK_RESULT	Query results: including daily active users, daily active templates, and daily visits	VARCHAR	4096
TASK_CONDITION	Query conditions: task type + query time range	VARCHAR	1024
TASK_TYPE	Task Type	VARCHAR	255

10.11 FINE_SWIFT_FILEKEY Time index table for swift data blocks (seg)

Field Name	Description	Data Type	Length
SEGMENTID	The ID of the swift data block, corresponding to the ID in fine_swift_segments	VARCHAR	255
TIMEKEY	File index of the data block. For versions after April 11, 2021, the cubes directory has been changed. A folder is generated daily to store the data of that day, named with the date, e.g., 20210701	VARCHAR	255

10.12 FINE_SWIFT_RESTORE_RESULT Log restoration temporary record

This table is a temporary status table, deleted immediately after writing. Under normal circumstances, the content of this table is empty.

Field Name	Description	Data Type	Length
UUID	Record ID	VARCHAR	255
CLUSTERID	Cluster ID, standalone is LOCAL	VARCHAR	255
endTime	Right boundary of log restoration interval	BIGINT	64
errorCode	Error code	INTEGER	32
errorMsg	Error information	VARCHAR	255
EXCEPTION	Exception Information	VARCHAR	65536
starttime	Left boundary of log restoration interval	BIGINT	64
SUCCESS	Log restoration process result true: success false: failure	Boolean	[NULL]

11. Quartz module (not allowed to modify)

11.1 QRTZ_BLOB_TRIGGERS Triggers stored as Blob type

Stored as Blob type, used when Quartz users create their own custom Trigger types using JDBC, and JobStore does not know how to store the instance.

Field Name	Description	Data Type	Length
SCHED_NAME	Scheduler name	VARCHAR	255
TRIGGER_GROUP	Foreign key to trigger_group in qrtz_triggers table	VARCHAR	255
TRIGGER_NAME	Foreign key to trigger_name in qrtz_triggers table	VARCHAR	255
BLOB_DATA	A blob field storing persistent Trigger object	VARBINARY	16777216

11.2 QRTZ_CALENDARS Calendar information storage table

Stores calendar information as Blob type. Quartz can configure a calendar to specify a time range.

Field Name	Description	Data Type	Length
CALENDAR_NAME	Calendar name	VARCHAR	255
SCHED_NAME	Scheduler name	VARCHAR	255
CALENDAR	A blob field for storing persistent calendar objects.	VARBINARY	4000

11.3 QRTZ_CRON_TRIGGERS stores Cron-type triggers.

A table for storing the cron expressions of triggers.

Field Name	Description	Data Type	Length
SCHED_NAME	Scheduler name	VARCHAR	255
TRIGGER_GROUP	Foreign key to the trigger_group in the qrtz_triggers table	VARCHAR	255
TRIGGER_NAME	Foreign key to the trigger_name in the qrtz_triggers table	VARCHAR	255
CRON_EXPRESSION	Cron Expression	VARCHAR	255
TIME_ZONE_ID	Time zone	VARCHAR	255

11.4 QRTZ_FIRED_TRIGGERS stores fired triggers.

Stores state information related to fired Triggers and execution information of associated Jobs.

Field Name	Description	Data Type	Length
ENTRY_ID	Scheduler instance ID	VARCHAR	255
SCHED_NAME	Scheduler name	VARCHAR	255
FIRED_TIME	Trigger Time	NUMERIC	19
INSTANCE_NAME	Scheduler instance name	VARCHAR	255
IS_NONCONCURRENT	Whether concurrent 1: Yes 0: No	Boolean	0
JOB_GROUP	The name of the job group in the cluster	VARCHAR	255
JOB_NAME	The name of the job in the cluster	VARCHAR	255
PRIORITY	Precedence	INTEGER	32
REQUESTS_RECOVERY	Whether to accept recovery execution, default is 0 1: Yes 0: No	Boolean	0
SCHED_TIME	The time specified by the scheduler	NUMERIC	19
state	State	VARCHAR	255
TRIGGER_GROUP	Foreign key to the trigger_group in the qrtz_triggers table	VARCHAR	255
TRIGGER_NAME	Foreign key to the trigger_name in the qrtz_triggers table	VARCHAR	255

11.5 QRTZ_JOB_DETAILS stores a JobDetail information

Stores detailed information for each configured jobDetail.

Field Name	Description	Data Type	Length
JOB_GROUP	The name of the job group in the cluster	VARCHAR	255
JOB_NAME	The name of the job in the cluster	VARCHAR	255
SCHED_NAME	Scheduler name	VARCHAR	255
DESCRIPTION	The fully qualified name of the notejob implementation class in the cluster. Quartz uses this path to locate the job class in the classpath.	VARCHAR	255
IS_DURABLE	Whether to persist 1: Yes, Quartz will persist the job to the database. 0: No	Boolean	0
IS_NONCONCURRENT	Whether to execute concurrently 1: Yes 0: No	Boolean	0
IS_UPDATE_DATA	Whether to update data 1: Yes 0: No	Boolean	0
JOB_CLASS_NAME	The fully qualified name of the notejob implementation class in the cluster. Quartz uses this path to locate the job class in the classpath.	VARCHAR	255
JOB_DATA	A blob field that stores the persisted job object.	VARBINARY	16777216
REQUESTS_RECOVERY	Whether to accept recovery execution, default is 0. 1: Yes 0: No	Boolean	0
CREATOP	/	VARCHAR	255

11.6 QRTZ_LOCKS stores pessimistic lock information.

Stores the pessimistic lock information of the stored program (if pessimistic locking is used).

Field Name	Description	Data Type	Length
LOCK_NAME	Pessimistic Lock Name	VARCHAR	255
SCHED_NAME	Scheduler Name	VARCHAR	255

11.7 QRTZ_PAUSED_TRIGGER_GRPS

Stores information about paused trigger groups.

Field Name	Description	Data Type	Length
SCHED_NAME	Scheduler Name	VARCHAR	255
TRIGGER_GROUP	Foreign key to the trigger_group in the qrtz_triggers table	VARCHAR	255

11.8 QRTZ_SCHEDULER_STATE

Stores instance information of nodes in the cluster. Quartz periodically reads this table to determine the current state of each instance in the cluster.

Field Name	Description	Data Type	Length
INSTANCE_NAME	The name configured in org.quartz.scheduler.instanceId in the configuration file will be written to this field	VARCHAR	255
SCHED_NAME	Scheduler Name	VARCHAR	255
CHECKIN_INTERVAL	Check-in interval time	NUMERIC	19
LAST_CHECKIN_TIME	Last check-in time	NUMERIC	19

11.9 QRTZ_SIMPLE_TRIGGERS Information about simple triggers

Stores simple triggers, including repeat count, interval, and the number of times already triggered.

Field Name	Description	Data Type	Length
SCHED_NAME	Scheduler name	VARCHAR	255
TRIGGER_GROUP	Trigger Group	VARCHAR	255
TRIGGER_NAME	Trigger Name	VARCHAR	255
REPEAT_COUNT	Repeat Count Statistics	NUMERIC	19
REPEAT_INTERVAL	Repeat Interval	NUMERIC	19
TIMES_TRIGGERED	Times Triggered	NUMERIC	19

11.10 QRTZ_SIMPROP_TRIGGERS

qrtz_simprop_triggers stores CalendarIntervalTrigger (similar to SimpleTrigger, specifies a task trigger that executes at a certain time interval starting from a specific time) and DailyTimeIntervalTrigger (specifies a task trigger that executes at a certain time interval within a specific time range each day)

Field Name	Description	Data Type	Length
SCHED_NAME	Scheduler name	VARCHAR	255
TRIGGER_GROUP	Foreign key to the trigger_group in the qrtz_triggers table	VARCHAR	255
TRIGGER_NAME	Foreign key to the trigger_name in the qrtz_triggers table	VARCHAR	255
BOOL_PROP_1	First parameter of the Boolean-type trigger	Boolean	0
BOOL_PROP_2	Second parameter of the Boolean-type trigger	Boolean	0
DEC_PROP_1	First parameter of the decimal-type trigger	NUMERIC	19
DEC_PROP_2	The second parameter of a decimal type trigger	NUMERIC	19
INT_PROP_1	The first parameter of an int type trigger	INTEGER	32
INT_PROP_2	The second parameter of an int type trigger	INTEGER	32
LONG_PROP_1	The first parameter of a long type trigger	NUMERIC	19
LONG_PROP_2	The second parameter of a long type trigger	NUMERIC	19
STR_PROP_1	The first parameter of a String type trigger	VARCHAR	255
STR_PROP_2	The second parameter of a String type trigger	VARCHAR	255
STR_PROP_3	The third parameter of a String type trigger	VARCHAR	255

11.11 QRTZ_TRIGGERS Basic Trigger Information

Saves the basic information of triggers.

Note: After setting the user synchronization dataset, locate the data with "JOB_NAME" as "syncUser" in the qrtz_triggers table to view the user update time.

Field Name	Description	Data Type	Length
SCHED_NAME	Scheduler name	VARCHAR	255
TRIGGER_GROUP	Trigger group name	VARCHAR	255
TRIGGER_NAME	Trigger name	VARCHAR	255
CALENDAR_NAME	Calendar name	VARCHAR	255
DESCRIPTION	Detailed description information	VARCHAR	255
END_TIME	End time	NUMERIC	19
JOB_DATA	A blob field that stores the persisted job object.	VARBINARY	16777216
JOB_GROUP	Foreign key for job_group in qrtz_job_details table	VARCHAR	255
JOB_NAME	Foreign key for job_name in qrtz_job_details table	VARCHAR	255
MISFIRE_INSTR	Strategy for misfire handling or compensation execution	INTEGER	32
NEXT_FIRE_TIME	Next trigger time	NUMERIC	19
PREV_FIRE_TIME	Previous trigger time	NUMERIC	19
PRIORITY	Precedence	INTEGER	32
START_TIME	Start time	NUMERIC	19
TRIGGER_STATE	Current trigger state Waiting PAUSED: Paused ACQUIRED: Normal execution BLOCKED: Blocked ERROR	VARCHAR	255
TRIGGER_TYPE	Type of trigger SIMPLE: Repeats execution after a specific time interval. For example, starts at 9 AM and executes once every hour. CRON: Based on calendar scheduling, such as executing every Tuesday at 2 AM.	VARCHAR	255
APPOINT_ID	Platform cluster node ID. Indicates on which node the trigger needs to run; if empty, it executes on all nodes.	VARCHAR	255

12. Mobile Terminal

12.1 FINE_MOBILE_DEVICE Mobile Device Table

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
CREATEDATE	Device addition date	timestamp	26
DEVICENAME	Device Name	VARCHAR	255
MACADDRESS	Device MAC address	VARCHAR	255
PASSED	Whether the device is authenticated 1: Yes 0: No	Boolean	0
UPDATEDATE	Device modification date	timestamp	26
USERNAME	Associated username	VARCHAR	255

12.2 FINE_MOBILE_PUSH_MESSAGE Mobile Push Message Table

Field Name	Description	Data Type	Length
GROUPID	Message recipient group ID	VARCHAR	255
MEDIAID	Image ID for Rich Text Messages	VARCHAR	255
MSGTYPE	Message Type 1: Regular text message 2: Graphic message 3: File message	INTEGER	32
TERMINAL	Push Terminal Currently fixed as 1, representing app notification	INTEGER	32
TITLE	Message Title	VARCHAR	255
ID	Primary key	VARCHAR	255

12.3 FINE_WEIXIN_USER_RELATION Platform and WeChat user mapping table under manual matching

Note: Data appears in this table after selecting [Manual Matching] in WeChat Management - User Matching Method and binding the relationship between platform users and WeChat users.

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
FSUSER	Platform username	VARCHAR	255
WEIXINUSER	WeChat user ID	VARCHAR	255

12.4 FINE_WEIXIN_OUTPUT Scheduled task information for WeChat push

Note: Data appears in this table only when "Customer Notification > WeChat Notification" is checked and saved in scheduled tasks.

Field Name	Description	Data Type	Length
AgentID	App ID	VARCHAR	255
CONTENT	Content of customer notification	VARCHAR	255
CUSTOMIZELINK	Content filled in custom link	VARCHAR	255
LINKOPENTYPE	Link type of customer notification 1: Scheduled task link 2: Custom Link	VARCHAR	255
MEDIAID	mediaId of files or images obtained by calling the upload interface	VARCHAR	255
SUBJECT	Title of customer notification	VARCHAR	255
TERMINAL	Fixed as 2, corresponding to WeChat notification	INTEGER	32
type	Message type for customer notification 1: Link message 2: Graphic message 3: File message	INTEGER	32
ID	Primary key	VARCHAR	255
ADDRESSEE	Additional customer for receiving messages, 1 represents group push	INTEGER	32
CHATGROUPS	String array storing group push IDs	VARCHAR	255

12.5 FINE_WEIXIN_AGENT Application information table in WeChat management

Note: Data appears in this table only when "Customer Notification > WeChat Notification" is checked and saved in the scheduled task.

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
AgentID	App ID	VARCHAR	255
AGENTNAME	App name	VARCHAR	255
CorpID	Enterprise CorpID	VARCHAR	255
secret	Application secret key	VARCHAR	255
timestamp	Timestamp	VARCHAR	255
type	Application Type 1: Application with management group secret key, considered legacy 2: Normal application 3: Application that failed to obtain token	INTEGER	32

12.6 FINE_WEIXIN_GROUP WeChat group information table in WeChat management

Note: Data appears in this table only when "Customer Notification > WeChat Group Notification" is checked and saved in the scheduled task.

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
AgentID	App ID	VARCHAR	255
GROUPID	Group chatid, used for push	VARCHAR	255
GROUPNAME	Group name	VARCHAR	255
timestamp	Timestamp	VARCHAR	255

12.7 FINE_DINGTALK_USER_RELATION Platform and DingTalk user correspondence table under manual matching

Note: Data appears in this table only when "Customer Notification > DingTalk Notification" is checked and saved in the scheduled task.

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
FSUSER	Platform username	VARCHAR	255
DINGTALKUSER	DingTalk user ID	VARCHAR	255

12.8 FINE_DINGTALK_OUTPUT Scheduled task information pushed by DingTalk

Note: Data appears in this table only when "Customer Notification > DingTalk Notification" is checked and saved in the scheduled task settings.

Field Name	Description	Data Type	Length
AgentID	App ID	VARCHAR	255
CONTENT	Content of customer notification	VARCHAR	255
CUSTOMIZELINK	Content filled in custom link	VARCHAR	255
LINKOPENTYPE	Link type of customer notification 1: Scheduled task link 2: Custom Link	VARCHAR	255
MEDIAID	Media ID of file or image obtained by calling the upload interface	VARCHAR	255
SUBJECT	Title of customer notification	VARCHAR	255
TERMINAL	Fixed as 4, corresponding to DingTalk notification	INTEGER	32
type	Message type of customer notification 1: Link message 2: Graphic message 3: File message	INTEGER	32
ID	Primary key	VARCHAR	255
ADDRESSEE	Additional customers receiving messages, where 1 represents group push	INTEGER	32
CHATGROUPS	String array storing group push IDs	VARCHAR	255

12.9 FINE_DINGTALK_AGENT Application information table in DingTalk management

Note: Data appears in this table only when "Customer Notification > DingTalk Notification" is checked and saved in the scheduled task.

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
AgentID	App ID	VARCHAR	255
AGENTNAME	App name	VARCHAR	255
AppKey	Application AppKey
CorpID	CorpID	VARCHAR	255
secret	It is the app secret.	VARCHAR	255
timestamp	Timestamp	VARCHAR	255
type	Application Type 1: Normal application 2: Application that failed to obtain token	INTEGER	32

12.10 FINE_DINGTALK_GROUP DingTalk group information table in DingTalk management

Note: Data appears in this table only when "Customer Notification > DingTalk Group Notification" is checked and saved in the scheduled task.

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
AgentID	App ID	VARCHAR	255
GROUPID	Group chatid for push notifications	VARCHAR	255
GROUPNAME	Group name	VARCHAR	255
timestamp	Timestamp	VARCHAR	255

12.11 FINE_FEISHU_USER_RELATION Correspondence table between platform and Feishu users under manual matching

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
FSUSER	Platform username	VARCHAR	255
FEISHUUSER	Lark user ID	VARCHAR	255

12.12 FINE_FEISHU_OUTPUT Scheduled task information for Feishu push notifications

Field Name	Description	Data Type	Length
AgentID	App ID	VARCHAR	255
CONTENT	Content of customer notification	VARCHAR	255
CUSTOMIZELINK	Content filled in for custom links	VARCHAR	255
LINKOPENTYPE	Link type for customer notification 1: Scheduled task link 2: Custom Link	VARCHAR	255
MEDIAID	mediaId of files or images obtained by calling the upload interface	VARCHAR	255
SUBJECT	Title of customer notification	VARCHAR	255
TERMINAL	Fixed as 4, corresponding to DingTalk notification	INTEGER	32
type	Message type of customer notification 1: Link message 2: Graphic message 3: File message	INTEGER	32
ID	Primary key	VARCHAR	255
ADDRESSEE	Additional customers receiving messages, 1 represents push group	INTEGER	32
CHATGROUPS	String array storing push group IDs	VARCHAR	255

12.13 FINE_FEISHU_AGENT Feishu management application information table

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
AgentID	App ID	VARCHAR	255
AGENTNAME	App name	VARCHAR	255
CorpID	Enterprise CorpID	VARCHAR	255
encrypted	Whether encrypted true: encrypted false: not encrypted	Boolean	0
secret	Application key	VARCHAR	255
timestamp	Timestamp	VARCHAR	255
type	Application Type 1: Applications with management group keys, belonging to legacy applications 2: Normal applications 3: Applications that failed to obtain tokens	INTEGER	32

12.14 FINE_FEISHU_GROUP Feishu group information table in Feishu management

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
AgentID	App ID	VARCHAR	255
GROUPID	Group chat ID, used for pushing	VARCHAR	255
GROUPNAME	Group name	VARCHAR	255
timestamp	Timestamp	VARCHAR	255

13. Reports

13.1 FINE_PARAM_TEMPLATE Template parameter combination

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
templateid	Template ID	VARCHAR	255
tpgroup	Parameter combination	VARCHAR	65536
USERNAME	Username	VARCHAR	255

13.2 FINE_PRINT_OFFSET Print offset

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
CPTNAME	Template Name	VARCHAR	50
instance	Customer IP address	VARCHAR	20
OFFSETX	Horizontal offset	VARCHAR	50
OFFSETY	Vertical offset	VARCHAR	50
SIGN	Offset options 0: No offset 1: Global configuration 2: Single template configuration	VARCHAR	10

13.3 FINE_PRINT_OFFSET_IP_RELATE Print offset IP relation table

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
CHILDIP	Associated customer IP Associated table field fine_print_offset>id	VARCHAR	20
MOTHERID	Corresponding ID field in the print offset table	VARCHAR	255

13.4 FINE_REMOTE_DESIGN_AUTH Remote design user table

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
path	Paths with remote design permissions	VARCHAR	1000
PATHTYPE	Path type 0: File 1: Folder	Boolean	0
USERID	User ID	VARCHAR	255
USERNAME	Username	VARCHAR	255
ROLETYPE	Role type 0: No role 1: Department Position Role 2: Custom Role 3: User Role	INTEGER	32

13.5 FINE_WRITE_STASH Temporary Storage Table for Data Entry

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
DATA	Temporary Data	VARCHAR	16777216
REPORTPATH	Template Path	VARCHAR	1000
USERNAME	Username	VARCHAR	255

13.6 FINE_PROCESS_EXPAND FineReport Submission Expansion Table

Expansion Attribute Table for Submission Process Type Permission Entities

Refers to the related attributes configured in the decision-making platform directory for the submission process, including name, path, description, type, display terminal, parameter settings, etc.

Field Name

Description

Data Type

Length

Primary key

VARCHAR

255

PROCESSTYPE

Submission Process Type

1: Submission Task Management

2: Submission Process Management

3: My Submission Tasks

INTEGER

13.7 FINE_REPORT_EXPAND FineReport Report Expansion

Expansion Attribute Table for Report Type Permission Entities, recording the parameter attributes configured when reports are mounted to the decision-making platform directory.

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
SHOWTYPE	0: Data entry 1: Pagination 2: Analysis 3: Table Preview 4: New data entry 5: PC Preview of FRM report	INTEGER	32
TRANSMITPARAMETERS	Custom Preview Parameters	VARCHAR	65536

13.8 FINE_EXCEL_SUBMIT_TASK Excel Batch Import Permission Entity Expansion Table

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
createTime	It displays the task creation time.	timestamp	26
DESCRIPTION	Description	VARCHAR	1000
name	Task Name	VARCHAR	255
REPORTPATH	Associated template path	VARCHAR	1000
SUBMITTIME	Submission time	timestamp	26

13.9 FINE_VCS Template Version Control Table

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
COMMITCODE	Used to roll back commits	VARCHAR	255
COMMITMSG	Git commit message	VARCHAR	255
fileName	Template Name	VARCHAR	255
TIME	Submission time	timestamp	26
USERNAME	Username	VARCHAR	255
VERSION	Version number	INTEGER	32

13.10 FINE_COMPONENT_HEALTH Component Health Record Table

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
CLUSTERNODEID	Node ID	VARCHAR	255
EXTRAINFO	Additional information No current use, reserved field	VARCHAR	65536
MODULE	Module	VARCHAR	255
STATUS	Status type 1: Available 2: Not enabled 3: Exception 4: Timeout 5: Unknown error	INTEGER	32
TIME	Submission time	timestamp	26

14. Open Platform Plugin

Note: All tables in this chapter are generated only when the Open Platform plugin is installed.

14.1 FR_OPEN_API API Information

Field Name	Description	Data Type	Length
ID	ID	VARCHAR	255
createTime	Created on:	timestamp	26
DESCRIPTION	Description	VARCHAR	255
EDITABLE	Editable 1: Editable 0: Not editable	INTEGER	32
ENABLE	Available 1: Available 0: Unavailable	INTEGER	32
name	Internationalization key for display name	VARCHAR	255
CLASS	Class path	VARCHAR	255
config	Configuration item (json)	VARCHAR	10000
TDEFAULT	Default parameters (json)	VARCHAR	255
INFO	Request path	VARCHAR	255
ISPUBLIC	Public status 1: Public 0: Private	INTEGER	32
Method	Method (GET/POST, etc.)	VARCHAR	255

14.2 FR_OPEN_APP Customer information

Field Name	Description	Data Type	Length
ID	ID	VARCHAR	255
createTime	Created on:	timestamp	26
DESCRIPTION	Description	VARCHAR	255
EDITABLE	Editable 1: Editable 0: Non-editable	INTEGER	32
ENABLE	Available 1: Available 0: Unavailable	INTEGER	32
name	Internationalization key for display name	VARCHAR	255
ICON	Icon	VARCHAR	255
secret	Secret key (encrypted)	VARCHAR	255
SPAREAUTH	Authenticator ID	VARCHAR	255

14.3 FR_OPEN_AUTH Permission information

Field Name	Description	Data Type	Length
ID	ID	VARCHAR	255
createTime	Created on:	timestamp	26
DESCRIPTION	Description	VARCHAR	255
EDITABLE	Editable 1: Editable 0: Non-editable	INTEGER	32
ENABLE	Available 1: Available 0: Unavailable	INTEGER	32
name	Internationalization key for display name	VARCHAR	255
CLAZZ	Class path	VARCHAR	255
config	Configuration item (json)	VARCHAR	255
TDEFAULT	Default parameters (json)	VARCHAR	255

14.4 FR_OPEN_GROUP API Group Name

Field Name	Description	Data Type	Length
ID	ID	VARCHAR	255
createTime	Created on:	timestamp	26
DESCRIPTION	Description	VARCHAR	255
EDITABLE	Editable 1: Editable 0: Non-editable	INTEGER	32
ENABLE	Available 1: Available 0: Unavailable	INTEGER	32
name	Internationalization key for display name	VARCHAR	255

14.5 FR_OPEN_PRIVILEGE Open Platform Privilege Table

Field Name	Description	Data Type	Length
ID	ID	VARCHAR	255
API ID	apiId	VARCHAR	255
clientId	Customer ID	VARCHAR	255

14.6 FR_OPEN_RELATION Group and API Association Table

Field Name	Description	Data Type	Length
ID	ID	VARCHAR	255
GROUPID	Group ID	VARCHAR	255

14.7 FR_OPEN_API_PERFORMANCE API Query Rate

Field Name

Description

Data Type

Length

API ID

VARCHAR

255

frequency

Access frequency limit for the corresponding API

Unit: times/s

INTEGER

15. Multi-Product Connection Tool Plugin

Note: All tables in this chapter are generated only when the multi-product connection tool plugin is installed.

15.1 FINE_COORDINATOR_ENTRY Template from the Server

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
ORIGINPATH	Original path of the server template	VARCHAR	255

15.2 FINE_COORDINATOR_SERVER Information of the Server

Field Name	Description	Data Type	Length
ID	Primary key	VARCHAR	255
name	from Server Name	VARCHAR	255
URL	URL address of the server	VARCHAR	1000
WITHTEMPLATE	Whether it is a template server 0: No 1: Yes	Boolean	/

Previous：Configuring MySQL8 Databases

Next：FINE_CONF_ENTITY Table Modification Through Data Entry

Helpful
Not helpful
Only read

中文（简体）中文（繁體）日本語

English