export_model_content
Serialize the active ArchiMate model as XML string content, with support for multiple output formats and optional automatic layout.
Instructions
Serialize the active model as XML string content.
Use this when the caller wants the XML in the response payload. Use
`export_model_to_file` to write directly to disk.
Args:
output_format: One of `archimate` (default, Open Group exchange
XML), `archi` (Archi native `.archimate` XML, opens directly
in Archi), or `xml`.
auto_layout: When true, run layout on every view before
serialization. Defaults to false.
layout_strategy: Layout strategy used when `auto_layout=true`.
One of `layered_by_type` (default, ArchiMate semantic
lanes), `layered` (relationship-direction layered), or
`grid`.
layout_engine: Layout engine applied to every view when
`auto_layout=true`. One of `internal` (default) or
`pyarchimate` (see `auto_layout_view` for what the latter
gives up). Per-call only: nothing about the engine is
written into the exported file. Validated even when
`auto_layout=false`, so a typo is never swallowed.
Returns:
Success envelope with `data.content` (XML string),
`data.auto_layout`, and (when `auto_layout=true`)
`data.layout_strategy` and `data.layout_engine`.
Errors:
`ModelNotFoundError` if no model is active.
`UnsupportedFormatError` for an unknown `output_format`.
`ModelOperationError` for layout or serialization failures,
including an unknown strategy/engine (with
`error.details.suggestions`) and a view the `pyarchimate`
engine cannot lay out safely — one such view fails the
whole export.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| auto_layout | No | ||
| quality_gate | No | off | |
| allow_orphans | No | ||
| layout_engine | No | internal | |
| output_format | No | archimate | |
| layout_strategy | No | layered_by_type | |
| allow_visual_issues | No | ||
| allow_semantic_issues | No | ||
| include_quality_report | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||