This page helps developers understand how business tables, APIs, and frontend pages are connected. Use it before adding fields, changing queries, or extending modules.
Prefix Area Notes iot_IoT product, device, thing model, logs, and runtime data. Core business data. sys_User, role, menu, department, dictionary, and config. System administration and permission. gen_Code generator table and column configuration. Development tool data. oauth_OAuth client and token data. SSO and authorization. notify_Notification channel, template, and log. Message delivery. ai_AI providers, models, knowledge, and chat records. AI module data.
Business Area Tables API Area Frontend Entry Product and thing model iot_product, iot_model, iot_things_model/iot/product, /iot/modelvue3/src/views/iot/productDevice iot_device, device log tables/iot/devicevue3/src/views/iot/deviceRule and scene rule and scene tables /rule/*, /scene/*vue3/src/views/rule, vue3/src/views/sceneData center history and report-related tables /datacenter/*vue3/src/views/datacenterIoT card card-related tables /card/*vue3/src/views/cardApp version app-version tables /appVersion/*vue3/src/views/appAI AI-related tables /ai/*vue3/src/views/aiGenerator gen_table, gen_table_column/tool/genvue3/src/views/tool/gen
Change Required Checks Add field SQL migration, entity, DTO/VO, mapper XML, frontend form, export, and permission. Change enum Dictionary value, frontend label, backend validation, existing data. Change query Data scope, tenant scope, index, pagination, and export behavior. Change API Frontend request file, OpenAPI docs, permission identifier, and backward compatibility. Change time-series data TDengine table, retention policy, aggregation, and dashboard query.
Keep database changes traceable through SQL migration files. Do not bypass tenant and data-scope filters in business queries. Reuse dictionaries for status fields when possible. When adding export fields, verify both list display and export output. Prev
Platform topics
Next
Thing model format