Create a project and diagram

Click path

You need project-creation access in AGL Studio.

1. Open Projects → New Project (accessible name Create New Project).
2. Open the project and click New Diagram.
3. In the visual editor, open Insert and place a component such as Server.
4. Set its name/properties in the inspector; use the connection tool for relationships.
5. Click Save, wait for confirmation and reopen the diagram from the project.

Enlarge screenshot

1 2

1. Create new project
2. Search projects

Enlarge screenshot

1 2 3 4 5 6

1. AGL Code
2. Save
3. AGL Code
4. Save
5. Export as SVG
6. Insert active shape from Shapes drawer

Verify and recover

Verify project membership and persistent elements/relationships after reopening. The real editor capture uses the built-in mock API, not a production write. Check role/organization for unavailable controls; preserve an available export before closing an unsaved diagram after failure.

Architecture levels and available notations

Select Architecture level first, then Notation. The menu contains only supported combinations for that level and, for Enterprise, the Enterprise layer. Selecting a notation retains the level. Explicitly changing the level or enterprise layer replaces an incompatible notation with a suitable default: ArchiMate for Enterprise, C4 for Solution/System/Infrastructure, Network for Network. Objects and relationships from other views remain in .agl; the switch can be undone.

This is Studio’s supported profile matrix. C4 choices follow its abstraction levels and supporting diagrams. To switch from Container to Component using dropdowns, select System; object drill-down and canvas navigation remain separate.

Enlarge screenshot

1 2 3 4

1. Уровень архитектуры
2. Нотация
3. Слой предприятия
4. Доступные нотации / Available notations

In analytics, Create BPMN diagram creates a process at Enterprise / Business architecture; a new data model uses native ERD at System, and an integration flow uses C4 Dynamic at Solution. New files persist these settings. Existing analytical files retain their authored object types.

If an older file contains an incompatible level/notation pair, Studio resolves a compatible display context from its saved notation and C4 view. Authored objects are retained without conversion. Explicitly select a level for another view; if its objects are missing, add them from the library or ask the agent. Press Cmd/Ctrl+S to save your selection.

BPMN capabilities and scenarios

In local AGL Studio, use File → Open project… to open an .agl file and select the BPMN notation. Editing requires an editable project; saving requires write access to its file. Manual editing works without an external server.

Selectors, buttons and counts align on one row. In a narrow window, the row scrolls horizontally; Capability and Scenario captions remain above their selectors.

1. Use Capability and Scenario in the compact toolbar above the canvas. Only explicitly included objects and flows appear. All processes restores the complete diagram.
2. Click BPMN scenarios (accessible name and tooltip: Configure BPMN scenarios). Settings float over the canvas.
3. In Scenario binding, select an existing scenario, including one created for Sequence, or New BPMN scenario. Set Scenario capability, Capability name and Scenario name.
4. Scenario description, Scenario objects and Scenario flows open individual dropdown panels. Select process membership; a flow is available when both endpoints are included. Lists scroll without increasing the main toolbar height.
5. Click the disk icon Save BPMN binding. Press Cmd/Ctrl+S to write the complete .agl, bindings and selected scenario. Reopen the file and verify the selected process and description.

Enlarge screenshot

1 2 3 4 5

1. Выбрать capability BPMN
2. Выбрать сценарий BPMN
3. Настроить сценарии BPMN
4. Объекты сценария · 3/4
5. Сохранить привязку BPMN

Shared events, tasks and flows may belong to several scenarios without duplicating objects. One scenario can have both Sequence and a separate BPMN projection. New canvas objects join the selected BPMN scenario; deleting an object removes stale bindings. Undo restores topology and membership together. Remove BPMN binding retains the underlying objects and any existing Sequence projection.

SVG, PNG, PDF and BPMN XML Export uses the selected process; .agl retains all processes. Older BPMN files without bindings open as a complete diagram. Agents can supply explicit capabilities/scenarios and membership; invented IDs, unsupported types and flows with endpoints outside the scenario are rejected.

If the saved scenario is absent from the selected architecture scope, Scenario is unavailable in this view appears instead of silently substituting another process. Restore the appropriate architecture scope, choose another scenario or All processes. Correct names/membership after a rejected edit and save again. Keep unsaved files open until Cmd/Ctrl+S completes. The screenshot shows the real Russian-language interface using synthetic data.