0000744: Hierarchical formats require a root selection

ID	Project	Category	View Status	Date Submitted	Last Update

0000744	CaseTalk Modeler	Import and Export	public	2015-10-07 17:55	2023-04-22 12:20

Reporter	Marco Wobben	Assigned To	Marco Wobben
Priority	normal	Severity	feature	Reproducibility	sometimes
Status	assigned	Resolution	open
Product Version	6.6
Target Version	Future

Summary	0000744: Hierarchical formats require a root selection
Description	Hierarchical formats like xml for soap calls, require a root instance (type) to make the selection. A graph or network like structure does not provide for this. A diagram as selection could be used as a type selection, but still require a root as starting point.
Additional Information	Workaround before a final decision or solution is made: Perhaps the name of the diagram, corresponding to the root otft, would be an easy way to start.
Tags	No tags attached.

CaseTalk Edition

Date Modified	Username	Field	Change
2015-10-07 17:55	Marco Wobben	New Issue
2015-10-07 17:55	Marco Wobben	Status	new => assigned
2015-10-07 17:55	Marco Wobben	Assigned To	=> Marco Wobben
2015-11-17 10:39	Marco Wobben	Note Added: 0000470
2016-01-20 12:58	Marco Wobben	Category	Import/Export => Import and Export
2023-04-22 12:20	Marco Wobben	Relationship added	related to 0003940

Marco Wobben 2015-11-17 10:39 administrator ~0000470	Idea: A simple property added to the diagram itself may specify which FactType is supposed to be the root. The validation should check if all FactTypes are connected in this hierarchy before implementing any hierarchy related operation. Also the FactType should be visually marked so the user will recognize it.