View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0003572CaseTalk ModelerRepositorypublic2022-08-18 16:332022-08-19 10:58
ReporterMarco Wobben Assigned ToMarco Wobben  
PrioritynormalSeveritymajorReproducibilityhave not tried
Status resolvedResolutionfixed 
Target Version12.5Fixed in Version12.5 
Summary0003572: Role subtype optional failure
DescriptionRoles in subtypes cannot be optional, and roles in single OTE, do not turn to optional either. Behaviour seems inconsistent.
TagsNo tags attached.
CaseTalk Editionunknown

Activities

Marco Wobben

Marco Wobben

2022-08-19 09:32

administrator   ~0004589

Last edited: 2022-08-19 10:14

 When an OTFT is posted the routines are triggered to determine if roles are optional or not.

We assume the roles are non optional, until we find an expression which lacks that role in it.
Additionally the NOT NULL flag should overrule this optionality.
Marco Wobben

Marco Wobben

2022-08-19 10:58

administrator   ~0004590

Drawing of OP for optional roles remains the same, though is determined by the role being in the expression or not. Additionally the NOT NULL flag on roles overrules the optional role state. And the diagram drawing of OP/NN is made consistent.

Issue History

Date Modified Username Field Change
2022-08-18 16:33 Marco Wobben New Issue
2022-08-18 16:33 Marco Wobben Status new => assigned
2022-08-18 16:33 Marco Wobben Assigned To => Marco Wobben
2022-08-19 09:32 Marco Wobben Note Added: 0004589
2022-08-19 10:14 Marco Wobben Note Edited: 0004589
2022-08-19 10:58 Marco Wobben Status assigned => resolved
2022-08-19 10:58 Marco Wobben Resolution open => fixed
2022-08-19 10:58 Marco Wobben Fixed in Version => 12.5
2022-08-19 10:58 Marco Wobben Note Added: 0004590