see sql files in
t_ds_usertable stores the
queue_nameinformation in the
t_ds_tenantstores queue information using
queue_idcolumn. During the execution of the process definition, the user queue has the highest priority. If the user queue is null, use the tenant queue.
user_idfield in the
t_ds_datasourcetable shows the user who create the data source. The user_id in
t_ds_relation_datasource_usershows the user who has permission to the data source.
t_ds_projcettable represents the user who create the project, and the
t_ds_relation_project_usertable represents users who have permission to the project.
t_ds_resourcestable represents the user who create the resource, and the
t_ds_relation_resources_userrepresents the user who has permissions to the resource.
t_ds_udfstable represents the user who create the UDF, and the
t_ds_relation_udfs_usertable represents a user who has permission to the UDF.
t_ds_process_task_relationand the associated key is
code + version. When the pre-task of the task is empty, the corresponding
t_ds_process_instance, one process instance corresponds to one or more task instances
t_ds_relation_process_instancetable is used to handle the case that the process definition contains sub-processes.
parent_process_instance_idrepresents the id of the main process instance containing the sub-process,
process_instance_idrepresents the id of the sub-process instance,
parent_task_instance_idrepresents the task instance id of the sub-process node. The process instance table and the task instance table correspond to the
t_ds_process_instancetable and the