Skip to content

Features

Grafix supports the creation and editing of business diagrams via chat input, template selection, or form fields. The functional scope ranges from initial generation through targeted editing of individual regions to export in interchangeable formats. Several mechanisms safeguard the quality of the results.

Application scenarios

  • Create and populate a SWOT analysis — A request such as "SWOT analysis for electric cars" produces the four-quadrant base structure. The individual fields (strengths, weaknesses, opportunities, threats) can then be populated with bullet lists in a targeted way without affecting the other quadrants.
  • Represent processes as a flowchart — A sequence of steps is described as a list ("request, review, approval, implementation") and immediately rendered as a horizontal chevron chain. Subsequent requests can rename, add, or remove individual steps.
  • Build organisation charts with sub-structures — Even complex hierarchies with three levels can be expressed in a single request. When sub-units are mentioned, the application automatically switches from the two-level to the three-level template and assigns the named units to their respective departments.
  • Compare options — Statements like "Comparison: Cloud vs On-Premise" produce a two-column comparison diagram. Follow-up requests can update both the topic (for example switching to "Electric car vs Diesel") and the individual argument lists for the two columns independently.
  • Model and extend Venn relationships — A two-circle Venn diagram can be extended later with a third circle. The application recognises this extension as a template upgrade and transfers the existing content into the new structure.
  • Temporal sequences and KPI overviews — Roadmaps are represented through a timeline template, operational metrics through a dashboard template with tiles. Both templates are scalable in the number of elements.

At a glance

  • 27 diagram types in seven categories (process, list, hierarchy, relationship, matrix, pyramid, cycle).
  • Three input paths: chat-based request, direct template selection from a gallery, form input per template.
  • Slot system for targeted editing of named regions within a diagram.
  • Direct editing on the canvas with selection, moving, text editing, and undo/redo.
  • Seven predefined colour schemes, optional shadows, automatic font-size adjustment.
  • Full session history with the ability to jump back to earlier states.
  • Export as PNG (raster image) and JSON (reconstructible state).

Diagram creation and editing

Diagrams originate either from a free description in the chat or from the selection of a template. In both cases the content is placed into a predefined slot structure whose geometry is set by the template engine. Scalable templates adapt to the number of elements specified, while fixed templates (such as SWOT with its four quadrants) retain their structure.

  • Creation via chat — Natural-language input is classified and translated into a concrete template populated with content.
  • Creation via the template gallery — Templates can be selected directly from a categorised overview and loaded with default content.
  • Editing via form fields — For each template, matching input fields are available (for example the four SWOT fields or the two columns in a comparison) and are re-rendered after a change.
  • Direct editing on the canvas — Individual elements can be selected, moved, and edited textually with the mouse. Steps can be undone and redone.

Slot and upgrade system

Targeted editing of individual regions is based on a slot concept: each template defines named regions that can be addressed individually. A change to "Strengths" affects only that region, not the entire diagram.

When a request exceeds the capacity of a template — for example by adding a third circle to a two-circle Venn diagram or by introducing a third hierarchy level in an organisation chart — the pipeline automatically switches to the more suitable template and transfers the existing content.

Style and layout adjustment

  • Colour schemes — Seven predefined palettes (blue, green, orange, purple, red, teal, gray) that can be assigned by request or selection field.
  • Shadows and contrast — Shadows can be enabled or disabled; the text colour is automatically adjusted to the brightness of the background.
  • Font size — When a text is too long for its container, the template engine reduces the font size automatically within defined bounds.
  • Title — Each diagram can be given a separate main title that can be set and changed independently of its content.

Sessions and history

Every editing operation is assigned to a session and documented as an action with timestamp, original input, recognised action type, and resulting canvas state.

  • Session history — All actions in a session can be viewed in chronological order.
  • Jump to earlier states — Any past canvas state can be restored from the action list.
  • Multiple parallel sessions — Several sessions can be maintained side by side within a single application instance and accessed individually.
  • Session export — A complete session can be saved as a JSON file, including the history and the current canvas state.

Quality assurance

Several stages check whether the produced result matches the request and whether the layout is sound:

  • Structured intent recognition — The language model returns classifications with a confidence value and reasoning. If the confidence falls below a defined threshold, an additional validation step is activated or a clarification question is sent to the user.
  • Validation stage — A separate check compares the produced result against the original intent and identifies discrepancies.
  • Layout consistency check — Visibility, spacing, alignment, overlaps, and colour usage are checked. Detected problems are corrected automatically where possible. For structured templates the template layout is left untouched in order not to break its proportions.
  • Determinism — Because layout generation is rule-based, results are reproducible.
  • Traceability through the session — The JSON history records the input, the recognised classification, its confidence, and the resulting state for every step. This allows every editing operation to be reviewed afterwards.
  • Clarification mechanism — Ambiguous or unclear requests trigger a clarification question instead of a guessed action.

Input and output

  • Input formats — Free text in the chat, selection from the template gallery, structured form fields per template.
  • Export formats — PNG for distribution or embedding in reports and presentations; JSON for archiving the editable state or re-importing it into another instance.