Skip to main content

Diagram overview

Diagrams are visual views of your architecture model. They help teams explore structure, tell a story, and collaborate around a specific question.

A good diagram has a clear purpose. For example:

  • Map the applications that support a business capability.
  • Explain a data flow between systems.
  • Show a target landscape for a transformation program.
  • Capture workshop ideas before approving them into the shared repository.

Shared diagram workspace in Caplo

Repository-linked shapes​

When a shape represents a reusable architecture object, link it to a repository entity. This lets the same entity appear on many diagrams without becoming separate records.

Linked shapes stay connected to the shared model. Their names, properties, relations, report usage, and other diagrams all refer back to the same repository item.

If something only matters on one diagram, keep it freeform instead. Use draw-mode shapes, labels, and arrows for explanation, framing, or workshop notes that should not become reusable repository data.

Diagram references​

When you select a repository-linked entity shape, the right panel shows Diagram references. This section lists every place where the same entity appears in diagrams, including normal architecture shapes, BPMN shapes, and Mermaid shapes.

Each reference has an icon that shows where the entity was found:

  • The entity type icon means the entity is linked through a normal architecture shape, such as an Application, Process, Capability, or Data object.
  • A BPMN icon means the entity is linked through a BPMN diagram shape.
  • A Mermaid icon means the entity is referenced from a Mermaid diagram shape.

Click a reference to open that diagram and focus the relevant shape. You can also right-click a selected entity shape on the canvas and use Diagram references from the context menu for the same cross-diagram navigation. On an entity detail page, the Diagrams tab lists the same usages with a shape type column so you can see whether each row comes from a normal entity shape, BPMN, or Mermaid.

Arrows and relations​

When both ends of an arrow are linked to repository entities, Caplo can create or reuse the matching reusable relation for you.

That is why relation-aware arrows matter: they do not just decorate the canvas, they update shared architecture structure.

Draw mode and Architect mode​

Caplo supports two modeling styles:

  • Draw mode keeps the canvas lightweight for sketching, annotation, and early thinking.
  • Architect mode focuses on architecture shapes, entity linking, reusable relations, and repository reuse.

Switch modes based on the work you are doing. Early workshops may start in Draw mode and move into Architect mode once the team agrees on reusable entities.

Panels​

The diagram page includes a left entity panel and a right properties panel. Use the page-header buttons to open or close them as needed.

Typical flow:

  1. Open the left panel to find and drag repository entities onto the canvas.
  2. Select a shape or relation on the canvas.
  3. Use the right panel to inspect or edit its properties and relations.

Collaboration​

Diagrams are designed for team work. Multiple people can work from the same shared diagram, while Personal diagrams remain useful for drafts and exploration.

Keyboard shortcuts​

Useful Diagram shortcuts and controls:

  • Undo: Ctrl+Z on Windows/Linux or Cmd+Z on macOS.
  • Redo: Ctrl+Shift+Z on Windows/Linux or Cmd+Shift+Z on macOS.
  • Pan the canvas: drag with the scroll wheel, or hold Space while dragging.
  • Zoom: hold Ctrl while scrolling.