template_name, object_id, service_id, sub_service_id, service_execution_code — workflow config binding (n8n_workflow_configs). Data: stc_development_v1.
| Template name | Object ID | Service ID | Sub service ID | Sub service meta ID | Service execution code | Workflow config | Created |
|---|
Data source: stc_development_v1 (n8n_workflow_configs, sub_service_meta, dm_object_new, service_executions). Mock data until backend API is connected.
This UI manages the mapping of template_name, object_id (DMF object code), service_id, sub_service_id, sub_service_meta_id, and service_execution_code to a specific n8n_workflow_config (workflow config binding).
Key tables (stc_development_v1):
| Table | Relevant columns |
|---|---|
| n8n_workflow_configs | id, workflow_id, name, operation_template_code, dmf_template_object, dependency_config_id |
| sub_service_meta | id, workflow_config_id → n8n_workflow_configs.id |
| service_workflow_executions | workflow_config_id → n8n_workflow_configs.id |
| dm_object_new | code (object_id), sub_service_meta_id |
MCP Configuration Control Tower shows the full chain: Service → Sub → Meta → DMF → MCP Tool → n8n Workflow/Config.