View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005775 | CaseTalk Modeler | User Interface | public | 2026-07-22 14:39 | 2026-07-25 22:02 |
| Reporter | Marco Wobben | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Target Version | 15.0 | ||||
| Summary | 0005775: New fact expression created roles marked as Link instead of FCO-IM | ||||
| Description | When a new fact expression is entered in the expression input dialog for a subject that is still a concept, the roles that are created for that expression are classified as generic 'Link' relationships rather than as FCO-IM fact roles. Because the roles carry the wrong classification, they are treated as ordinary links wherever role classification matters: they are excluded from FCO-IM-only role listings, they are drawn and reported as links instead of fact roles, and they are skipped by checks and verbalizations that only consider FCO-IM roles. The model looks correct on screen but behaves as if the fact type has no proper roles. Only the first expression entered for a concept is affected; expressions added afterwards are classified correctly, which makes the problem easy to miss. | ||||
| Tags | No tags attached. | ||||
| CaseTalk Edition | Corporate | ||||
| related to | 0005798 | resolved | Changing the meta level of a type does not reclassify its existing roles |
|
Fixed. A concept is now promoted to a fact or object type as soon as the very first expression is attached to it, before any roles for that expression are created. The roles are therefore classified as proper FCO-IM fact roles right away. In addition, the role classification is now recalculated once more when the expression is finally stored, after all involved types have their definitive kind. This also corrects roles whose classification would otherwise be based on a type that was still being determined while the expression was being entered - for example a player that was created as a label and only later became an object type. Existing models that already contain wrongly classified roles are not repaired automatically; re-entering or editing the affected expression will correct them. |
|
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-07-22 14:39 | Marco Wobben | New Issue | |
| 2026-07-22 14:39 | Marco Wobben | Note Added: 0008546 | |
| 2026-07-22 14:39 | Marco Wobben | Status | new => resolved |
| 2026-07-22 14:39 | Marco Wobben | Resolution | open => fixed |
| 2026-07-25 22:02 | Marco Wobben | Relationship added | related to 0005798 |