Skip to main content
V1.0 Update time 2024.11
When you configure a dedicated database for dedicated storage, the YiDA platform adds several required tables to it to store the data generated as you use YiDA. The schema of these tables is not fixed — it evolves with business growth and technical iteration, and new fields or tables may be added over time. In general, existing fields will remain unchanged to avoid disrupting your business operations, but the YiDA platform still recommends that you do not build strong dependencies on this data.

Table List

Odin_Open_Application_Data

Table name: odin_open_application_data Description: form instance data table (shared by form and report). Character set: UTF8
Column nameTypeLengthPrecisionScaleNullableDefault valueDescription
idvarchar128YUnique id; may be empty for historical data — uniqueness is still determined by pid
gmt_createtimestampNCreated time
gmt_modifiedtimestampNModified time
creatorvarchar64YCreated by
modifiervarchar64YLast modified by
is_deletedbpchar1NnWhether deleted
corp_idvarchar128YOrganization id where the instance is inserted
namespace_codevarchar128NApp appType
table_namevarchar128NForm model id
pidvarchar64NInstance id
parent_pidvarchar64YUsed in cases such as sub-table association, where the sub-table data is linked to the parent table’s pid through this field
json_datajsonbYSpecific component data, in json
data_versionint8N0Data change version
data_orderint8N0Data display order, typically used for sub-tables
Index nameTypeIncluded Fields
odin_open_application_data_gmt_modified_idx1Normalgmt_modified
odin_open_application_data_namespace_code_creator_idx1Normalnamespace_code,creator
odin_open_application_data_namespace_code_table_name_gmt_c_idx1Normalnamespace_code,table_name,gmt_create
odin_open_application_data_namespace_code_table_name_paren_idx1Normalnamespace_code,table_name,parent_pid,is_deleted
odin_open_application_data_namespace_code_table_name_pid_idx1Uniquenamespace_code,table_name,pid
odin_open_application_data_pid_idx1Normalpid

Tianshu_Form_Data_Operation_Log

Table name: tianshu_form_data_operation_log Description: Form data activity log table. Character set: utf8mb4
Column nameTypeLengthPrecisionScaleNullableDefault valueDescription
idbigint(20) unsigned200NGenerated via tianshu_form_data_operation_log_id_seqPrimary key
gmt_createdatetimeNCreated time
gmt_modifieddatetimeNModified time
creatorvarchar(64)64NCreated by
modifiervarchar(64)64NLast modified by
is_deletedchar(1)1NWhether logically deleted
system_typevarchar(64)64NSystem type
app_typevarchar(64)64NApp key
form_inst_idvarchar(128)128Nform instance data id
operation_typevarchar(64)64NAction type
operation_fieldvarchar(64)64NAction field
pre_valuemediumtext16777215YOriginal content
valuemediumtext16777215YModified content
shard_keyvarchar(130)130NSharding key
pre_codemediumtext16777215YCode corresponding to the original control value
codemediumtext16777215YCode corresponding to the control
operation_idvarchar(64)64YUnique action ID
parent_operation_fieldvarchar(64)64NROOTParent action field
parent_operation_idvarchar(64)64NROOTParent action id
trigger_srcvarchar(4000)4000YTrigger source description
trigger_typevarchar(4)4YTrigger source type
Index nameTypeIncluded Fields
idx_app_typeNormalapp_type
idx_inst_id_parent_operation_field_gmt_modifiedNormalform_inst_id,parent_operation_field,gmt_modified
idx_inst_id_parent_operation_field_parent_operation_idNormalform_inst_id,parent_operation_field,parent_operation_id
idx_operation_idNormaloperation_id
idx_operation_id_is_deletedNormaloperation_id,is_deleted
idx_opertaion_field_gmt_modifiedNormaloperation_field,gmt_modified
idx_parentoperationid_parentoperationfieldNormalparent_operation_id,parent_operation_field
PRIMARYPrimaryid
uk_inst_id_idUniqueform_inst_id,id

Tianshu_Proc_Inst_Carbon

