0005718: Support the full set of ArchiMate relationship types in the ArchiMate export

ID	Project	Category	View Status	Date Submitted	Last Update
0005718	CaseTalk Modeler	Import and Export	public	2026-07-01 12:03	2026-07-27 17:47

Reporter	Marco Wobben	Assigned To
Priority	normal	Severity	feature	Reproducibility	have not tried
Status	new	Resolution	open
Target Version	15.x

Summary	0005718: Support the full set of ArchiMate relationship types in the ArchiMate export
Description	The ArchiMate export (PlantUML picture and XMI) currently renders these relationships, derived automatically where the model implies them: composition and aggregation (from a relationship's type or a container grouping its members), specialization (subtype), realization (concept to object type) and association (the default). Extend it to support the remaining ArchiMate relationship types so exported diagrams can express the full notation: Assignment Serving Access (read / write / read-write) Influence Triggering Flow Junctions (and/or connectors) This requires a way to assign an ArchiMate relationship type to a relationship between concepts/containers, and the ability to set that type through the MCP interface (which today can set an element's ArchiMate type but not a relationship's).
Tags	No tags attached.

CaseTalk Edition	Corporate

Date Modified	Username	Field	Change
2026-07-01 12:03	Marco Wobben	New Issue
2026-07-01 12:10	Marco Wobben	Relationship added	related to 0005719
2026-07-27 17:47	Marco Wobben	Note Added: 0008660

Marco Wobben 2026-07-27 17:47 administrator ~0008660	A matrix can be assembled between partof/playedby types to determine the most likely archimate relationship type, but roles may still need some concepttype similar to the OTFT does.