Areas, tasks, views and sheets
Organize investigations of one database: shared area structure, task plan and journal, semantic views and independent sheets.
SchemaMap 0.14.0 · Updated · The editor uses Russian UI labels, shown as written.
Four levels of context
An area contains one source structure and a shared library. A task owns the goal, description, journal, links and common planned changes. A view groups a meaningful part of the investigation. A sheet holds a specific table selection, JOINs, notes and layout. For example, a Payment refund task can contain Existing flow and Future validation views, each with an overview and detail sheet.
Build and save context
- Select an area and create a task from the task menu.
- Create a view and sheet, then choose relevant tables.
- Open the task description beside the views. Add the goal and use «Добавить» (Add) in the left journal for a separate finding.
- Set tracker, MR and Swagger links in task settings if needed.
- Wait for server saving, then reopen the sheet.
The result is a saved investigation with a shared goal and its own layout. Duplicated sheets are independent. Open tabs, selection and camera are personal; sheet content and coordinates are shared.
History and limits
Journal entries append without replacing the description or earlier entries: up to 500 entries, a 160-character title and a 65,535-character body. Object descriptions have a common level and sheet-specific notes. Sheet history does not roll back the common task plan. Concurrent content changes return a conflict while retaining the local draft. Moving sheets between incompatible task plans is rejected.
Next: Tables, foreign keys, JOINs and indexes
Related materials: Plan a task’s future structure · Collaboration and roles