Table name: tianshu_proc_inst_carbon Description: workflow instance CC recipient table Character set: utf8mb4
Column nameTypeLengthPrecisionScaleNullableDefault valueDescription
idbigint(20)190NGenerated via proc_inst_carbon_id_seqPrimary key
gmt_createdatetimeNCreated time
gmt_modifieddatetimeNModified time
shard_keyvarchar(130)130NSharding field
system_typevarchar(64)64NSystem category
app_typevarchar(64)64NApp type
form_uuidvarchar(128)128NForm UUID
is_deletedchar(1)1NDelete flag
form_inst_idvarchar(128)128NInstance ID
form_inst_titlevarchar(1024)1024NInstance title
carbonvarchar(64)64NCC recipient
activity_idvarchar(128)128NCC node ID
process_codevarchar(128)128NWorkflow code
inst_statusvarchar(32)32NInstance status
is_printedchar(1)1YWhether printed
inst_originatorvarchar(64)64YInstance initiator
Index nameTypeIncluded Fields
idx_carbonNormalcarbon
idx_carbon_appNormalcarbon,shard_key,is_deleted
idx_form_inst_idNormalform_inst_id
idx_form_uuid_carbonNormalform_uuid40,carbon20,is_deleted
idx_inst_originatorNormalinst_originator
idx_shard_keyNormalshard_key
PRIMARYPrimaryid

Tianshu_Data_Form_Version

Table name: tianshu_data_form_version Description: Association table between instance data and form version Character set: utf8mb4
Column nameTypeLengthPrecisionScaleNullableDefault valueDescription
idbigint(20) unsigned200NGenerated via data_form_version_id_seqPrimary key
gmt_createdatetimeNCreated time
gmt_modifieddatetimeNModified time
creatorvarchar(64)64NCreated by
modifiervarchar(64)64NLast modified by
form_uuidvarchar(128)128NForm id
model_uuidvarchar(128)128NModel id
inst_idvarchar(128)128NInstance id
versionbigint(20)190NForm version
system_typevarchar(64)64NSystem version
app_typevarchar(64)64NApp ID
shard_keyvarchar(130)130NSharding key
Index nameTypeIncluded Fields
idx_form_uuidNormalform_uuid
idx_inst_idNormalinst_id
idx_model_uuidNormalmodel_uuid
idx_shard_keyNormalshard_key
PRIMARYPrimaryid

Tianshu_Form_Data_Stash

Table name: tianshu_form_data_stash Description: Form cache table Character set: utf8mb4
Column nameTypeLengthPrecisionScaleNullableDefault valueDescription
idbigint(20) unsigned200NGenerated via form_data_stash_id_seqPrimary key
gmt_createdatetimeNCreated time
gmt_modifieddatetimeNModified time
shard_keyvarchar(130)130NSharding key
is_deletedchar(1)1NDelete flag
system_typevarchar(64)64NSystem identifier
app_typevarchar(64)64NApp identifier
form_uuidvarchar(64)64NForm UUID
inst_valuemediumtext16777215YForm content
creatorvarchar(64)64NCreated by
modifiervarchar(64)64NLast modified by
Index nameTypeIncluded Fields
idx_form_creatorNormalshard_key90,form_uuid,creator
PRIMARYPrimaryid

Tianshu_Form_Remark

Table name: tianshu_form_remark Description: Comments feature Character set: utf8mb4
Column nameTypeLengthPrecisionScaleNullableDefault valueDescription
idbigint(20) unsigned200NGenerated via form_remark_id_seqPrimary key
gmt_createdatetimeNCreated time
gmt_modifieddatetimeNModified time
creatorvarchar(64)64NCreated by
modifiervarchar(64)64NLast modified by
form_inst_idvarchar(128)128NInstance ID
reply_idbigint(20) unsigned200YAssociation ID
contenttext65535NContent
filesvarchar(3000)3000YAttachment
reply_user_idvarchar(64)64YReply user ID
at_user_idvarchar(640)640YMentioned user ID
is_deletedchar(1)1NnDelete flag
system_typevarchar(64)64NSystem type
app_typevarchar(64)64NApp type
shard_keyvarchar(130)130NSharding key
imagestext65535YImage
Index nameTypeIncluded Fields
idx_form_inst_idNormalform_inst_id
PRIMARYPrimaryid

