反馈已提交
网络繁忙
This article briefly introduces the table field descriptions contained in the FineDB database.
Note: Due to the different types of external databases, the data types of the fields are not completely consistent. This article takes the built-in database of the project as an example, and users need to match them by themselves.
Classification
subcategory
Table Name
Introduction
Access control
User-Department Position-Role
FINE_USER
user table
FINE_EXTRA_PROPERTY
User additional information sheet
FINE_DEPARTMENT
Department table
FINE_POST
job list
FINE_DEP_ROLE
The intermediate table of department positions, through which users associate departments and positions
FINE_CUSTOM_ROLE
custom role table
FINE_USER_ROLE_MIDDLE
An intermediate table for user roles, through which users are associated with custom roles and department job roles
FINE_SOFT_DATA
Synchronized user soft-deleted data table to store the data of synchronization user's soft-deletion
permissions-directory
FINE_AUTHORITY
Permission table, only records the permissions granted to the current directory, the template and subdirectory permissions in this directory will not be recorded
FINE_AUTHORITY_OBJECT
Permission entity table, which records the object, directory name, and report name of the permissions of the current directory (excluding templates and subdirectories under this directory)
FINE_AUTH_PREFERENCE
Permissions Panel User Preferences
FINE_HOMEPAGE_EXPAND
Home Extension Form
Documents extended attributes of a home type permission entity
FINE_FAVORITE_ENTRY
Favorite node table
Platform operation
Log in
FINE_LAST_LOGIN
Last Login Information Form
FINE_LOGIN_LOCK
login lock table
Lockout due to too many incorrect passwords
For details, see: Login Lockout
FINE_BLOCK_IP
Login Lock IP Table
Lockout due to high access frequency from the same IP
For details, see: Access Control
Backup restore
FINE_BACKUP_NODE
Backup node table
Scheduled
FINE_SCHEDULE_TASK
Scheduled task table
FINE_SCHEDULE_TASK_PARAM
Scheduled task parameter value
FINE_SCHEDULE_RECORD
Record task execution logs
FINE_SCHEDULE_OUTPUT
Export in scheduled tasks
FINE_BASE_OUTPUT
Task attachment processing master table
FINE_OUTPUT_CLASS
custom class handling
FINE_OUTPUT_CLIENT_NOTICE
Client notification
FINE_OUTPUT_EMAIL
push mail
FINE_OUTPUT_FTP
FTP upload
FINE_OUTPUT_MOUNT
Scheduled task mount directory
FINE_OUTPUT_PLATFORM_MSG
Platform system messages
FINE_OUTPUT_PRINT
print processing
FINE_OUTPUT_SFTP
SFTP upload
FINE_OUTPUT_SMS
send messages
FINE_BASE_MESSAGE
Platform message master table
FINE_PROCESS_MESSAGE
escalate news
FINE_SYSTEM_MESSAGE
FINE_MOBILE_DEVICE
Mobile device table
information
report
FINE_WORKFLOW
Process in the escalation process
FINE_WORKFLOW_TASK
Tasks in the escalation process
FINE_WORKFLOW_TASK_IMPL
The specific tasks issued under the tasks in the reporting process
FINE_WORKFLOW_NODE
Nodes in the escalation process
FINE_WORKFLOW_STASH_DATA
Data staging in the reporting process
FINE_WORKFLOW_LOG
Operation logs in the reporting process
System Management
configure
FINE_CONF_CLASSNAME
If the field of the configuration class is an interface type, record its type
FINE_CONF_ENTITY
Stores data in configuration classes
FINE_CONF_XMLENTITY
The structure of some fields is very complex, in order to store it in the database, the way to store it as XML
FINE_INTERNATIONAL
A table to record multilingual data
SWIFT module
FINE_SWIFT_COL_IDX_CONF
Field index configuration
FINE_SWIFT_CONFIG_ENTITY
Swift internal configuration table
FINE_SWIFT_METADATA
Used to store data table metadata
FINE_SWIFT_SEG_LOCATION
Swift Segment distribution information
FINE_SWIFT_SEGMENTS
Swift Segment Details
FINE_SWIFT_SERVICE_INFO
Save Swift service information
FINE_SWIFT_TAB_IDX_CONF
table index configuration
FINE_SWIFT_TABLE_PATH
Cube intermediate directory configuration management
Quartz Modules
QRTZ_BLOB_TRIGGERS
Triggers stored as Blob
QRTZ_CALENDARS
Calendar information storage table
QRTZ_CRON_TRIGGERS
Stores triggers of type Cron
QRTZ_FIRED_TRIGGERS
Store fired triggers
QRTZ_JOB_DETAILS
Store a JobDetail information
QRTZ_LOCKS
Stored procedure pessimistic locking information
QRTZ_PAUSED_TRIGGER_GRPS
information for a paused Trigger group
QRTZ_SCHEDULER_STATE
Storage cluster note instance information
QRTZ_SIMPLE_TRIGGERS
Information on Simple Triggers
QRTZ_SIMPROP_TRIGGERS
Store CalendarIntervalTrigger and DailyTimeIntervalTrigger
QRTZ_TRIGGERS
Basic information about triggers
other modules
mobile
FINE_MOBILE_PUSH_MESSAGE
Mobile message push table
fine_weixin_user_relation
Platform WeChat User Correspondence Table
fine_weixin_output
Scheduled task information pushed by WeChat
fine_weixin_agent
Information sheet pushed to WeChat
fine_weixin_group
Information sheet pushed to WeChat group
fine_dingtalk_user_relation
Platform DingTalk User Correspondence Table
fine_dingtalk_output
Scheduled task information pushed by Dingding
fine_dingtalk_agent
Information sheet pushed to Dingding
fine_dingtalk_group
Information table pushed to Dingding group
FINE_PARAM_TEMPLATE
Template parameter combinations
FINE_PRINT_OFFSET
print offset
FINE_PRINT_OFFSET_IP_RELATE
print offset IP association table
FINE_REMOTE_DESIGN_AUTH
Remote Design User Form
FINE_WRITE_STASH
Fill out the temporary form
FINE_PROCESS_EXPAND
Extended attribute table for reporting process type permission entity
FINE_REPORT_EXPAND
Extended property sheet for report type permission entities
FINE_EXCEL_SUBMIT_TASK
Excel bulk import permission entity extension table
FINE_VCS
Template version management table
BI
FINE_PACK_FILTER
BI business package line filter table
FINE_BI_REPORT_EXPAND
BI report extension table
FINE_DASHBOARD_INDEX
Dashboard Node Index Table
FINE_REPORT_TABLES_INDEX
Dataset table used by dashboard
FINE_REPORT_STYLE
Template style configuration
FINE_SHARE_INDEX
Store shared data permission settings
fine_update_task
Update task list
New in version 5.1.12 and later
fine_update_task_detail
Update task schedule
Note: Based on the above table structure, and the tables are not directly related, so the data in the intermediate table must be deleted manually if it involves direct operation of the database.
For example: delete a department = delete department + delete dep_role + delete user_role_middle;
Delete a user = delete user + delete user_role_middle + delete extra_property.
Field Name
Description
Type of data
Length
Remark
ID
primary key
VARCHAR
255
Association 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
BIRTHDAY
Birthday
TIMESTAMP
26
-
CREATIONTYPE
create type
· 1: Manual creation
· 2: Synchronous creation
INTEGER
32
DESCRIPTION
describe
1000
EMAIL
Mail
ENABLE
Whether to enable
· true: enable
· false: not enabled
BOOLEAN
0
LANGUAGE
language
LASTOPERATIONTYPE
Last Modified Type
· 1: Manual modification
· 2: Synchronous modification
MALE
gender
· true: male
· false: female
MOBILE
Phone number
PASSWORD
password
The value of this field is the encrypted text of the platform user password, which does not affect the platform user's login data decision system.
REALNAME
Name
USERNAME
username
fine_base_message>userName
fine_workflow_task>creatorName
fine_schedule_record>creator
fine_schedule_task>creator
WORKPHONE
REALALIAS
realName sort index
For example, if the name is Anna, REALALIAS is an
FR: 2019-12-05 and later JARs, new fields
BI: 2020-01-15 and later JARs, new fields
USERALIAS
userName sort index
For example, the username is Alice, and USERALIAS is alice
TENANTID
Tenant ID
No use for now, reserved field
SALT
Salt value parameter
When the user password is updated, the salt value is updated accordingly, increasing the security
FR: 10.0.18 and later, new fields
BI: 5.1.15 and later, new fields
NAME
property name
RELATEDID
userid
fine_user>id
TYPE
the associated data item type
VALUE
attribute value
65536
fine_dep_role>departmentId
Department name
PARENTID
Parent Department ID
FULLPATH
Department full path
Grandfather Department ID
...
FR: 2019-05-20 and later JARs, new fields
BI: 2019-06-13 and later JARs, new fields
ALIAS
NAME sort index
For example, the department is the leadership department, and ALIAS is the ldb
BI: 2010-01-15 and later JARs, new fields
4. FINE_POST Table
fine_dep_role>postId
job title
For example, the position is development engineer, and ALIAS is kfgcs
Field name
fine_user_role_middle>roleId
DEPARTMENTID
Associated department and job ID
· departmentId is empty, postId is empty: all department roles of the built-in + sync department (not visible in the front desk)
· department ntId is empty, postId is not empty: does not exist
· departmentId is not empty, postId is empty: indicates a department role that does not contain a job title
· departmentId is not empty, postId is not empty: Indicates normal department job role
POSTID
fine_post>id
· 1 - Manual modification
· 2 - Sync Modifications
fine_department>id
Intermediate data full path
· 1: Manually created by the administrator
· 2: Synchronous dataset creation
character name
NAME sort field index
For example, the role is project operation and maintenance, and ALIAS is xmyw
7. FINE_USER_ROLE_MIDDLE Table
ROLEID
The associated generalized role ID
depRoleId or customRoleId
fine_dep_role>id
fine_custom_role>id
ROLETYPE
associated generalized role type
· 1: Departmental Position
· 2: Custom Characters
USERID
associated user ID
8. FINE_SOFT_DATA Table
Note: This table is added in FineBI version 5.1.10 and later.
The data deleted in the synchronization source is actually deleted from the finedb, and different types of data are saved in the soft delete table.
The data recovered in the synchronization source is recovered from the soft delete table. The ID of the field with the same name will not change, and the use of permissions will not be affected.
DELETEDID
id to delete
1) The field DELETEDID+TYPE forms a unique key
That is, the DELETEDID and TYPE of any two data cannot be exactly the same
2) The field DELETEDNAME+TYPE forms a unique key
That is, the DELETEDNAME and TYPE of any two data cannot be exactly the same
DELETEDNAME
name to delete
· User: userName
· Department: Calculated full department name
· Position: job title
· role: role name
· Department position: department id + position id
Deleted data type
· 1: Department
· 2: Role
· 3: User
· 4: Position
· 5: Intermediate table of department positions
AUTHORITY
permission value
1 - Deny
2 - Allow
AUTHORITYENTITYID
The associated permission entity id
FINE_AUTHORITY_OBJECT>id
AUTHORITYENTITYTYPE
The associated permission entity type
Platform type
0 - Directory permissions, management system permissions, entities are in the authority_object table
1 - Personnel management-department authority, personnel management-role authority
2 - Data connection permissions
7 - Scheduled scheduling permissions
Report type
101 - FineReport Template Privileges (Template Certification)
BI type
201- BI Business Package Permissions
202- BI business package line filter permission (*not perceived by the outside world)
203- BI Dashboard permissions (mainly for sharing)
204- BI Template Permissions (Template Authentication)
205- BI Dashboard Share Control (Role to Role)
AUTHORITYTYPE
Permission type
1 - View permissions
2 - Authorization Permissions
3 - Edit permissions
4 - Data connection management rights
101 - FineReport Template Certification Authority
102 - FineReport Template View Rights
103 - FineReport Template Filling Permission
104 - Bulk Import Task Permissions
201 - Business Package Use Rights
202 - Business Package Management Rights
203 - BI report export permission
204 - BI Dashboard Sharing Permissions
205 - BI Template Authentication Permission
206 - BI Template View Permission
207 - BI template export permission
208 - BI Dashboard Share Role Control Permissions
209 - BI Dashboard sharing function permission
210 - BI Dashboard Public Links Feature Permission
the associated generalized role id
fine_user_role_middle>roleid
1 - Department, Title under the Department
2 - Custom Characters
3 - User
4 - Title
Contains directory information, management system
FINE_AUTHORITY>AUTHORITYENTITYID
EXPANDID
the associated extended attribute record id
EXPANDTYPE
the associated extended attribute type
1 - Platform Management System Node
2 - Home
3 - Directory
5 - Links
6 - Documents
101 - Escalation Process
102 - FineReport Reports
201 - BI Reports
The associated parent node ID
COVERID
Cover ID
Table of Contents Cover in System Administration > Appearance
Configuration >Table of Contents Styles
DEVICETYPE
display type
0 - Unchecked PC, Tablet, Phone
1 - PC
2 - Tablet
4 - Cell Phone
5 - Check PC, Mobile
6 - Check Tablet, Phone
7 - Tick PC, Tablet, Phone
DISPLAYNAME
Display report name and directory name
ICON
Icon ID
Directory Icons in System Administration > Appearance Configuration > Directory Styles
PATH
Path, different entry types have different meanings
SORTINDEX
Sort order
BIGINT
64
MOBILEICON
Mobile Icon ID
entity full path
AUTHTYPE
Permission panel type
AUTHVISIBLECFG
Permission Visibility Configuration
User ID
ANDROIDPADHOMEPAGE
Home link for Android tablets
ANDROIDPHONEHOMEPAGE
Home link for Android phones
IPADHOMEPAGE
Home link for iPad
IPHONEHOMEPAGE
Home link for iPhone
PCHOMEPAGE
Home page link for PC
Homepage Type
0 - FineReport template
1 - Platform Directory
2 - Link
3 - FineBI Template
ENTRYID
Favorite report ID
TIME
Collection time
Favorite User ID
CITY
Login to your city
IP
Login IP
Log in time
Login User ID
ERRORTIME
Number of wrong passwords
LOCKOBJECT
Lock IP or username
LOCKOBJECTVALUE
the value of IP or username
LOCKTIME
when is it locked
LOCKED
usually empty
UNLOCKTIME
when to unlock
CREATETIME
lock time
Locked IP
REJECTEDVISITS
Number of rejections
BACKUPMODULE
Backup module
jar: JAR package
jar-cluster: The jar package under the cluster (more special. Under the cluster, the jar package backup will be automatically converted to the proxy implementation, so this module is separated separately)
plugins: plugins
dashboards: BI templates
reportlets: report templates
config: platform configuration
BACKUPNAME
backup name
BACKUPTIME
When to back up
SAVEPATH
Backup address
BACKUPSIZE
Backup file size
DOUBLE
type
auto: automatic backup
manual : manual backup
BACKUPENDTIME
Backup end time
FR: 10.0.11 and later, new fields
BI: 5.1.8 and later, new fields
STATUS
Backup Status 0: None 1: Successful 2: Failed
DETAIL
Details (Error log)
fine_schedule_task_param>taskId
fine_schedule_record>taskId
BACKUPFILEPATH
Backup file path
reserved field, unused
CREATOR
task creator
fine_user>userName
EDITABLE
Whether the task is editable
true: editable
false: not editable
FILECLEARCOUNT
Number of attachments cleaned
-1: do not clean up
0: Clean up when the task ends
1: do not clean up
Other positive integers: reserved times
NEXTFIRETIME
next execution time
yyyy-MM-dd HH:mm:ss
OUTPUTSTR
Task attachment processing type combination string, used for filtering conditional queries
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 - Client notification
10 - SFTP upload
PREFIRETIME
last execution time
REPEATTIME
Repeat time interval
REPEATTIMES
repeat times
SENDBACKUPFILE
whether to send backup files
true: send
false: do not send
SHOWTYPE
Display type
0 - Pagination preview
1 - Fill out preview
2 - Data Analysis Preview
3 - PC side preview
4 - New report
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)
TASKDESCRIPTION
mission details
TASKNAME
mission name
TASKPARAMETER
Task parameters
JSON format, including 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 - Integer
Double - Double type
Date - the date
Boolean - Boolean value
TableColumn - Dataset column
value parameter value
If the parameter input method is the default, the value is a string
If the parameter input method is dataset, it includes value dataset name, colname dataset field value
TASKSTATE
0 - start
1 - Pause
2 - closed
It does not necessarily correspond to the state displayed in the front desk, and needs to be calculated before being displayed to the front desk.
TASKTYPE
task type
0 - no scheduling object
1 - Report Template
2 - BI Template
TEMPLATEPATH
template path
TRIGGERGROUP
trigger group
json form, including multiple triggers, including trigger type, time, etc.
triggerType trigger type:
1 - execute only once
2 - Simple repetition
3 - Detailed frequency settings
4 - Expression Settings
startTime start time:
startType start type:
1 - Execute now
2 - Select start time
endType end type:
1 - End immediately after execution
2 - Indefinite
3 - Select an end time
4 - how many additional executions
recurrenceInterval Simple recurrence interval (optional)
recurrenceIntervalUnit Simple recurrence interval time unit (optional)
1 minute
2 hours
3 days
4 weeks
repeatCount additional execution times (not required):
integer
hours Detailed frequency execution hours (optional):
minutes Detailed frequency execution minutes (not required):
dayType details the frequency of execution execution day (not required):
1 - Daily
2 - Weekly
3 - per month
monthDays Detailed frequency When the execution day is monthly, select the specific number of days in each month (not required):
integer array
weekDays Detail frequency When the execution day is weekly, select the specific days of the week (not required):
months When the detailed frequency is executed, which months are executed (not required):
USERGROUP
user group
json form:
customRole role list: array of role IDs
customRoleStr role list string: for foreground display
departmentAndPost department list: array of department IDs
departmentStr department list string: for front desk display
platformUser user list (optional): array, format is "name(username)"
platformUserStr user list string (not required): for foreground display
userType User type: 1 - platform user, 2 - custom user
columnIndex custom user-dataset column number (not required)
columnIndexStr custom user-dataset column name (not required)
tableDataName custom user-dataset name (not required)
SCHEDULEOUTPUT
task push
fine_schedule_output>id
CONDITIONPARAMETER
Custom class parameter for execution condition
name parameter name
FR: 2020-06-08 and later JARs, new fields
BI: 2020-08-04 and later JARs, new fields
PARAM
parameter list
parameter name: parameter value
TASKID
task id
fine_schedule_task>id
Note: For projects with JAR packages before 2019-05-20, use the fine_schedule_record table to store the execution logs of scheduled tasks
For projects with JAR packages on 2019-05-20 and later, use the fine_schedule_record table in the LogDB database to store the execution logs of scheduled tasks. Please refer to: Platform log LogDB database
creator
DETAILMESSAGE
details
FILEPATH
Generate attachment path
LOGMESSAGE
log information
LOGTIME
task execution time
log print time
LOGTYPE
log type
0 - fail
1 - Success
2- Skip
next recording time
RUNTYPE
Attachment Handling Type
0 - snapshot generation
1 - Email Send
2 - FTP upload
3 - Platform news push
4 - Document Printing
5 - SMS sending
6 - Mounting the platform
7 - Custom Class Handling
8 - Timed reporting
9 - Client Notification
-1 - attachment sent (default)
fine_schedule_task>scheduleOutput
fine_base_output>output_Id
BASENAME
Generate attachment name
CREATEATTACHBYUSERNAME
Whether to generate different attachments by different users
1 - yes
0 - no
FORMATS
export attachment type
json format: formatNum file processing method:
0 - output CPR
1 - Export the new version of EXCEL
2 - Output PDF
4 - Output WORD
8 - Output legacy EXCEL
16 - Output PNG
32 - Output FRR
ACTIONNAME
Attachment handling class name
EXECUTEBYUSER
Whether to execute separately for different users
RESULTURL
result link
OUTPUTID
export id
CLASSNAME
custom class name
fine_base_output>id
ADDRESSEE
Receiver
CONTENT
content
CUSTOMIZELINK
custom link
LINKOPENTYPE
link type
1 - Timed result link
2 - Custom Links
MEDIAID
Image ID for rich text message
SUBJECT
theme
TERMINAL
push terminal
Currently fixed at 1, representing app notification
message type
1 - Link message
2 - Graphic message
3 - File message
ADDLINK
BCCADDRESS
Bcc
BODYCONTENT
CCADDRESS
cc
PREVIEWATTACH
Text preview
USEATTACH
Use attachments
CUSTOMADDRESS
CUSTOMBCCADDRESS
CUSTOMCCADDRESS
PREVIEWWIDGET
Whether to check "Text preview component content"
FR: 10.0.13 and later, new fields
BI: 5.1.10 and later, new fields
PORT
The port number
upload path
SERVERADDRESS
server address
FTPMODE
FTP mode
passive: passive mode
avtive: active mode
FOLDERENTRYID
mount directory id
FOLDERENTRYNAME
mount directory name
FOLDERENTRYSTR
mount directory
PRINTERNAME
printer name
PRIVATEKEY
private key
TEMPLATEID
Template ID
SMSPARAM
SMS parameters
json, for each parameter:
id parameter
IDname parameter name
Type types include:
Boolean — Boolean value
Formula - Formula
non empty
TRUE
message creation time
FALSE
DATETIME
message time
new
MESSAGE
Message content
READED
Has it been read
TOASTED
Is there a pop-up prompt?
0 - system message
1 - Escalation message
2 - Template message
3 - Mobile Messages
-1 - unknown message
URL
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 block routing, jump to a certain tab page of system management
4 - URLs to open multiple templates within the platform
ALLTASKID
All task IDs
DEADLINE
End Time
PROCESSED
Is it done
1 - Done
0 - not completed
report task ID
fine_base_message>id
Currently fixed at 1, representing PC-side message notification
TITLE
Note: For JARs after 2018-12-27, new reporting tables are added.
creation time
CREATORID
Creator ID
fine_workflow_stash_data>userId
fine_workflow_log>operatorname
Process name
NODESID
Node ID
fine_workflow_node>id
fine_workflow_task_impl>taskId
fine_workflow>creatorId
CREATORNAME
creator name
fine_user>username
DEADLINEDATE
deadline
DEADLINETYPE
cutoff type
ISSUECONTROL
Scheduled delivery
ISSUEOVER
Whether the delivery is over
LEAPFROGBACK
Fallback
parent task id
fine_workflow_task_impl>parentId
PROCESSID
Process ID
fine_workflow_task_impl>processId
REMINDCONTROL
Reminder method
TASKNAMECALCULATEONCE
Whether to check "Only count once when the task is initiated" when adding a task
1 - Checked
2 - unchecked
ALERTED
Whether to warn
COMPLETEESTATE
The operator and completion status of the current task,
1 - Completed
For example: {"demo/authority/product sales query.cpt":{"sunlin":0}}
Creation time (delivery time)
CURRENTNODEIDX
current process node id
FRTASKID
ID of the source task
task name
NEEDALLCOMPLETE
Does it need to be completed
NODEROUTE
Path traveled by the node
json
NOTE
16777216
OPERATORJSON
The first nodes on Node are multi-user
OPERATOROFFSET
The number of users of the multi-user node
OPERATOROFFSETNAME
The name of the first user of the multi-user node
fine_workflow_task>parentId
VARCH AR
FAL SE
fine_workflow_task>processId
REPORTOFFSET
the first few templates
SENDTIME
send time
SENDER
sender
SENDERID
sender ID
SONTASKID
ID of the subtask
[{nodeIdx:0, userId:1, taskId:1}]
STATE
-1 - initial
0 - pending escalation
1 - Pending review
2 - Approved
3 - was returned
4 - closed
5 - Timeout
fine_workflow_task>Id
fine_workflow>nodesId
ALERTCONTROL
Alert Details
permission
node name
Does it need to be transferred after it is all completed?
NEEDOFFLINEREPORT
Do you need to fill in offline
REPORTCONTROL
Escalation Details
DATA
data
REPORTPATH
report path
time
OPERATORNAME
operator name
PROCESSNAME
The position of the current field in the configuration
The field type to which the corresponding configuration value in the configuration belongs
The location of the data in the configuration
data value
Note 1: Most of the configuration content stored in the database is in this table, such as: id = BackupConfig.backupMemory, value = 1024 means to configure a value of 1024 for the backupMemory in BackupConfig, which means that the automatic backup occupies a maximum of 1024mb.
The common configuration items of the platform and the front desk do not provide a configuration interface, which are basically stored in the fine_conf_entity table. For details, please refer to: fine_conf_entity table introduction
the XML text value of the field
BLOB
67108864
Note: This table appears in the FineReport version of the JAR package on 2020-02-28 and later.
I18NKEY
international key
international language
zh_CN: Simplified Chinese
zh_TW: Traditional Chinese
en_US: English
ja_JP: Japanese
ko_KR: Korean
I18NVALUE
internationalized value
Chinese characters need to be converted into Unicode encoding with an online conversion tool and then written
COLUMNNAME
TABLEKEY
Datatable SourceKey
REQUIREGLOBALDICT
whether to generate a global index
REQUIREINDEX
whether to generate an index
CONFIGKEY
where the configuration is located
CONFIGVALUE
configuration value
SourceKey calculated by the data table
FIELDS
Field information
REMARK
translation name
SCHEMANAME
Schema of database table
SWIFTSCHEMA
Data file storage location
CUBE / LOG
TABLENAME
CLUSTERID
cluster ID
SEGMENTID
Generated Segment ID
SOURCEKEY
Data table SourceKey, indicating which table the Segment belongs to
SEGMENTORDER
Segment number
SEGMENTOWNER
SEGMENTURI
Relative URL of the data file
STORETYPE
Data save type
MEMORY - memory storage, only in memory, lost after shutdown
NIO - is to write the contents of the memory to the file to solve the problem of shutdown loss
FINE_IO - an io framework implemented by fr itself. When the NIO file is full, it will be written to FINE_IO.
Data file storage directory
Service ID
CLUSTER_ID
IS_SINGLETON
whether to start only one
SERVICE
Service type
cluster_master_service - record the master node id for all nodes to use synchronously Other - services started by each node (such as query, import, history, real-time and other services)
SERVICE_INFO
Additional information about the service
Table SourceKey
ALLOTRULE
block logic
Single machine is LOCAL
LASTPATH
last used temporary directory
TABLEPATH
the currently used intermediate directory
TMPDIR
Intermediate directory used when Cube is generated
As a Blob type store, it is used when Quartz users use JDBC to create their own custom Trigger types, and the JobStore does not know how to store the instance.
SCHED_NAME
Schedule name
TRIGGER_GROUP
Foreign key to trigger_group of qrtz_triggers table
TRIGGER_NAME
Foreign key to qrtz_triggers table trigger_name
BLOB_DATA
A blob field that holds the persistent Trigger object
VARBINARY
To store calendar information in Blob type, quartz can configure a calendar to specify a time range.
CALENDAR_NAME
Calendar name
CALENDAR
A blob field that stores the persistent calendar object
4000
A table of cron expressions to store triggers.
CRON_EXPRESSION
Cron expressions
TIME_ZONE_ID
Time zone
Stores state information related to the triggered Trigger and execution information of the associated Job.
ENTRY_ID
scheduler instance id
FIRED_TIME
trigger time
NUMERIC
19
INSTANCE_NAME
Scheduler instance name
IS_NONCONCURRENT
Is it concurrent
JOB_GROUP
The name of the group the job belongs to in the cluster
JOB_NAME
The name of the job in the cluster
PRIORITY
priority
REQUESTS_RECOVERY
Whether to accept resume execution, the default is 0
SCHED_TIME
time set by timer
state
Stores details for each configured jobDetail.
The name of the group to which the job belongs in the cluster
The fully qualified name of a notejob implementation class in the cluster. Quartz finds the job class based on this path to the classpath.
IS_DURABLE
Is it persistent
1 - Yes, quartz will persist the job to the database
Whether to execute concurrently
IS_UPDATE_DATA
Whether to update the data
JOB_CLASS_NAME
The fully qualified name of the notejob implementation class in the cluster. Quartz finds the job class based on this path to the classpath
JOB_DATA
A blob field that holds the persistent job object
Stores information about pessimistic locking of the program (if pessimistic locking is used).
LOCK_NAME
Pessimistic lock name
Stores information for a paused Trigger group.
qrtz_triggers table trigger_group foreign key
Store the note instance information in the cluster, and quartz will periodically read the information in the table to determine the current state of each instance in the cluster.
The name of the org.quartz.scheduler.instanceId configuration in the previous configuration file,
will write to this field
CHECKIN_INTERVAL
Check interval
LAST_CHECKIN_TIME
Last check time
Stores a simple Trigger, including the number of repetitions, the interval, and the number of times it has been triggered.
trigger name
REPEAT_COUNT
Statistics of repetitions
REPEAT_INTERVAL
repeat time interval
TIMES_TRIGGERED
Triggered times
qrtz_simprop_triggers stores CalendarIntervalTrigger (similar to SimpleTrigger, specifying a task trigger that starts from a certain time and executes at a certain interval) and DailyTimeIntervalTrigger (specifies a task trigger that executes at a certain time interval within a certain period of time every day)
Foreign key to trigger_name of qrtz_triggers table
BOOL_PROP_1
The first parameter of trigger of type Boolean
BOOL_PROP_2
The second parameter of trigger of type Boolean
DEC_PROP_1
The first parameter of trigger of type decimal
DEC_PROP_2
The second parameter of trigger of type decimal
INT_PROP_1
The first parameter of trigger of type int
INT_PROP_2
The second parameter of trigger of type int
LONG_PROP_1
The first parameter of trigger of type long
LONG_PROP_2
The second parameter of trigger of type long
STR_PROP_1
The first parameter of trigger of type String
STR_PROP_2
The second parameter of trigger of type String
STR_PROP_3
The third parameter of trigger of type String
Save the basic information of the trigger.
Note: After setting the user synchronization data set , find the data whose "TRIGGER_NAME" is "syncUser" in the qrtz_triggers table, and you can view the update user time.
trigger group name
schedule name
Detailed description information
END_TIME
Foreign key to qrtz_job_details table job_group
Foreign key to qrtz_job_details table job_name
MISFIRE_INSTR
measures or strategies to compensate for the implementation of
NEXT_FIRE_TIME
next trigger time
PREV_FIRE_TIME
Last trigger time
START_TIME
Starting time
TRIGGER_STATE
Current trigger state
WAITING - waiting
PAUSED - Pause
ACQUIRED - normal execution
BLOCKED - blocked
ERROR - error
TRIGGER_TYPE
type of trigger
SIMPLE - Repeated execution after a specific time interval. If it starts at 9:00, it will be executed every 1 hour.
CRON - Calendar based schedule, such as execution every Tuesday at 2am.
APPOINT_ID
Platform cluster node id. Indicates which node the trigger needs to run on, if it is empty, it will be executed.
Added in May 2020
CREATEDATE
Date the device was added
DEVICENAME
device name
MACADDRESS
Device Mac Address
PASSED
Whether the device is certified
UPDATEDATE
Device Modification Date
associated username
GROUPID
Message receiving group ID
MSGTYPE
1 - normal text message
message title
Note: This table appears and data is generated only when "Client Notification > WeChat Notification" is selected in the scheduled task and saved.
FSUSER
Platform username
WEIXINUSER
WeChat userid
AGENTID
App ID
The content of the client notification
Customize the content of the link
Link type for client notifications
1: Timing scheduling link
2: Custom Links
The mediaId of the file or image obtained by calling the upload interface
The title of the client notification
Fixed is 2, corresponding to WeChat notification
message type for client notification
1: Link message
2: Graphic message
3: File message
Additional clients to receive messages, 1 for push group
CHATGROUPS
String array to store push group id
AGENTNAME
Application Name
CORPID
Enterprise corpId
SECRET
application key
timestamp
App types
1: The application of the management group key, which belongs to the old application
2: normal application
3: The application that failed to obtain the token
Note: This table appears and data is generated only when "Client Notification > WeChat Group Notification" is checked in the scheduled task and saved.
The chatid of the group, used for push
GROUPNAME
group name
Note: This table appears and data is generated only when "Client Notification > DingTalk Notification" is checked in the scheduled task and saved.
DINGTALKUSER
DingTalk userid
Fixed is 4, corresponding to Dingding notification
APPKEY
Apply appKey
1: normal application
2: The application that failed to obtain the token
Note: This table appears and data is generated only when "Client Notification > Dingding Group Notification" is checked in the scheduled task and saved.
TPGROUP
parameter combination
CPTNAME
template name
50
client ip address
20
OFFSETX
Lateral offset
OFFSETY
vertical offset
SIGN
Offset options
0 - no offset
1 - Global configuration
2 - Single Template Configuration
10
CHILDIP
Associate client IP
fine_print_offset>id
MOTHERID
Corresponds to the ID field of the print offset table
Path with remote design permission
PATHTYPE
path type
0 - file
1 - Folder
role type
0: no role
1: Departmental role
2: Custom Characters
3: User roles
staging data
PROCESSTYPE
Reporting process type
1: Reporting task management
2: Reporting process management
3: My escalation task
0 - Fill in
1 - Pagination
2 - Analysis
3 - Form Preview
TRANSMITPARAMETERS
Some custom preview parameters
Note: For FR projects with JAR packages after 2018-12-27, this table is added.
task creation time
associated template path
SUBMITTIME
submission time
COMMITCODE
Used to roll back the commit
COMMITMSG
git commit Msg
FILENAME
VERSION
version number
The row and column permission control information in the FineBI dataset is stored in this table.
FILTER
filter actual content
PACKAGEID
ID of the business package
Owned generalized role ID
Types of generalized roles owned
1-Department job role
2- Custom Characters
3- User roles
TABLEID
The ID of the filter associated data table
2020-9 New
BI template ID
This table holds all template information, including the number of the dashboard.
APPLYTIME
Application hang out time
CREATEBY
creator user id
FOLDER
mark whether it is a folder node
true: is a folder
false: not a folder
HANGOUT
mark pending status
-1: ungrouped (status of a normal user's dashboard folder)
1: Apply to hang out
2: hang out
3: Other status
INITTIME
LASTUPDATETIME
Last update time
MOUNTEDDIRIDS
The value of mountedDirlds is to be hung out
display name
PID
parent node id
REPORTID
Node id, the same as id
REPORTPUBLICLINK
public link
SHARED
field deprecation
WATERMARK
Whether the watermark is enabled
fine_dashboard_index>reportId
TABLES
Information about the datasets used by the dashboard
Template creator ID
GLOBAL
Is it a global style
true: is a global style that all users can select
flase: is a unique style for CREATEBY users
template style name
STYLE
Template style details
STYLEID
Template styleId
ENTITYID
Entity ID, i.e. reportID
ENTITYPATH
The entity path fullPath, which is the template path
ENTITYTYPE
entity type
0: Template
1: Template folder
SHARETYPE
Sharing data permission type
0: Use creator permissions
1: Use shareee permissions
Note: For BI projects of version 5.1.12 and later, this table is added.
For BI projects before 5.1.12, this part of the information can be viewed in LogDB.
meaning
planId
The unique identifier of the task instance, which is different for each run
string
taskName
Table name + task type (single table/business package/global)
startTime
task start time
Long
endTime
task end time
runningResult
finished condition
ALL: All successful
PART: Partial success
update status
END: has ended
RUNNING: run
triggerType
Trigger method
MANUAL: Manual
AUTO: timing
roleId
Trigger Id
roleName
Trigger name
countOverView
The update status of each type of table in the task. JSON
expectBaseTableUpdate expects the number of base tables
actualBaseTableUpdate The actual number of base tables that were successfully updated
expectComplexUpdate the expected number of bootstrap datasets
actualComplexUpdate actual number of successful bootstrap datasets
expectRelationUpdate Expected number of association updates
actualRelationUpdate the actual number of successful associations
extra1
extra field 1
extra2
extra field 2
extra3
extra field 3
Data insertion time, swift table cleanup required
loadId
Detail ID, unique within an update task
Integer
loadName
name of detail
The table is the table name + package name, and the association is the associated information
loadType
detail type
BASE: base table
FAST, ETL: Self-Service Datasets
RELATION: Relation
updateType
update type
FULL: full amount
INCREASE: Increment
LOADING: Updating
SUCCESS: success
PART_SUCCESS: Partial success
WAITING: waiting in line
WRONG: failed
Data update end time
effectTime
Effective time, really available
Update start time
execption
failure error message
failedSonId
The set of IDs of the table whose update failed due to the underlying table
fatherFailedIds
The ID collection of the parent table that failed to update
tableId
extra fields
updateCount
The number of rows changed, may increase or decrease
errorCode
error code
totalCount
total number of rows
deleteCount
Increment and decrement the number of rows
writeTime
file write time
etlFlow
Steps for Self-Service Datasets
appendCount
Incremental number of rows
columns
List
jdbcTime
data acquisition time
openTime
sql execution time
infos
Non-error message (only internationalized key values and parameters)
feedback
鼠标选中内容，快速反馈问题
鼠标选中存在疑惑的内容，即可快速反馈问题，我们将会跟进处理。
不再提示
10s后关闭