View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0005029CaseTalk ModelerGeneration (SQL, XML, etc)public2025-03-13 10:242025-03-16 11:35
ReporterBCP Software Assigned ToBCP Software  
PrioritynormalSeveritymajorReproducibilityhave not tried
Status resolvedResolutionfixed 
PlatformIntelOSWindowsOS Version11
Target Version14.xFixed in Version14.2 
Summary0005029: OWL Max Cardinality wrong for InterUCs
DescriptionWhen InterUCs is placed on roles, and the fact types are grouped into the class. These attributes are generated having a maxCardinality of 1. This is only valid for regular UCs, not for InterUCS.
TagsNo tags attached.
CaseTalk Editionunknown

Activities

BCP Software

BCP Software

2025-03-13 13:14

administrator   ~0005502

The model transformations were taking InterUCs as regular UCs. This resulted in UML Attribute not showing up, and the cardinality should've been maxCardinality for most attributes (unless theres a wide UC creating a multi value attribute).
BCP Software

BCP Software

2025-03-13 13:15

administrator   ~0005503

The cardinality on attributes and relations is now consistent, with or without interUCs. The InterUC on attributes inside one class, may render a ClassMethod in UML diagrams to validate this interUC.

Issue History

Date Modified Username Field Change
2025-03-13 10:24 BCP Software New Issue
2025-03-13 10:24 BCP Software Status new => assigned
2025-03-13 10:24 BCP Software Assigned To => BCP Software
2025-03-13 13:14 BCP Software Note Added: 0005502
2025-03-13 13:15 BCP Software Status assigned => resolved
2025-03-13 13:15 BCP Software Resolution open => fixed
2025-03-13 13:15 BCP Software Fixed in Version => 14.x
2025-03-13 13:15 BCP Software Note Added: 0005503
2025-03-16 11:35 BCP Software Fixed in Version 14.x => 14.2