Alibpms_App_Cm_Operator_Record

Table name: alibpms_app_cm_operator_record Description: workflow instance approval record table Character set: utf8mb4 Notes: Does not include approval tasks that are currently in progress.
Column nameTypeLengthPrecisionScaleNullableDefault valueDescription
idbigint(20)190NGenerated via pro_operator_record_id_seqPrimary key id
operatorvarchar(64)64YActual operator id
operate_timedatetime(3)YModified time
actionvarchar(256)256YAction description
remarktext65535YAction alias
process_instance_idvarchar(64)64Yworkflow instance ID
activity_setting_idvarchar(64)64YNode definition ID
task_idvarchar(64)64YTask ID
stepvarchar(256)256YAction step
visiblevarchar(128)128YWhether visible (true = visible, false = hidden)
app_keyvarchar(128)128YApp key
activity_idvarchar(64)64YNode ID
original_operatorvarchar(64)64YOriginal operator
agent_operatorvarchar(64)64YDelegated operator
operate_typevarchar(32)32YAction type
group_idbigint(20)190N1Integrator isolation
from_mobilechar(1)1NnFlag indicating whether submitted from mobile approval
fileslongtext4294967295YFlag file field
user_jobvarchar(70)70YUser job title flag
is_deletedchar(1)1NnDelete flag
gmt_modifieddatetimeYModified time
modifiervarchar(64)64YLast modified by
step_envarchar(256)256YAction step in English
noticetext65535YApproval responsibility in Chinese and English
reasontext65535YApproval reason in Chinese and English
digital_signvarchar(512)512YElectronic signature image
target_userstext65535YTarget users; separate multiple users with commas
Index nameTypeIncluded Fields
idx_activity_idNormalapp_key,activity_id
idx_process_instance_idNormalapp_key,process_instance_id,operate_time
idx_task_idNormalapp_key,task_id
operatorNormalapp_key,operator
original_operatorNormalapp_key,original_operator
PRIMARYPrimaryid

Other Tables

tianshu_instance_relation: form instance relation table — used by the legacy YiDA dedicated storage. Deprecated. yida_entity_instance: form instance data table — used by the legacy YiDA dedicated storage. Deprecated. Many users still depend on it; data is asynchronously synchronized through the odin_open_application_data table. We recommend using the odin_open_application_data table as the source of truth. The following example shows how to add an index on timeout — replace the placeholder values while still using odin_open_application_data as the reference:
  • Alternatively, use the productized interface. Manual index creation is preferred; if you are not sure how, create the index through the product instead. Indexes created through the product may occasionally fall short of optimal efficiency — contact R&D if needed.
For physical column scenarios — for example, when querying the phy_textfield_lmsj0bkf field below:
tianshu_form_data: Form data table — used by the legacy YiDA dedicated storage. Deprecated. ecds_xxxx: YiDA internal system tables — these are internal tables used for system operation. Do not operate on them, and do not manually create them when switching databases; they are generated automatically. yida_app_data_xxx: physical column table — has the same schema as odin_open_application_data, except that the json field is flattened. One table per form, and sub-tables are also independent tables. Details are as follows: The corresponding table name is the underline-lowercase form of the form page code above: yida_app_data_form_obd66r71q2asxubwc9p3g8yneplv2jcv43d6m3 Because database table name length limits must be observed, the sub-table name — which would originally be yida_app_data_form_obd66r71q2asxubwc9p3g8yneplv2jcv43d6m3_tableFieldXxx — is truncated with an md5 hash once it reaches 64 bytes. The final computation result is similar to the following:
tableName is yida_app_data_form_obd66r71q2asxubwc9p3g8yneplv2jcv43d6m3_tableFieldXxx, and tableNameHashPostfix is ”_” + tableNameMd5 (where tableNameMd5 is the md5-encrypted result 8af1899537e0ac902f784162207c0e54).